From: "Andrew Lyon" <andrew.lyon@gmail.com>
To: "Kernel Mailing List" <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org
Subject: ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0) r0xj0
Date: Thu, 28 Dec 2006 02:12:48 +0000 [thread overview]
Message-ID: <f4527be0612271812p7282de31j98462aebde16e5a1@mail.gmail.com> (raw)
Hi,
My system is gigabyte ds3 motherboard with onboard SATA JMicron
20360/20363 AHCI Controller (rev 02), drive connected is WDC
WD740ADFD-00 20.0, I am running 2.6.18.6 32 bit, under heavy i/o I get
the following messaegs:
ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0)
ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0)
ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0)
ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0)
ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0)
ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0)
ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0)
ata1: spurious interrupt (irq_stat 0x8 active_tag -84148995 sactive 0x0)
Is this condition dangerous?
I plan to upgrade to 2.6.19 soon as I have problems with a sata dvd
writer but I have to wait for a driver that I need to catch up, this
system cannot be down for long as it runs mythtv.
Andy
next reply other threads:[~2006-12-28 2:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-28 2:12 Andrew Lyon [this message]
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
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=f4527be0612271812p7282de31j98462aebde16e5a1@mail.gmail.com \
--to=andrew.lyon@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®