From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932230AbXADBBu (ORCPT ); Wed, 3 Jan 2007 20:01:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932229AbXADBBu (ORCPT ); Wed, 3 Jan 2007 20:01:50 -0500 Received: from ug-out-1314.google.com ([66.249.92.169]:47611 "EHLO ug-out-1314.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932230AbXADBBr (ORCPT ); Wed, 3 Jan 2007 20:01:47 -0500 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=UggyFkFwWD9xNrQPWJ17K/gBK0TNnyrMUylM2iSLcJzjueWlwfvsmWJCEQrlxACxe5cKWQqVB52rwmfh8qW7+dIFweiRAnbYOaM7wkassGLb3+p3ydd9mZLyTc3/MyuqM5qj7IsNntEP7V4QWHDejla3ArT3C6N8PZO0BvVRJvA= Message-ID: Date: Thu, 4 Jan 2007 01:01:46 +0000 From: "Andrew Lyon" To: bbee Subject: Re: ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0) r0xj0 Cc: "Tejun Heo" , linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <45933A53.1090702@gmail.com> <459B140C.1060401@gmail.com> <459B2DEA.8080202@gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 1/3/07, bbee wrote: > On Wed, 3 Jan 2007, Tejun Heo wrote: > > bbee wrote: > >>> Yeap, I have major issues with SDB FISes which contains spurious > >>> completions but most other spurious interrupts shouldn't be dangerous > >>> and I haven't seen spurious completions for quite some time, so I was > >>> thinking either removing the message or printing it only on SDB FIS > >>> containing spurious completions. > >>> > >>> But, Andrew Lyon *is* reporting spurious completions. Now I just wanna > >>> update those printks such that more info is reported only on spurious > >>> SDB FISes. > >> > >> That would certainly help verify that I'm having the exact same problem, > >> since Andrew didn't say anything about his drive going offline. > > > > Okay. > > Sorry, I thought you meant you would need to update it *further*. I applied > the patch you gave to Andrew with this result so far: > > $ dmesg | grep -A1 "spurious interrupt" > ata1: spurious interrupt (irq_stat 0x8 active_tag 0xfafbfcfd sactive 0x0) > ata1: issue=0x0 SAct=0x0 SDB_FIS=004040a1:00000008 > -- > ata1: spurious interrupt (irq_stat 0x8 active_tag 0xfafbfcfd sactive 0x0) > ata1: issue=0x0 SAct=0x0 SDB_FIS=004040a1:00000001 > > No luck yet triggering the exception. > > On Wed, 3 Jan 2007, Andrew Lyon wrote: > > Alan said he was going to add the drive to a blacklist he was > > maintaining for NCQ, perhaps that has been done in kernel 2.6.19, I > > dont know as I am still running 2.6.18. > > > > Perhaps the WD Raptor drive that I have does have lousy NCQ and that > > explains both the poor performance and the spurious interrupts. > > Blacklisting NCQ on the drive(s) for all controllers might be ill advised, > since it could be a JMicron-specific issue (or ahci-specific, since the > person in the thread I referenced had a different ahci controller..). > Either that, or both our drive models have "lousy NCQ".. > > > Thanks, > > bbee > Is there anything more I can do to assist? I plan to upgrade to 2.6.19/latest at the weekend, let me know if there is anything more i can do. Andy