Hello,
I am encountering an issue where my system freezes entirely after a random but short time after boot-up: the computer does not react to any user input, be it mouse, keyboard or plugging-unplugging peripherals. The image on screen remains still and does not go black. Any sound that was playing at the moment of the freeze loops indefinitely with a period of around 1s. I have the intuition that the issue is sound related because of that.
Some additional information with this issue - Only happens only with the latest stable releases of the kernel: 5.12.9 and 5.12.10 . 5.12.8 does not have this issue. I have not tested other kernel version, e.g. LTS 5.10 , to see if it's a change that got back-ported. - Happens in Gentoo and archlinux with their respective official kernel binary release. But also self built, with Archlinux's upstream .config file and also stripped down versions (please find an example .config attached as config-stripped). Happens on Gnome on Wayland and Xorg and on LXQt (Openbox). - The output of `journalctl` stops before the freeze happens, I suppose it's because nothing can be saved in the disk when it happens. Please find the output of journalctl for a boot where the freeze happens attached to this mail as `journaloutput`. This should give all the necessary information about my system. I just realized that I have extra boot kernel parameters, maybe removing the extra ones works around the issue and would help pinpoint the issue. I will report back if I have any extra information
Given the above information I believe this issue is best reported to you. I unfortunately do not have more information to report for proper pinpointing and I am willing to work from your directed feedback. My kernel knowledge is limited but I can probably deal with technical requests from you given enough time and documentation.
Thank you for your help and I hope I am not wasting your time with something
Kind regards,
Adel KARA SLIMANE
On Sun, Jun 13, 2021 at 08:19:37PM +0200, adel.ks@zegrapher.com wrote:
Hello,
I am encountering an issue where my system freezes entirely after a random but short time after boot-up: the computer does not react to any user input, be it mouse, keyboard or plugging-unplugging peripherals. The image on screen remains still and does not go black. Any sound that was playing at the moment of the freeze loops indefinitely with a period of around 1s. I have the intuition that the issue is sound related because of that.
Some additional information with this issue
- Only happens only with the latest stable releases of the kernel: 5.12.9
and 5.12.10 . 5.12.8 does not have this issue. I have not tested other kernel version, e.g. LTS 5.10 , to see if it's a change that got back-ported.
Any chance you can run 'git bisect' to find the offending change? That's the easiest way to fix this up.
thanks,
greg k-h
Hello,
Yes I can, I will do then report back. It will take me some time as I only know how to do it manually.
Thank you for your help,
Adel
Jun 14, 2021 07:17:59 Greg KH gregkh@linuxfoundation.org:
On Sun, Jun 13, 2021 at 08:19:37PM +0200, adel.ks@zegrapher.com wrote:
Hello,
I am encountering an issue where my system freezes entirely after a random but short time after boot-up: the computer does not react to any user input, be it mouse, keyboard or plugging-unplugging peripherals. The image on screen remains still and does not go black. Any sound that was playing at the moment of the freeze loops indefinitely with a period of around 1s. I have the intuition that the issue is sound related because of that.
Some additional information with this issue
- Only happens only with the latest stable releases of the kernel: 5.12.9
and 5.12.10 . 5.12.8 does not have this issue. I have not tested other kernel version, e.g. LTS 5.10 , to see if it's a change that got back-ported.
Any chance you can run 'git bisect' to find the offending change? That's the easiest way to fix this up.
thanks,
greg k-h
Hello,
I decided to test first the ALSA changes, which happen to be the commits right after v5.12.8, and the very first commit of the series, `73d862c55 ALSA: hda/realtek: the bass speaker can't output sound on Yoga 9i` made the freeze happen (although it took some time when compared to f3c23683d and 59ef5291f).
I am ready and willing to help further on the matter.
Kind regards,
Adel K.S.
On 2021-06-14 11:03, Adel Kara Slimane wrote:
Hello,
Yes I can, I will do then report back. It will take me some time as I only know how to do it manually.
Thank you for your help,
Adel
Jun 14, 2021 07:17:59 Greg KH gregkh@linuxfoundation.org:
On Sun, Jun 13, 2021 at 08:19:37PM +0200, adel.ks@zegrapher.com wrote:
Hello,
I am encountering an issue where my system freezes entirely after a random but short time after boot-up: the computer does not react to any user input, be it mouse, keyboard or plugging-unplugging peripherals. The image on screen remains still and does not go black. Any sound that was playing at the moment of the freeze loops indefinitely with a period of around 1s. I have the intuition that the issue is sound related because of that.
Some additional information with this issue
- Only happens only with the latest stable releases of the kernel:
5.12.9 and 5.12.10 . 5.12.8 does not have this issue. I have not tested other kernel version, e.g. LTS 5.10 , to see if it's a change that got back-ported.
Any chance you can run 'git bisect' to find the offending change? That's the easiest way to fix this up.
thanks,
greg k-h
On Mon, Jun 14, 2021 at 01:47:46PM +0200, adel.ks@zegrapher.com wrote:
Hello,
I decided to test first the ALSA changes, which happen to be the commits right after v5.12.8, and the very first commit of the series, `73d862c55 ALSA: hda/realtek: the bass speaker can't output sound on Yoga 9i` made the freeze happen (although it took some time when compared to f3c23683d and 59ef5291f).
I am ready and willing to help further on the matter.
Thanks for testing!
So I am also guessing that 5.13-rc6 fails in this same way?
And you do have this specific hardware, for this specific patch, right?
thanks,
greg k-h
Hello,
So I am also guessing that 5.13-rc6 fails in this same way?
I took the time to compile and test the 5.13-rc6 version: it has the same issue (complete freeze with sound looping forever until I manually switch off the computer with the hardware button on the case). Please find attached the kernel journal for that specific boot, called `journaloutput-513r6`
And you do have this specific hardware, for this specific patch, right?
Yes, I have a Realtek ALC1220 codec in my motherboard, currently on 5.12.8, I have the following modules running:
$ lsmod | grep snd snd_usb_audio 331776 2 snd_usbmidi_lib 45056 1 snd_usb_audio snd_rawmidi 40960 1 snd_usbmidi_lib snd_hda_codec_realtek 159744 1 snd_hda_codec_generic 94208 1 snd_hda_codec_realtek ledtrig_audio 16384 1 snd_hda_codec_generic snd_hda_codec_hdmi 73728 1 snd_hda_intel 57344 4 snd_intel_dspcfg 20480 1 snd_hda_intel snd_hda_codec 163840 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_hwdep 16384 2 snd_usb_audio,snd_hda_codec snd_hda_core 106496 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_pcm 114688 5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core snd_timer 40960 1 snd_pcm snd
I found it intriguing that I am the first person to report this issue, maybe because of my specific hardware interaction and use-case, some additional information: - I use the line-out rear port of my motherboard to connect to a home-cinema through a 3.5mm jack cable. To trigger the issue, I am playing the same video on MPV (a video player) with sound output to the home-cinema (therefore using the realtek soundcard). The freeze usually gets triggered at a random time within the 20mins the video takes. The freeze does happen without using MPV though, sometimes system sounds (like pressing backspace on an empty field) trigger it too.
- Motherboard: MSI MPG X570 GAMING PRO CARBON WIFI, BIOS 7B93v1C, with AMD ComboAM4PIV2 1.2.0.2. More information in ref [1] - External USB sound card running at the same time: SteelSeries GameDAC [2] (I decide to redirect sound output in a per-app basis with pulseaudio and pavucontrol) - My GPU supports audio through HDMI but my monitor is connected through DP and does not have speakers. - CPU: Ryzen 5950X - GPU: 5700XT
I am wondering how can ALSA affect the kernel up to the point that it can't write things to the journal. Is it something worse than a "kernel panic" (that I have never encountered before) ?
Thanks for testing!
I am really happy to finally be able to contribute! Thank you for sparing some time for this issue.
Please feel free to ask anything so we can progress further on the issue, I will be awaiting instructions.
Kind regards,
Adel K.S.
[1] https://www.msi.com/Motherboard/MPG-X570-GAMING-PRO-CARBON-WIFI/Specificatio... [2] https://steelseries.com/gaming-accessories/gamedac
Hello,
I have an important new information to report that may make the bisected commit not (entirely) guilty. It may be more of a sign of a subtle hardware failure on my end than a kernel regression/bug.
The fact that the bisection I did gave out the very first commit after the v5.12.8 tag puzzled me. So I built the 5.12.8 version with the same `.config` (I attached to this mail as `config.bisect`) that I used for bisection and worked with it since then, it took hours (instead of the average dozen minutes) but it ended up freezing. So the changes that have been brought by the ALSA patches that start with the commit 73d862c55 seem to have only made a deeper, more subtle, issue more apparent by making the freeze happen very early.
The 5.12.8 version that I use that hasn't frozen for the past weeks of use contains out-of-tree patches (e.g. a different CPU task scheduler) and does not have the same `.config` file (I attached it as `config.works`). `config.works` freezes with 5.12.9 too (with the same extra out-of-tree patches). I will reuse it as a base for vanilla building and test things out again. I will also reduce my RAM frequency to a very safe (not XMP) one.
I am willing to do everything that is needed to pinpoint precisely the issue on my own, with your help, if possible.
I hope I am not wasting anyone's time with this report. If you deem it so, please inform me and I will immediately refrain from writing any further.
Kind regards,
Adel K.S.
Hello,
A small update on the matter, the bisected commit 73d862c55 `ALSA: hda/realtek: the bass speaker can't output sound on Yoga 9i` is not the one that introduced the issue. I will keep the lengthy bisection ongoing till I can find it. It will take at least few days as I do not have a way yet to trigger the freeze at will. But playing a video through MPV with the sound output through a jack cable is my only "best" method so far.
I will be bisecting with Arch's config file, but with modules stripped through `make LSMOD=modprobed.db localmodconfig` to win some build time and restrict the possibilities, please find the config attached as `config.arch.stripped` and the module database as `modprobed-db`. If you would like me to use another base `.config` file, please send it to me.
The tests I did again so far with the `config.arch.stripped`: - v5.12.10 and could reproduce the freeze. Both with RAM at its original 3400Mhz CL15 speed and at a looser 2666Mhz CL20 speed: RAM is therefore likely not the culprit. So I reverted back to 3400Mhz CL15. On whom I ran memtest86+ 4 passes in the past without reported errors. - v5.12.8 and could reproduce the freeze again, which makes the commit 73d862c55 not guilty.
I am testing v5.12.6 right now, and I will be making bigger steps back in time till I find a version on which I cannot reproduce the freeze in a reasonable time: I will give it two days of normal use to deem it good.
I think this issue is not related to my hardware as I own a custom v5.12.8 version that has not frozen in the past weeks of use (I attached it in one previous message as `config.works`). Its vanilla counterpart (I ran `make xconfig` on `config.works` to remove the spurious additions), attached to this mail as `config.works.vanilla` seems to workaround the issue in v5.12.10 as I couldn't make it freeze with the same procedure under the same time constraint, although I must keep running it for longer to really be sure.
Please feel free to give your thoughts and direct my research, I will keep updating this thread with my progress if no objection is expressed.
Thank you for your time and consideration,
Kind regards,
Adel K.S.
Hello,
Kernel versions back to 5.9 were freezing on my machine. Which clearly indicated that something was wrong with my hardware: I pinpointed the issue to my BIOS. I had a few CPU options toggled on: "Global C states control", "Collaborative Processor Performance Control (CPPC)" and "CPPC Prefered cores". Toggling those settings back to "auto" (which means probably it's off ?) prevented the issue from happening since then. Note that the hardware these freezes was happening on is a AMD Ryzen 5950X with a X570 chipset motherboard.
Thank you
Kind regards,
Adel KARA SLIMANE
linux-stable-mirror@lists.linaro.org
-
Adel Kara Slimane -
adel.ks＠zegrapher.com
-
Greg KH