From: "Andrew Lyon" <andrew.lyon@gmail.com>
To: bbee <bumble.bee@xs4all.nl>
Cc: "Tejun Heo" <htejun@gmail.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0) r0xj0
Date: Thu, 4 Jan 2007 01:01:46 +0000 [thread overview]
Message-ID: <f4527be0701031701q4eaafe63sfd5dcbbfddc89f51@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701031733001.1969@dolores.legate.org>
On 1/3/07, bbee <bumble.bee@xs4all.nl> 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
next prev parent reply other threads:[~2007-01-04 1:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 2:12 Andrew Lyon
2006-12-28 3:30 ` Tejun Heo
2006-12-31 21:39 ` Andrew Lyon
2007-01-03 1:44 ` bbee
2007-01-03 2:25 ` Tejun Heo
2007-01-03 3:38 ` bbee
2007-01-03 4:15 ` Tejun Heo
2007-01-03 16:50 ` bbee
2007-01-04 1:01 ` Andrew Lyon [this message]
2007-01-04 3:18 ` Tejun Heo
2007-01-04 3:16 ` Tejun Heo
[not found] ` <f4527be0701030825m3e07a38dm67d2c21fd25b1978@mail.gmail.com>
2007-01-03 16:26 ` Fwd: " Andrew Lyon
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=f4527be0701031701q4eaafe63sfd5dcbbfddc89f51@mail.gmail.com \
--to=andrew.lyon@gmail.com \
--cc=bumble.bee@xs4all.nl \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--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®