From: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: John Bradford <john@grabjohn.com>,
Erik van Engelen <Info@vanE.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Errors on 2th ide channel of promise ultra100 tx2
Date: Fri, 27 Feb 2004 21:14:23 +0100 [thread overview]
Message-ID: <200402272114.23108.bzolnier@elka.pw.edu.pl> (raw)
In-Reply-To: <1077908499.29713.19.camel@dhcp23.swansea.linux.org.uk>
On Friday 27 of February 2004 20:01, Alan Cox wrote:
> On Gwe, 2004-02-27 at 19:30, Marcelo Tosatti wrote:
> > > > 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?
>
> Our early setup/probing code in 2.4.x at least may send stuff that very
> very old disks don't understand. Its arguably a bug in the ident parsing
> but it shouldnt ever be harmful
ide-disk.c sends WIN_READ_NATIVE_MAX_{EXT} without checking
if HPA feature set is supported, this is fixed in 2.6.x for a long time.
We need 2.4<->2.6 IDE sync monkey... a really smart one...
Cheers,
Bartlomiej
next prev parent reply other threads:[~2004-02-27 20:07 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
2004-02-27 19:01 ` Alan Cox
2004-02-27 20:14 ` Bartlomiej Zolnierkiewicz [this message]
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=200402272114.23108.bzolnier@elka.pw.edu.pl \
--to=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 \
--cc=marcelo.tosatti@cyclades.com \
/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®