NVIDIA HDMI audio errors after resume: snd_hda_intel: spurious response last cmd

Graphics / Linux Linux
,
1

Multiple people report that the NVIDIA drivers HDMI codec implementation starts malfunctioning after suspend/resume.

Currently known affected GPUs: NVIDIA GeForce GTX 1050, NVIDIA GeForce RTX 2080, NVIDIA GeForce RTX 2070, NVIDIA GeForce GTX 1660 Ti and possibly Geforce 680M.

Steps to reproduce: suspend, resume. That’s it.

dmesg messages:

On boot:

snd_hda_intel 0000:07:00.1: Disabling MSI

After resuming:

snd_hda_intel 0000:07:00.1: azx_get_response timeout, switching to polling mode: last cmd=0x001f000a
snd_hda_intel 0000:07:00.1: spurious response 0x0:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0x0:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0x0:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0x0:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0x3:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0x0:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0xc0:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0x0:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0x84:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: spurious response 0x1:0x0, last cmd=0x1f000a
snd_hda_intel 0000:07:00.1: azx_get_response timeout, switching to single_cmd mode: last cmd=0x005f0900
snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD buf size -1
snd_hdac_bus_update_rirb: 500 callbacks suppressed
snd_hda_intel 0000:07:00.1: spurious response 0x0:0x0, last cmd=0x870e00

The device is: 07:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller (rev a1)

More info here, bug 208829

Please fix.

1 Like
3

I confirm this on GeForce RTX 2070 Super and Quadro M2000M.

4

I’m gonna bump this indefinitely.

5

I have filed a bug 200656401 internally for reference and can recreate issue locally.

Please let me know if possible the last working driver.

6

Thank you!

I can’t say which drivers worked. I simply don’t remember.

7

No worries, thanks for the information.

1 Like
8

I’m still experiencing this issue with the latest driver (450.66).

Here’s my config:

  • GPU: Asus Phoenix GeForce GTX 1650 Super
  • MB: Asus ROG STRIX X570-E Gaming (latest BIOS)
  • kernel: 5.8.11-200.fc32.x86_64

Has there been any progress on the issue? (Thanks!)

9

This issue is still under investigation.
I will inform once it is fixed.

1 Like
10

Keep us posted please and keep NVIDIA developers busy. :-)

11

Any updates on this? Still reproducible with 455.38

12

Sorry for late reply, we are debugging issue currently and working towards fix.
Will let you know once we have fix available.

1 Like
13

Hello! Reproducible here. A lot of

Feb 13 22:15:07 leonidas kernel: snd_hdac_bus_update_rirb: 133 callbacks suppressed
Feb 13 22:15:07 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa70e00
Feb 13 22:15:07 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa70e00
Feb 13 22:15:07 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x573500
Feb 13 22:15:07 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x5f0700
Feb 13 22:15:07 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x40:0x0, last cmd=0x570700
Feb 13 22:15:07 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x570700
Feb 13 22:15:08 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa20000
Feb 13 22:15:08 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa20000
Feb 13 22:15:08 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Feb 13 22:15:08 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x233:0x0, last cmd=0x1f0500
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x473500
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x4f0015
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x473501
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x470700
Feb 13 22:15:42 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x470700
Feb 13 22:15:54 leonidas kernel: snd_hdac_bus_update_rirb: 185 callbacks suppressed
Feb 13 22:15:54 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa70e00
Feb 13 22:15:54 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa70e00
Feb 13 22:15:54 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x3:0x0, last cmd=0x5f0700
Feb 13 22:15:54 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x570700
Feb 13 22:15:54 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x40:0x0, last cmd=0x570700
Feb 13 22:15:54 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x570700
Feb 13 22:15:55 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa20000
Feb 13 22:15:55 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa20000
Feb 13 22:15:55 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0x1f0500
Feb 13 22:15:55 leonidas kernel: snd_hda_intel 0000:01:00.1: spurious response 0x233:0x0, last cmd=0x1f0500

here on Archlinux 5.10.14-arch1-1 with 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] (rev a1) on Gigabyte GA-MA790GP-DS4Hwith nvidia 460.39-6 installed from repos.

Just changing in pavucontrol the GP107GL High Definition Audio Controller from Digital Stereo (HDMI 2) Output to Off and back again after suspend prints a lot of spurious response messages.

14

2.0b hdmi cable being used.? I dont see the nvidia issue.
Your MBoard is 10 years old no? It had its fair share of issues if you check the Product Errata Report. Waste of a good GPU w/ 2.0b HDMI PCi-e3vx16 on sharded 2vPCI-e.
Wheres the intel driver come into the mix?
Realtek ALC889A audio driver for the Mboard. SouthBridge Chipset.
https://github.com/torvalds/linux/search?q=ALC889

LOOKATME!
https://help.ubuntu.com/community/SoundTroubleshootingGuide#Ae_.28.28Make_NVIDIA_HDMI_Audio_work.29

  1. North Bridge: AMD 790GX
  2. South Bridge: AMD SB750
    https://github.com/torvalds/linux/search?q=ALC889

GoodLuck

15

username.murphy Probably you are right. Thank you for your time!

16
  • When you run lspci and then a different backended hardware identification utility, are there differing naming anomolies.???

Checked against the exact hardware spec’d? as per Manufacturer whitepaper.?

After every install, kernel,firmware,hardware, driver change or just because …biannually;

  • I run update-pciids with the latest pci.ids.(and the rest)
    So the hardware is identified correctly.

Is the correct hardware audio codec pinned on the mainboard and or in the bios?
the “driver can be incorrectly chosen by the system codec?”

What about the correct dma mask/ buff setup.?

Is nvidia choking(64Mb or Higher) and the kernel is defaulting to intel??

https://www.kernel.org/doc/html/latest/PCI/index.html

https://www.kernel.org/doc/html/latest/sound/hd-audio/models.html

https://help.ubuntu.com/community/SoundTroubleshootingGuide#Ae_.28.28Make_NVIDIA_HDMI_Audio_work.29

Try running pciutils. install pci.ids aswell. check you stsem codec

17

Hi, Facing similar error logs in kernel. PFA the log file and system information below.

This happened when installing Arch linux pn VM using Virualbox. The desktop environment got hanged completely and had login to tty session and restart xfce.

SYSTEM_INFO

System:    Kernel: 5.10.15-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: Xfce 4.16.0 tk: Gtk 3.24.24 wm: xfwm4 
       dm: LightDM Distro: Manjaro Linux 
CPU:       Info: 6-Core model: Intel Core i7-9750H bits: 64 type
Graphics:  Device-1: NVIDIA TU106M [GeForce RTX 2060 Mobile] vendor: Lenovo driver: nvidia v: 460.39 bus ID: 01:00.0 
       chip ID: 10de:1f11 
       Display: x11 server: X.Org 1.20.10 driver: loaded: nvidia resolution: 1920x1080~144Hz s-dpi: 96 
       OpenGL: renderer: GeForce RTX 2060/PCIe/SSE2 v: 4.6.0 NVIDIA 460.39 direct render: Yes 
Audio:     Device-1: Intel Cannon Lake PCH cAVS vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
       chip ID: 8086:a348 
       Device-2: NVIDIA TU106 High Definition Audio vendor: Lenovo driver: snd_hda_intel v: kernel bus ID: 01:00.1 
       chip ID: 10de:10f9 
       Sound Server: ALSA v: k5.10.15-1-MANJARO

nvidia_error.log (13.1 KB)

18

I’m experiencing the same problems after wakeup with driver NVIDIA-Linux-x86_64-460.56 on a PC with 2 GT 710 and linux kernel 5.10. Both sound outputs are working fine after boot. But after resume, the sound device are not accessible anymore (eror messages “spurious response” in kernel log). Reboot or shutting down the graphical interface, unloading nvidia module and reloading it helps.

I think the problem didn’t occur with NVIDIA-Linux-x86_64-460.32.03. I will downgrade and try to verify that.

Please let me know if you need further information.

19

460.32.03 works fine indeed :-)

20

I recently started having this problem with my GT 1030. I’m using the driver in Linux Mint’s repository, package nvidia-driver-460 version 460.39-0ubuntu0.20.04.1.
Strangely enough, I have another problem where the screen goes completely black depending on the content being displayed (happens often on YouTube), and as a workaround I coded a simple script bound to a shortcut key that changes the mode from 60Hz to 30Hz, and then back, which remediates the issue. Today I found out that it also makes the sound output work again. The script:

#!/bin/bash
xrandr --output HDMI-0 --mode 1920x1080 --rate 30
echo press enter to get back to FHD 60hz
read
xrandr --output HDMI-0 --mode 1920x1080 --rate 60
1 Like
21

2.0b hdmi cable being used.? I dont see the nvidia issue.

The seller reports it to be hdmi 2.0 (no ‘a’ nor ‘b’). How does the cable used affect spurious response message from kernel?

Wheres the intel driver come into the mix?

It is using hardware with nvidia in the name, below is the lspci. Should a different driver be used? I guess this could be the manufacturer ZOTAC fault, because he manufactured sound stuff, something like that is possible?

No, why would there be? I added lspci -v as attachment.lspci.txt (8.3 KB) dmesg_without_audit.txt (1.1 MB)

The kernel lines are snd_hda_intel 0000:01:00.1: spurious response 0x0:0x0, last cmd=0xa70e00 so I think the problem is with 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) - both have 01:00.1 number - right?

I also checked to be sure - the messages sporious response also show up when the motherboard sound card is turned off in bios.

Checked against the exact hardware spec’d?

What is or should be or should I checked against? How would I check it? You mean lspci output? It looks like this for ages, I do not see anything interesting there.

I see nvidia is here: /h-node.org/soundcards/view/en/2159/NVIDIA-Corporation-GP107GL-High-Definition-Audio-Controller–rev-a1- , looks the same to what I have.

I run update-pciids with the latest pci.ids.(and the rest)
So the hardware is identified correctly.

Och, cool. I did too.

Is the correct hardware audio codec pinned on the mainboard and or in the bios?

I do not have an option to “pin audio codec” in bios, there are no switches on motherboard that I know of. I am not versed in this topic, probably I do not understand the question - would like to clarify how to check it?

What about the correct dma mask/ buff setup.?

I do not know how to check it.

Is nvidia choking(64Mb or Higher) and the kernel is defaulting to intel??

Nvidia is known to have problems in low memory situations. I have few gb of memory free. I do not understand what does “kernel defaulting to intel” mean - I think this is when you use intel cpu when the cpu has also graphic card with it. I have AMD and the motherboard graphic card is turned off, there is only nvidia and no intel in sight. free reports 2.5Gi free ram, nvidia-smi shows 463MiB / 4039MiB in Memory-Usage box.

/www.kernel.org/doc/html/latest/PCI/index.html

/www.kernel.org/doc/html/latest/sound/hd-audio/models.html)

Well, NVIDIA driver is closed source. TBH, dunno what to do with these links. Browsing kernel sources, the message seems to come from hdac_controller.c#L226.

/help.ubuntu.com/community/SoundTroubleshootingGuide#Ae_.28.28Make_NVIDIA_HDMI_Audio_work.29

The audio works - quite well and I experience no problems with HDMI audio, pulseaudio is working fine with it. The problem are these messages from kernel - I do not know what they mean and how to interpret them.