Created attachment 1798414 [details] kernel logs 1. Please describe the problem: Intermittently sound stops working suddenly on a Thinkpad T490s laptop. This appears to be a kernel level failure and these error messages show up in dmesg: [18466.050281] snd_hda_intel 0000:00:1f.3: refused to change power state from D3hot to D0 [18466.170222] snd_hda_intel 0000:00:1f.3: CORB reset timeout#2, CORBRP = 65535 [18466.396499] snd_hda_codec_hdmi hdaudioC1D2: Unable to sync register 0x2f0d00. -5 [18466.623414] snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 [18466.623463] snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 [18470.023623] snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 [18470.023692] snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 2. What is the Version-Release number of the kernel: kernel-5.12.13-300.fc34.x86_64 (Also several previous kernels) 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? Old kernels are available for download at https://koji.fedoraproject.org/koji/packageinfo?packageID=8 : This has worked previously, but since it triggers only intermittently, I'm not certain so far which kernel this first appeared in. If I have time, I will investigate. 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: I have no reliable reproducer. It seems to be linked to plugging in and/or unplugging a headset, thus changing the sound device's output . It might also be linked to docking/undocking, which also switches between the internal sound and the dock sound. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: Not tested yet, I'll try to test and update. 6. Are you running any modules that not shipped with directly Fedora's kernel?: No. 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag.
Well, I tried to install the rawhide kernel and got this: Downloading Packages: [SKIPPED] kernel-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64.rpm: Already downloaded [SKIPPED] kernel-core-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64.rpm: Already downloaded [SKIPPED] kernel-modules-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64.rpm: Already downloaded Fedora - Rawhide - Developmental packages for the next Fedora release 1.6 MB/s | 1.6 kB 00:00 GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-34-x86_64 (0x45719A39) is already installed Fedora - Rawhide - Developmental packages for the next Fedora release 1.6 MB/s | 1.6 kB 00:00 GPG key at file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-36-x86_64 (0x38AB71F4) is already installed The GPG keys listed for the "Fedora - Rawhide - Developmental packages for the next Fedora release" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository.. Failing package is: kernel-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-34-x86_64, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-36-x86_64 Public key for kernel-core-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64.rpm is not installed. Failing package is: kernel-core-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-34-x86_64, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-36-x86_64 Public key for kernel-modules-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64.rpm is not installed. Failing package is: kernel-modules-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64 GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-34-x86_64, file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-36-x86_64 The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: GPG check FAILED
I eventually managed to install the rawhide kernel: kernel-5.14.0-0.rc0.20210701gitdbe69e433722.6.fc35.x86_64 I've had that installed for a couple of weeks and haven't seen the problem again, so I think the rawhide kernel probably fixes this bug.
Problem is still present with kernel-5.13.9-200.fc34.x86_64 (stopped using the Rawhide kernel because it had other problems).
@dgibson It looks like I'm having a similar problem with my Dell XPS 13 on Arch Linux. It's been there for a while (5.12?) and I can confirm it's still a problem in 5.13. I was advised to add the following to a modprobe config file and will try that right now. I want to share this with you as I stumbled over this thread while searching for the problem: options snd_hda_intel power_save=0 https://bbs.archlinux.org/viewtopic.php?id=269058
Thanks for the information. I haven't the problem show up for a while (with kernel-5.13.12-200.fc34.x86_64). If it shows up again, I'll try disabling powersave.
Alas, while I didn't see the problem with the Rawhide 5.14, I do still see the problem with kernel-5.14.14-200.fc34.x86_64. Trying the power_save option next.
I get this error on Asrock X370 Taichi, only when the computer comes back from sleep. Only the mouse stopped working, and it works when I move it to another USB port. Kernel 5.10.78. [ 10.142906] hid-generic 0003:046D:C084.0002: input,hiddev96,hidraw1: USB HID v1.11 Keyboard [Logitech G203 Prodigy Gaming Mouse] on usb-0000:0e:00.3-4/input1 [203401.907866] xhci_hcd 0000:0e:00.3: saving config space at offset 0x0 (reading 0x145c1022) [203401.907867] xhci_hcd 0000:0e:00.3: saving config space at offset 0x4 (reading 0x100403) [203401.907869] xhci_hcd 0000:0e:00.3: saving config space at offset 0x8 (reading 0xc033000) [203401.907870] xhci_hcd 0000:0e:00.3: saving config space at offset 0xc (reading 0x800010) [203401.907871] xhci_hcd 0000:0e:00.3: saving config space at offset 0x10 (reading 0xfca00004) [203401.907872] xhci_hcd 0000:0e:00.3: saving config space at offset 0x14 (reading 0x0) [203401.907873] xhci_hcd 0000:0e:00.3: saving config space at offset 0x18 (reading 0x0) [203401.907874] xhci_hcd 0000:0e:00.3: saving config space at offset 0x1c (reading 0x0) [203401.907875] xhci_hcd 0000:0e:00.3: saving config space at offset 0x20 (reading 0x0) [203401.907876] xhci_hcd 0000:0e:00.3: saving config space at offset 0x24 (reading 0x0) [203401.907877] xhci_hcd 0000:0e:00.3: saving config space at offset 0x28 (reading 0x0) [203401.907878] xhci_hcd 0000:0e:00.3: saving config space at offset 0x2c (reading 0x79141849) [203401.907879] xhci_hcd 0000:0e:00.3: saving config space at offset 0x30 (reading 0x0) [203401.907881] xhci_hcd 0000:0e:00.3: saving config space at offset 0x34 (reading 0x48) [203401.907882] xhci_hcd 0000:0e:00.3: saving config space at offset 0x38 (reading 0x0) [203401.907883] xhci_hcd 0000:0e:00.3: saving config space at offset 0x3c (reading 0x304) [203401.907899] xhci_hcd 0000:0e:00.3: PME# enabled [203401.920205] xhci_hcd 0000:0e:00.3: PCI PM: Suspend power state: D3hot [248242.381298] xhci_hcd 0000:0e:00.3: refused to change power state from D3hot to D0 [248242.441825] xhci_hcd 0000:0e:00.3: PME# disabled [248242.453072] xhci_hcd 0000:0e:00.3: refused to change power state from D3hot to D0 [248242.453083] xhci_hcd 0000:0e:00.3: enabling bus mastering [248242.453087] xhci_hcd 0000:0e:00.3: Controller not ready at resume -19 [248242.453088] xhci_hcd 0000:0e:00.3: PCI post-resume error -19! [248242.453089] xhci_hcd 0000:0e:00.3: HC died; cleaning up [248242.453129] PM: Device 0000:0e:00.3 failed to resume async: error -19 [248257.314088] xhci_hcd 0000:0e:00.3: xHCI host controller not responding, assume dead [248257.314093] xhci_hcd 0000:0e:00.3: HC died; cleaning up [248257.314126] xhci_hcd 0000:0e:00.3: Timeout while waiting for configure endpoint command after unbind/bind [248842.066208] xhci_hcd 0000:0e:00.3: remove, state 4 [248842.066212] usb usb4: USB disconnect, device number 1 [248842.066398] xhci_hcd 0000:0e:00.3: USB bus 4 deregistered [248842.066405] xhci_hcd 0000:0e:00.3: remove, state 4 [248842.066406] usb usb3: USB disconnect, device number 1 [248842.066523] xhci_hcd 0000:0e:00.3: Host halt failed, -19 [248842.066524] xhci_hcd 0000:0e:00.3: Host not accessible, reset failed. [248842.066614] xhci_hcd 0000:0e:00.3: USB bus 3 deregistered [248842.066747] xhci_hcd 0000:0e:00.3: runtime IRQ mapping not provided by arch [248842.078206] xhci_hcd 0000:0e:00.3: refused to change power state from D3hot to D0 [248842.078326] xhci_hcd 0000:0e:00.3: enabling bus mastering [248842.078329] xhci_hcd 0000:0e:00.3: xHCI Host Controller [248842.078334] xhci_hcd 0000:0e:00.3: new USB bus registered, assigned bus number 3 [248842.078343] xhci_hcd 0000:0e:00.3: Host halt failed, -19 [248842.078344] xhci_hcd 0000:0e:00.3: can't setup: -19 [248842.078346] xhci_hcd 0000:0e:00.3: USB bus 3 deregistered [248842.078380] xhci_hcd 0000:0e:00.3: init 0000:0e:00.3 fail, -19
I have a System76 Galago Pro laptop which I mostly keep "docked" via usb-c, to a dongle that connects me to a 4k display, network, additional USB, and power. I use gnome and F34, and have configured sound to use HDMI/DisplayPort-Built-in-Audio (as opposed to speakers/built-in-audio). Once about every 3 or 4 times when I get back to my laptop after it's had time to power off the display, I get the attached image ("select audio device", see audio_select.png) superimposed over my password box. If I interact with it *in ANY way* (pick headphones or headset, or hit cancel, or escape, or anything), I get no working audio after logging back in! The only current workaround is to wait for the 20-30 seconds it takes to put the external display *back* to sleep, then hit another key or move the mouse to wake it back up. 90% of the time I no longer get the "select audio" dialog, can log in, and have working hdmi audio afterwards through the monitor's speakers. Doing a `dmesg` immediately after unlocking the screen yields: snd_hda_intel 0000:00:1f.3: refused to change power state from D3hot to D0 snd_hda_intel 0000:00:1f.3: CORB reset timeout#2, CORBRP = 65535 snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 I found a suggested "workaround" elsewhere (https://bbs.archlinux.org/viewtopic.php?id=269058) that recommends adding options snd_hda_intel power_save=0 to a .conf file under /etc/modprobe.d/ which I plan to try, but since this problem occurs only sporadically, it might take some time to decide whether the workaround, well, *works* :) Happy to try any other suggested fixes, run tests, or provide additional details about my configuration. Also happy to file a separate bug if this sounds unrelated (in which case I apologize to everyone for the noise).
Created attachment 1846457 [details] this shows up intermittently when external screen+audio woken up
(In reply to Gabriel Somlo from comment #8) > [...] > I found a suggested "workaround" elsewhere > (https://bbs.archlinux.org/viewtopic.php?id=269058) that recommends adding > > options snd_hda_intel power_save=0 > I've been running my laptop with the above line in `/etc/modprobe.d/workaround_snd_intel_power.conf` for the last 6 days, and (fingers crossed), haven't encountered the issue since. Hopefully the workaround helps others, and maybe even sheds some light on what the underlying problem could be.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.
still occurs on F36, same message logged to dmesg, applications trying to play audio now getting stuck (firefox/youtube spinning a circle, mpg123 hangs hard, can't be ctrl-c-ed).
Confirming still occurs for me with 5.18.10-200.fc36.x86_64. Seems to be triggered when switching from audio via the USB-C dock to audio on the internal speakers. Doesn't happen on every switch though, just sometimes.
ThinkPad T490s with kernel kernel-6.0.10-300.fc37.x86_64 in Fedora 37 connected to a dock station with a USB-C cable. [118790.406385] snd_hda_intel 0000:00:1f.3: CORB reset timeout#2, CORBRP = 65535 [118790.633764] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 [118790.856688] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 [118790.856723] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 [118816.159339] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 [118816.159361] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5
To add another device to the list and it's bugging me as well: Thinkpad T490 with kernel 6.0.12-300.fc37.x86_64 in Fedora 37 connected to a external monitor by HDMI. [36214.836126] snd_hda_intel 0000:00:1f.3: CORB reset timeout#2, CORBRP = 65535 [36215.063466] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 [36215.291316] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 [36215.291345] snd_hda_codec_realtek hdaudioC0D0: Unable to sync register 0x2b8000. -5 I've had pluged-in some headphones on the AUX and after coffee break sound was gone when I've unlocked the notebook again.
I'm seeg this on fc36 with a Dell Inspiron laptop. 3 times today. ugh. I'll try the modprobe suggestion above and report back yea or nea. ec 21 22:32:23 fedora-laptop kernel: snd_hda_intel 0000:00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040380 Dec 21 22:32:23 fedora-laptop kernel: snd_hda_intel 0000:00:1f.3: enabling device (0000 -> 0002) Dec 21 22:32:23 fedora-laptop kernel: snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915]) Dec 21 22:32:23 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC3204: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker Dec 21 22:32:23 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) Dec 21 22:32:23 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: hp_outs=1 (0x21/0x0/0x0/0x0/0x0) Dec 21 22:32:23 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: mono: mono_out=0x0 Dec 21 22:32:23 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: inputs: Dec 21 22:32:23 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Headset Mic=0x19 Dec 21 22:32:23 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Headphone Mic=0x1a Dec 21 22:32:23 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Internal Mic=0x12 Dec 22 09:35:07 fedora-laptop kernel: snd_hda_intel 0000:00:1f.3: CORB reset timeout#2, CORBRP = 65535 Dec 22 09:35:07 fedora-laptop kernel: snd_hda_codec_hdmi hdaudioC1D2: Unable to sync register 0x2f8100. -5 Dec 22 09:35:07 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 09:35:07 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 14:46:52 fedora-laptop kernel: snd_hda_intel 0000:00:1f.3: CORB reset timeout#2, CORBRP = 65535 Dec 22 14:46:52 fedora-laptop kernel: snd_hda_codec_hdmi hdaudioC1D2: Unable to sync register 0x2f8100. -5 Dec 22 14:46:53 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 14:46:53 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 14:50:11 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 14:50:11 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 14:54:12 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 14:54:12 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 15:44:17 fedora-laptop kernel: snd_hda_intel 0000:00:1f.3: CORB reset timeout#2, CORBRP = 65535 Dec 22 15:44:18 fedora-laptop kernel: snd_hda_codec_hdmi hdaudioC1D2: Unable to sync register 0x2f8100. -5 Dec 22 15:44:18 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 15:44:18 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 15:44:52 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5 Dec 22 15:44:52 fedora-laptop kernel: snd_hda_codec_realtek hdaudioC1D0: Unable to sync register 0x2b8000. -5
It still happens while 'undocking' on F38 - 6.2.7-300.fc38.x86_64 ThinkPad T14s Gen 1
There seems to be some regression after 6.2.5. I don't experience the issues when docking/undocking laptop with 6.2.5-300.fc38.x86_64. However, it's even causing some bigger issues with 6.2.6+. System being not responsive for a while and looses sound device.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
(In reply to Milan Zink from comment #18) > It still happens while 'undocking' on F38 - 6.2.7-300.fc38.x86_64 ThinkPad > T14s Gen 1 I am also seeing something similar on F38 on a ThinkPad T14s Gen 2 when I boot up with an external screen connected via HDMI: Apr 29 14:00:18 ThinkPad-T14s.fritz.box kernel: snd_hda_codec_realtek ehdaudio0D0: Unable to sync register 0x2b8000. -5 No audio works when that happens.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.