From: Joe Perches <joe@perches.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [RFC PATCH] hda_intel: ratelimit "spurious response" message
Date: Tue, 19 Nov 2013 00:40:07 -0800 [thread overview]
Message-ID: <1384850407.17783.17.camel@joe-AO722> (raw)
In-Reply-To: <s5ha9h6qhjb.wl%tiwai@suse.de>
On Fri, 2013-11-15 at 07:56 +0100, Takashi Iwai wrote:
> At Thu, 14 Nov 2013 09:52:34 -0800,
> Joe Perches wrote:
> >
> > > Hrm, the codec proc for the analog audio isn't seen here.
> > > Maybe the codec communication was already screwed up at this point.
> > >
> > > Can you have a good output by any chance (showing the right contents
> > > of /proc/asound/card1/codec#*)?
> >
> > Using the linux version I've normally used:
> >
> > $ cat /proc/version
> > Linux version 3.11.0-031100rc2-generic (apw@gomeisa) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #201307211535 SMP Sun Jul 21 19:45:33 UTC 201
> >
> > $ cat /proc/asound/card1/codec#0
> > Codec: Realtek ALC271X
>
> So this codec was detected properly. Judging from your patch
> description, the verb triggering the stall (0x170500) was about the
> power up to D0 for AFG node. Did the sound work even after the flood
> of the messages?
>
> The problem might be also not a stall but a bogus CORB/RIRB pointer.
> Try the first patch, and give the first "spurious response" message.
> Now it shows rp and wp values, and we might see a pattern in them to
> trigger the spurious message (e.g. wp is always same value).
>
> Also, to be sure, try the second patch, too. It disables the access
> to some vendor-specific verbs.
Hi again.
I'm not ignoring you.
I've rebuilt the kernel with these patches and
I'm waiting for the messages to show up again.
The only times I've seen them have been after
hibernating and resuming.
I've done several hibernate/restart cycles but
haven't had the messages emitted in the logs yet.
cheers, Joe
next prev parent reply other threads:[~2013-11-19 8:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 19:55 [RFC PATCH] hda_intel: ratelimit "spurious response" message Joe Perches
2013-11-07 20:23 ` Takashi Iwai
2013-11-07 20:28 ` Joe Perches
2013-11-08 10:59 ` Takashi Iwai
2013-11-09 4:41 ` Joe Perches
2013-11-14 17:28 ` Takashi Iwai
2013-11-14 17:52 ` Joe Perches
2013-11-15 6:34 ` Takashi Iwai
2013-11-15 6:56 ` Takashi Iwai
2013-11-19 8:40 ` Joe Perches [this message]
2013-11-19 8:57 ` 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=1384850407.17783.17.camel@joe-AO722 \
--to=joe@perches.com \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).