From: Jens Axboe <axboe@suse.de>
To: Andre Hedrick <andre@linux-ide.org>
Cc: jacob@chaos2.org, linux-kernel@vger.kernel.org
Subject: Re: hdd: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Date: Sat, 27 Jan 2001 14:17:30 +0100 [thread overview]
Message-ID: <20010127141730.C27929@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0101252046320.13852-100000@inbetween.blorf.net> <Pine.LNX.4.10.10101270047200.23960-100000@master.linux-ide.org>
In-Reply-To: <Pine.LNX.4.10.10101270047200.23960-100000@master.linux-ide.org>; from andre@linux-ide.org on Sat, Jan 27, 2001 at 12:48:11AM -0800
On Sat, Jan 27 2001, Andre Hedrick wrote:
> > I've been getting this during the boot sequence for quite some time now.
> > They don't seem to impact the functionality of the drive any though. Just
> > another extra-verbose kernel message I should ignore? :)
> >
> > (This is from the 2.4.1-pre10 btw.)
> >
> > hdd: CD-ROM TW 120D, ATAPI CD/DVD-ROM drive
> > hdd: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> > hdd: set_drive_speed_status: error=0x04
>
> Means your device did not like that command and barfed.
> status=0x51, error=0x04 == command aborted next....
My gut tells me that this is the 'get last written' command, and even
with the quiet flag we get the IDE error status printed. Could you
try and add
goto use_toc;
add the top of drivers/cdrom/cdrom.c:cdrom_get_last_written() and
see if that makes the error disappear?
--
* Jens Axboe <axboe@suse.de>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-27 13:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-27 8:38 hdd: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } Jacob Luna Lundberg
2001-01-27 8:48 ` Andre Hedrick
2001-01-27 13:17 ` Jens Axboe [this message]
2001-01-27 19:26 ` Jacob Luna Lundberg
2001-01-27 19:59 ` Andre Hedrick
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=20010127141730.C27929@suse.de \
--to=axboe@suse.de \
--cc=andre@linux-ide.org \
--cc=jacob@chaos2.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 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.