From: "Mantas M." <grawity@gmail.com>
To: alsa-devel@alsa-project.org
Subject: "hda-intel: azx_get_response timeout"
Date: Sun, 16 Dec 2012 18:04:17 +0200 [thread overview]
Message-ID: <kakre0$jpv$1@ger.gmane.org> (raw)
After upgrading to Linux 3.7 (on Arch Linux, x86_64), I've been getting
the following messages in dmesg:
> [Dec11 21:52] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x001f0500
> [ +1.006709] hda-intel: No response from codec, disabling MSI: last cmd=0x001f0500
> [ +1.006773] hda_intel: azx_get_response timeout, switching to single_cmd mode: last cmd=0x001f0500
This seems to happen when resuming from suspend-to-memory, and is new to
v3.7 – I haven't seen any such messages on any kernels I've used earlier
(between v3.0 and v3.6.9).
The device is:
> # lspci -v
> 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
> Subsystem: ASUSTeK Computer Inc. Device 1643
> Flags: bus master, fast devsel, latency 0, IRQ 22
> Memory at d5200000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [50] Power Management version 2
> Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
> Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
> Capabilities: [100] Virtual Channel
> Capabilities: [130] Root Complex Link
> Kernel driver in use: snd_hda_intel
Is there anything I can/should do about this?
--
Mantas Mikulėnas <grawity@gmail.com>
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next reply other threads:[~2012-12-16 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 16:04 Mantas M. [this message]
2012-12-17 9:58 ` "hda-intel: azx_get_response timeout" Takashi Iwai
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='kakre0$jpv$1@ger.gmane.org' \
--to=grawity@gmail.com \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.