From: "Steve Lee" <steve@tuxsoft.com>
To: <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Who has record no. of DriveReady SeekComplete DataRequest errors?
Date: Sat, 5 Jun 2004 13:01:29 -0500 [thread overview]
Message-ID: <000401c44b27$24ba1880$8119fea9@pluto> (raw)
>Well since 2.6.3 I think I've been getting the record number of
>
>hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
>hdd: status error: error=0x00
>hdd: drive not ready for command
>hdd: ATAPI reset complete
>
>errors from my cdrw on hdd; and it's only one drive's worth.
I've been witnessing almost exactly the same thing as you. I assumed,
perhaps falsely, that my AOpen CDRW was failing. I just recently
replaced it with a DVD-Rom drive and thus far have not seen these
errors.
hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest
Error }
hdd: status error: error=0x20LastFailedSense 0x02
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: drive not ready for command
hdd: status error: status=0x58 { DriveReady SeekComplete DataRequest }
hdd: status error: error=0x00
hdd: DMA disabled
hdd: drive not ready for command
hdd: ATAPI reset complete
Could this be a kernel bug? Please CC me as I'm no longer subscribed to
this list.
Thanks,
Steve
next reply other threads:[~2004-06-05 18:01 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-05 18:01 Steve Lee [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-05 14:07 [OT] Who has record no. of DriveReady SeekComplete DataRequest errors? Con Kolivas
2004-06-05 14:24 ` Jan Dittmer
2004-06-06 9:28 ` Jens Axboe
2004-06-06 10:38 ` Con Kolivas
2004-06-06 10:58 ` Jens Axboe
2004-06-06 11:05 ` Con Kolivas
2004-06-06 11:10 ` Jens Axboe
2004-06-06 11:37 ` Con Kolivas
2004-06-06 11:51 ` Con Kolivas
2004-06-06 12:11 ` Pascal Schmidt
2004-06-06 20:39 ` Jens Axboe
2004-06-06 23:06 ` Con Kolivas
2004-06-07 0:21 ` Grant Byers
2004-06-07 7:24 ` Jens Axboe
2004-06-07 9:18 ` Con Kolivas
2004-06-07 9:36 ` Jens Axboe
2004-06-07 9:50 ` Con Kolivas
2004-06-07 9:54 ` Jens Axboe
2004-06-07 10:08 ` Con Kolivas
2004-06-07 10:17 ` Jens Axboe
2004-06-07 10:29 ` Con Kolivas
2004-06-07 10:33 ` Jens Axboe
2004-06-07 16:29 ` Jens Axboe
2004-06-07 17:59 ` Jan Dittmer
2004-06-07 18:06 ` Jens Axboe
2004-06-08 13:50 ` Con Kolivas
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='000401c44b27$24ba1880$8119fea9@pluto' \
--to=steve@tuxsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.