FS#64515 - [linux] linux-5.3.11 causes backtrace with snd_hda_intel

Attached to Project: Arch Linux
Opened by David C. Rankin (drankinatty) - Friday, 15 November 2019, 18:57 GMT
Last edited by Jelle van der Waa (jelly) - Thursday, 14 September 2023, 17:50 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

Upon reboot after update to linux-5.3.11 a backtrace was generated regarding the snd_hda_codec. This is the first time this has occurred. The kernel is untainted, so there isn't 3rd party software involved.

I'm not quite sure what to make of it or what changed in the kernel that could be related to this issue. The backtrace is attached.

   kernel_5.3.11_snd_hda_intel.t... (5.5 KiB)
This task depends upon

Closed by  Jelle van der Waa (jelly)
Thursday, 14 September 2023, 17:50 GMT
Reason for closing:  Deferred
Additional comments about closing:  Old kernel, please retry with the latest
Comment by loqs (loqs) - Friday, 15 November 2019, 23:57 GMT
There were multiple alsa changes in 5.3.11 [1]
If you downgrade the kernel to 5.3.10 is the issue no longer present?

[1] https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.3.11
Comment by David C. Rankin (drankinatty) - Saturday, 16 November 2019, 05:51 GMT
Well, it actually started with 5.3.10, 5.3.8 was fine. For example in the journal for 2 boots ago:

Nov 01 10:57:23 phoinix kernel: Linux version 5.3.8-arch1-1 (linux@archlinux) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT @1572357769
<snip>
Nov 01 10:57:30 phoinix kernel: snd_hda_intel 0000:00:07.0: spurious response 0x0:0x0, last cmd=0x1af0900

(no problem)

Then with 5.3.10:

Nov 12 08:06:34 phoinix kernel: Linux version 5.3.10-arch1-1 (linux@archlinux) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Sun, 10 Nov 2019 11:29:38 +0000
<snip>
Nov 12 08:06:43 phoinix kernel: snd_hda_intel 0000:00:07.0: azx_get_response timeout, switching to polling mode: last cmd=0x023b0007

(same backtrace)

It almost looks like the snd_hda_intel init resulted in a "snd_hda_intel 0000:00:07.0: spurious response 0x0:0x0..." up though 5.3.8 and then beginning with 5.3.10 the same thing is interpreted as "snd_hda_intel 0000:00:07.0: azx_get_response timeout..." They may be different, but there are no other reports in the journal for 5.3.8, but beginning with 5.3.10 it provides a backtrace. Which is handled fine, its just strange to see in the journal.
Comment by David C. Rankin (drankinatty) - Saturday, 16 November 2019, 06:04 GMT
Wait, I went back through the journal to May, and the first `snd_hda_intel 0000:00:07.0: azx_get_response timeout,` and backtrace occurred:

Oct 16 16:30:18 phoinix kernel: Linux version 5.3.6-arch1-1-ARCH (builduser@heftig-3261850) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Fri Oct 11 18:28:05 UTC 2019

So it was actually with 5.3.6. I can't tell if this is a kernel change in the way the sound card response is handled or the sound card itself. Every boot has the `snd_hda_intel 0000:00:07.0: spurious response 0x0:0x0` logged, it's only the 5.3.6, 5.3.10 and 4.3.11 boots that give the backtrace. (I only reboot on kernel update and have all kernels except 5.3.9 for some reason -- .9 and .10 must have come close together)
Comment by Buggy McBugFace (bugbot) - Tuesday, 08 August 2023, 19:11 GMT
This is an automated comment as this bug is open for more then 2 years. Please reply if you still experience this bug otherwise this issue will be closed after 1 month.

Loading...