From: Nigel Kukard <nkukard@lbsd.net>
To: Dave Jones <davej@redhat.com>, Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org
Subject: Re: SATA problems
Date: Tue, 19 Jun 2007 04:57:07 +0000 [thread overview]
Message-ID: <46776223.3050402@lbsd.net> (raw)
In-Reply-To: <20070618200703.GB13344@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 599 bytes --]
> >
> > > > 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*
>
> 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?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-06-19 4:57 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 12:36 SATA problems 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 [this message]
2007-08-30 9:24 ` Nigel Kukard
2007-09-10 9:02 ` Andrew Morton
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=46776223.3050402@lbsd.net \
--to=nkukard@lbsd.net \
--cc=davej@redhat.com \
--cc=jeff@garzik.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;
as well as URLs for NNTP newsgroup(s).