From: Jens Axboe <axboe@suse.de>
To: Con Kolivas <kernel@kolivas.org>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Who has record no. of DriveReady SeekComplete DataRequest errors?
Date: Mon, 7 Jun 2004 12:17:32 +0200 [thread overview]
Message-ID: <20040607101732.GI13836@suse.de> (raw)
In-Reply-To: <200406072008.07176.kernel@kolivas.org>
On Mon, Jun 07 2004, Con Kolivas wrote:
> On Mon, 7 Jun 2004 19:54, Jens Axboe wrote:
> > I don't see how that command gets generated if you commented out
> > cdrom_is_mrw() in ide-cd. It's the only place we call it, and it's the
> > only place that issues that command...
>
> Ok I get the picture :P
:)
> > Can you repeat with the debug cdrom_queue_packet_command() patch still
> > applied? Thanks!
>
> Here's the whole shebang in case I miss something:
>
> hdd: RICOH CD-R/RW MP7163A, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
> hda: max request size: 1024KiB
> hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
> hda: hda1 hda2 < hda5 hda6 hda7 >
> hdb: max request size: 1024KiB
> hdb: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
> hdb: hdb2 < hdb5 hdb6 hdb7 >
> ide-cd: queueing cdb: 5a 00 2a 00 00 00 00 00 18 00 00 00
> ide-cd: queueing cdb: 46 00 00 28 00 00 00 00 08 00 00 00
> ide-cd: queueing cdb: 46 00 00 28 00 00 00 00 44 00 00 00
> ide-cd: queueing cdb: 5a 00 03 00 00 00 00 00 10 00 00 00
> ide-cd: queueing cdb: 5a 00 2c 00 00 00 00 00 10 00 00 00
> ide-cd: queueing cdb: 46 00 00 20 00 00 00 00 18 00 00 00
> hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
> Uniform CD-ROM driver Revision: 3.20
> ide-cd: queueing cdb: 00 00 00 00 00 00 00 00 00 00 00 00
> ide-cd: queueing cdb: 25 00 00 00 00 00 00 00 00 00 00 00
> ide-cd: queueing cdb: 43 02 00 00 00 00 00 00 04 00 00 00
> ide-cd: queueing cdb: 5a 00 2a 00 00 00 00 00 18 00 00 00
> ide-cd: queueing cdb: 46 00 00 28 00 00 00 00 08 00 00 00
> hdd: status error: status=0x59 { DriveReady SeekComplete DataRequest Error }
> hdd: status error: error=0x20LastFailedSense 0x02
> hdd: drive not ready for command
So that didn't help at all... Hmm I wonder what to do about this. So
last failure was NOT_READY - does it make a difference if you have a
medium loaded or not?
--
Jens Axboe
next prev parent reply other threads:[~2004-06-07 10:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2004-06-05 18:01 Steve Lee
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=20040607101732.GI13836@suse.de \
--to=axboe@suse.de \
--cc=kernel@kolivas.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