From: Andrew Morton <akpm@linux-foundation.org>
To: Nigel Kukard <nkukard@lbsd.net>
Cc: Dave Jones <davej@redhat.com>, Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: SATA problems
Date: Mon, 10 Sep 2007 02:02:43 -0700 [thread overview]
Message-ID: <20070910020243.1101cf7a.akpm@linux-foundation.org> (raw)
In-Reply-To: <46D68CC2.3030206@lbsd.net>
On Thu, 30 Aug 2007 09:24:18 +0000 Nigel Kukard <nkukard@lbsd.net> wrote:
> Hrmmm,
>
> >> >
> >> > > > Jun 14 07:55:52 nigel-m2v kernel: ATA: abnormal status 0x7F on port
> >> > > > 0x0001c807
> >> > > > Jun 14 07:55:52 nigel-m2v kernel: ATA: abnormal status 0x7F on port
> >> > > > 0x0001c807
> >> >
> >> > Unrelated to the other error, but I've been meaning to ask for a while..
> >> > If this is 'abnormal', why does every SATA box I've seen do it?
> >>
> >> *crickets*
chirp, chirp.
> >> Should we check for this case explicitly, and not print this?
> >>
> >>
> >>
> > After I get the above errors, my entire SATA bus crashes and I need to
> > hard reset the box ... not sure we can just ignore the errors?
> >
> >
>
> Appears even with the patch provided a few months ago I'm getting
> freezes. Replaced the HDD & all cables, same errors ... especially
> whilst doing heavy IO.
>
> Can anyone shed some light?
>
I think I was told last week that copying the appropriate mailing list will
at least prevent chirping, so let's try that.
Original thread here: http://lkml.org/lkml/2007/6/14/154
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:c9:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/133
> ata2: EH complete
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:c9:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/133
> ata2: EH complete
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:c9:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/133
> ata2: EH complete
> ata2.00: limiting speed to UDMA/100:PIO4
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:c9:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/100
> ata2: EH complete
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:c9:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/100
> ata2: EH complete
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:c9:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/100
> sd 3:0:0:0: SCSI error: return code = 0x08000002
> sda: Current [descriptor]: sense key=0xb
> ASC=0x0 ASCQ=0x0
> Descriptor sense data with sense descriptors (in hex):
> 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00
> 00 00 00 00
> end_request: I/O error, dev sda, sector 30132639
> ata2: EH complete
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:ca:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/100
> ata2: EH complete
> ata2.00: limiting speed to UDMA/33:PIO4
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:ca:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/33
> ata2: EH complete
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:ca:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/33
> ata2: EH complete
> ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
> ata2.00: cmd c8/00:00:9f:ca:cb/00:00:00:00:00/e1 tag 0 cdb 0x0 data
> 131072 in
> res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
> ata2: soft resetting port
> ATA: abnormal status 0x7F on port 0x0001c807
> ATA: abnormal status 0x7F on port 0x0001c807
> ata2.00: configured for UDMA/33
> ata2: EH complete
>
>
>
next prev parent reply other threads:[~2007-09-10 9:03 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 12:36 Nigel Kukard
2007-06-14 16:21 ` Jeff Garzik
2007-06-14 18:28 ` Dave Jones
2007-06-18 20:07 ` Dave Jones
2007-06-19 4:57 ` Nigel Kukard
2007-08-30 9:24 ` Nigel Kukard
2007-09-10 9:02 ` Andrew Morton [this message]
2007-09-13 8:55 ` Tejun Heo
[not found] <8vX5T-4hg-5@gated-at.bofh.it>
[not found] ` <8w0n1-15u-27@gated-at.bofh.it>
2007-06-14 16:58 ` Nigel Kukard
2007-06-14 17:33 ` Jeff Garzik
2007-06-18 8:05 ` Nigel Kukard
-- strict thread matches above, loose matches on Subject: below --
2007-01-02 14:08 Pablo Sebastian Greco
2007-01-03 12:20 ` Tejun Heo
2007-01-03 15:08 ` Pablo Sebastian Greco
2007-01-04 5:02 ` Tejun Heo
2007-01-04 13:17 ` Pablo Sebastian Greco
2007-01-05 3:15 ` Pablo Sebastian Greco
2007-01-08 2:23 ` Tejun Heo
2007-01-08 2:49 ` Jeff Garzik
2007-01-08 12:22 ` Pablo Sebastian Greco
2007-01-09 22:58 ` Pablo Sebastian Greco
2007-01-10 1:55 ` Tejun Heo
2007-01-23 17:45 ` Pablo Sebastian Greco
2007-01-24 1:54 ` Tejun Heo
2007-02-17 12:49 ` Marcus Haebler
2007-02-17 16:47 ` Pablo Sebastian Greco
2007-02-20 14:35 ` Tejun Heo
2007-02-20 16:24 ` Pablo Sebastian Greco
2007-02-21 3:08 ` Tejun Heo
2007-02-21 15:18 ` Pablo Sebastian Greco
2007-02-21 0:55 ` Marcus Haebler
2007-02-21 3:55 ` Tejun Heo
2007-02-21 5:57 ` Marcus Haebler
2007-02-21 6:24 ` Marcus Haebler
2007-02-21 7:25 ` Paul Rolland
2007-02-21 13:04 ` Marcus Haebler
2004-02-11 17:52 SATA Problems Dott. Surricani
2004-02-11 18:08 ` Armen Kaleshian
[not found] ` <402A72F0.9030005@surricani.cjb.net>
2004-02-11 18:25 ` Armen Kaleshian
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=20070910020243.1101cf7a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nkukard@lbsd.net \
/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
Powered by JetHome