At Mon, 19 Nov 2012 15:18:45 +0100, Julian Wollrath wrote:
Hm, then something screwed up the communication...
At which moment do you see such a message? In other words, how to trigger the bug?
I suspend my system to ram or to disk. Then I resume it, everthing comes up again and then, aprrox 4s after the resume was initiated, the spurious response messages hit the dmesg for approx. 0.07s as you can see in my first message. Hopefully this answer the question.
Hm, just got some messages, which did not appear before: [ 244.497999] snd_hda_intel 0000:00:14.2: wake-up capability disabled by ACPI [ 244.498063] snd_hda_intel 0000:00:14.2: enabling device (0000 -> 0002)
Do you have CONFIG_PM_RUNTIME=y? If yes, any difference when turn it off?
Also, apply the patch below so that we can see which device is actually stalling.
thanks,
Takashi
--- From: Takashi Iwai tiwai@suse.de Subject: [PATCH] ALSA: hda - Print PCI device name at "spurious message" warnings
... to make it clear to see from which device it comes.
Signed-off-by: Takashi Iwai tiwai@suse.de --- sound/pci/hda/hda_intel.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/sound/pci/hda/hda_intel.c b/sound/pci/hda/hda_intel.c index d327ffa..b6ffdd8 100644 --- a/sound/pci/hda/hda_intel.c +++ b/sound/pci/hda/hda_intel.c @@ -832,8 +832,9 @@ static void azx_update_rirb(struct azx *chip) smp_wmb(); chip->rirb.cmds[addr]--; } else - snd_printk(KERN_ERR SFX "spurious response %#x:%#x, " + snd_printk(KERN_ERR SFX "%s: spurious response %#x:%#x, " "last cmd=%#08x\n", + pci_name(chip->pci), res, res_ex, chip->last_cmd[addr]); }