From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: John Bradford <john@grabjohn.com>
Cc: Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
Erik van Engelen <Info@vanE.nl>,
linux-kernel <linux-kernel@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Errors on 2th ide channel of promise ultra100 tx2
Date: Fri, 27 Feb 2004 16:30:43 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.58L.0402271629430.19209@logos.cnet> (raw)
In-Reply-To: <200402271820.i1RIKVLb000744@81-2-122-30.bradfords.org.uk>
On Fri, 27 Feb 2004, John Bradford wrote:
> > > hdh: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hdh: task_no_data_intr: error=0x04 { DriveStatusError }
> > > hdh: 2128896 sectors (1090 MB) w/83KiB Cache, CHS=2112/16/63
> >
> > Haven't got a clue about these "status=0x51" and "error=0x04". Anyone?
>
> Basically, the errors mean what they say - the drive is in an error
> state, (received an unrecognised command), but is ready for further
> operation.
Received an unrecognised command from the kernel? What can cause that?
Thanks!
next prev parent reply other threads:[~2004-02-27 18:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 10:52 Erik van Engelen
2004-02-27 18:46 ` Marcelo Tosatti
2004-02-27 18:20 ` John Bradford
2004-02-27 19:30 ` Marcelo Tosatti [this message]
2004-02-27 19:01 ` Alan Cox
2004-02-27 20:14 ` Bartlomiej Zolnierkiewicz
2004-02-27 22:44 ` Erik Andersen
2004-02-28 1:20 ` Bartlomiej Zolnierkiewicz
2004-02-28 1:26 ` Erik Andersen
2004-02-28 16:01 ` Alan Cox
2004-02-28 20:25 ` John Bradford
2004-02-27 22:51 ` Marcelo Tosatti
2004-02-28 0:04 ` Bartlomiej Zolnierkiewicz
2004-02-27 22:08 ` Erik Andersen
2004-02-27 19:50 ` Rene Herman
2004-02-28 12:13 ` Erik van Engelen
2004-03-03 8:24 ` Erik van Engelen
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=Pine.LNX.4.58L.0402271629430.19209@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=Info@vanE.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=john@grabjohn.com \
--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®