From: Takashi Iwai <tiwai@suse.de>
To: Joe Perches <joe@perches.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] hda_intel: ratelimit "spurious response" message
Date: Fri, 08 Nov 2013 11:59:11 +0100 [thread overview]
Message-ID: <s5hwqkjrwg0.wl%tiwai@suse.de> (raw)
In-Reply-To: <1383856098.9263.28.camel@joe-AO722>
At Thu, 07 Nov 2013 12:28:18 -0800,
Joe Perches wrote:
>
> On Thu, 2013-11-07 at 21:23 +0100, Takashi Iwai wrote:
> > At Thu, 07 Nov 2013 11:55:15 -0800,
> > Joe Perches wrote:
> > >
> > > dmesg here has a 100+ consecutive lines of:
> > >
> > > [ 1464.219446] hda-intel 0000:00:14.2: spurious response 0x0:0x0, last cmd=0x170500
> > > [ 1464.219451] hda-intel 0000:00:14.2: spurious response 0x0:0x0, last cmd=0x170500
> > > [ 1464.219454] hda-intel 0000:00:14.2: spurious response 0x0:0x0, last cmd=0x170500
> > > ...
> > >
> > > Ratelimit the message to reduce the dmesg log noise.
> > >
> > > Coalesce the format while at it.
> > >
> > > Signed-off-by: Joe Perches <joe@perches.com>
> >
> > Thanks, applied.
> >
> > BTW, which hardware shows this problem?
> > I'm interested rather in that...
>
> It's a little Acer netbook AO725
>
> # lspci -v -v -s0:14.2
> 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01)
> Subsystem: Acer Incorporated [ALI] Device 0740
Could you give alsa-info.sh output (maybe better to get it after
applying your patch)? It'll show more comprehensive information.
thanks,
Takashi
prev parent reply other threads:[~2013-11-08 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 19:55 Joe Perches
2013-11-07 20:23 ` Takashi Iwai
2013-11-07 20:28 ` Joe Perches
2013-11-08 10:59 ` Takashi Iwai [this message]
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=s5hwqkjrwg0.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®