From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757125Ab3KHK7N (ORCPT ); Fri, 8 Nov 2013 05:59:13 -0500 Received: from cantor2.suse.de ([195.135.220.15]:39108 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752946Ab3KHK7M (ORCPT ); Fri, 8 Nov 2013 05:59:12 -0500 Date: Fri, 08 Nov 2013 11:59:11 +0100 Message-ID: From: Takashi Iwai To: Joe Perches Cc: alsa-devel , LKML Subject: Re: [RFC PATCH] hda_intel: ratelimit "spurious response" message In-Reply-To: <1383856098.9263.28.camel@joe-AO722> References: <1383854115.9263.21.camel@joe-AO722> <1383856098.9263.28.camel@joe-AO722> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka) FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/24.3 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 > > > > 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