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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to