From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Voluspa <voluspa@telia.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IDE CD problems in 2.6.13rc6
Date: Mon, 15 Aug 2005 01:37:08 +0100 [thread overview]
Message-ID: <1124066229.29265.2.camel@localhost.localdomain> (raw)
In-Reply-To: <20050815005101.26df083a.voluspa@telia.com>
On Llu, 2005-08-15 at 00:51 +0200, Voluspa wrote:
> hdc: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> hdc: drive_cmd: error=0x04 { AbortedCommand }
> ide: failed opcode was: 0xec
> ide: Did you just run "hdparm -I" or do you use a nosy desktop?
We certainly could interpret 0x51, 0x04 specifically. Its not an "error"
in the usual spew at the user case generally speaking but a "do this"
"no" sequence. Its useful to log because sending unknown commands to an
IDE device is something we want to catch (some drives hang if you do it,
others do really *crazy* things).
Would
hdc: command not supported by drive
ide: failed opcode was: 0xec
have been more helpful
Alan
next prev parent reply other threads:[~2005-08-15 0:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-14 22:51 IDE CD problems in 2.6.13rc6 Voluspa
2005-08-15 0:37 ` Alan Cox [this message]
2005-08-15 0:53 ` Voluspa
-- strict thread matches above, loose matches on Subject: below --
2005-08-15 18:30 Nick Warne
2005-08-14 20:10 Nick Warne
2005-08-14 19:55 Nick Warne
2005-08-14 19:30 Voluspa
2005-08-14 17:43 Voluspa
2005-08-13 23:29 Dave Jones
2005-08-14 0:26 ` Con Kolivas
2005-08-14 0:30 ` Con Kolivas
2005-08-14 13:53 ` Alan Cox
2005-08-14 11:35 ` Bartlomiej Zolnierkiewicz
2005-08-14 13:46 ` Alan Cox
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=1124066229.29265.2.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=voluspa@telia.com \
/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.