From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Alexander Fieroch <fieroch@web.de>,
Alexey Dobriyan <adobriyan@gmail.com>,
Michael Thonke <iogl64nx@gmail.com>,
linux-kernel@vger.kernel.org, Jesper Juhl <jesper.juhl@gmail.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
axboe@suse.de,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Natalie.Protasevich@unisys.com, Andrew Morton <akpm@osdl.org>,
Parag Warudkar <kaernel-stuff@comcast.net>
Subject: Re: PROBLEM: "drive appears confused" and "irq 18: nobody cared!"
Date: Mon, 1 Aug 2005 21:28:54 +0200 [thread overview]
Message-ID: <58cb370e050801122831a97873@mail.gmail.com> (raw)
In-Reply-To: <m3oe8h7978.fsf@defiant.localdomain>
On 8/1/05, Krzysztof Halasa <khc@pm.waw.pl> wrote:
> Alexander Fieroch <fieroch@web.de> writes:
>
> > hdb: media error (bad sector): status=0x51 { DriveReady SeekComplete Error }
> > hdb: media error (bad sector): error=0x30 { LastFailedSense=0x03 }
> > ide: failed opcode was: unknown
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > end_request: I/O error, dev hdb, sector 1306960
> > Buffer I/O error on device hdb, logical block 326740
>
> BTW: I believe this used to point to something useful rather than
> to "unknown opcode". Is it just a bug or does it really not know
> the opcode?
For regular FS requests it really doesn't know ATA opcode...
(on the TODO)
next prev parent reply other threads:[~2005-08-01 19:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 22:24 [2.6.12rc4] PROBLEM: "drive appears confused" and "irq 18: nobody cared!" Alexander Fieroch
2005-05-27 19:30 ` Alexander Fieroch
2005-05-28 0:16 ` Andrew Morton
2005-05-29 20:18 ` Alexander Fieroch
2005-06-14 8:04 ` Bartlomiej Zolnierkiewicz
2005-06-15 20:39 ` Alexander Fieroch
2005-06-15 21:30 ` Andrew Morton
2005-06-16 22:23 ` Alan Cox
2005-06-16 23:52 ` Bartlomiej Zolnierkiewicz
2005-06-17 10:49 ` Alexander Fieroch
2005-06-17 12:38 ` Alan Cox
2005-06-17 17:05 ` Alexander Fieroch
2005-06-17 17:17 ` Jesper Juhl
[not found] ` <42C0953B.8000506@web.de>
2005-06-28 13:47 ` Alan Cox
2005-08-04 20:25 ` Andrew Morton
2005-08-05 10:19 ` Alan Cox
2005-06-29 13:47 ` Alexander Fieroch
2005-07-06 10:17 ` Alexander Fieroch
2005-07-29 22:38 ` Alexander Fieroch
2005-07-30 0:57 ` Michael Thonke
2005-07-29 23:05 ` Parag Warudkar
2005-07-30 1:42 ` Alexey Dobriyan
2005-08-01 14:38 ` Alexander Fieroch
2005-08-01 14:56 ` Alexander Fieroch
2005-08-01 19:23 ` Krzysztof Halasa
2005-08-01 19:28 ` Bartlomiej Zolnierkiewicz [this message]
2005-08-09 17:28 ` Alexander Fieroch
2005-08-09 22:14 ` Alan Cox
2005-08-19 11:12 ` Alexander Fieroch
2005-07-31 22:15 ` Alexander Fieroch
2005-07-06 10:19 ` Alexander Fieroch
2005-06-17 11:29 ` [2.6.12rc4] " Alexander Fieroch
2005-06-13 17:59 ` Alexander Fieroch
-- strict thread matches above, loose matches on Subject: below --
2005-07-06 15:33 Protasevich, Natalie
2005-07-06 23:20 ` Alexander Fieroch
2005-07-11 5:35 Protasevich, Natalie
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=58cb370e050801122831a97873@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=Natalie.Protasevich@unisys.com \
--cc=adobriyan@gmail.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=fieroch@web.de \
--cc=iogl64nx@gmail.com \
--cc=jesper.juhl@gmail.com \
--cc=kaernel-stuff@comcast.net \
--cc=khc@pm.waw.pl \
--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