From: Patrick Dohman <pdohman@comcast.net>
To: linux-kernel@vger.kernel.org
Subject: ATAPI device errors
Date: 05 Feb 2004 04:16:24 -0600 [thread overview]
Message-ID: <1075976185.1369.20.camel@localhost.localdomain> (raw)
My CDROM & CDRW are problematic. I am running a 2.4.24 kernel. I suspect
a hardware problem but I am unsure if the problem lies with the CDROM,
CDRW or the IDE/ATAPI controler. Basically the the issue boils down to
having one or both of the drives fall offline after a day or two of
uptime. My logs are spammed with this.
:hdd: packet command error: status=0x51 { DriveReady SeekComplete Error}
:hdd: packet command error: error=0x40
:ATAPI device hdd:
:Error: Hardware error -- (Sense key=0x04)
:(vendor-specific error) -- (asc=0x90, ascq=0x00)
:The failed "Test Unit Ready" packet command was:
:"00 00 00 00 00 00 00 00 00 00 00 00 "
Is there a more verbose form of logging I can enable. Any clarification
is very much appreciated.
Thank you
next reply other threads:[~2004-02-05 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 10:16 Patrick Dohman [this message]
2004-02-05 12:50 ` ATAPI device errors Jens Axboe
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=1075976185.1369.20.camel@localhost.localdomain \
--to=pdohman@comcast.net \
--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