Skip to contentSkip to conversation

IDE CD problems in 2.6.13rc6

DISCUSSION Voluspa 2 participants 3 messages Aug 14, 2005 – Aug 15, 2005

lore
Share & tools
lore

Voluspa

author
#0 lore raw
Quoted 5 lines · On 2005-08-14 20:10:49 Nick Warne wrote:

Note the last sentence:

' This variation is designed for use with "libraries" of drive identification information, and can also be used on ATAPI drives which may give media errors with the standard mechanism.

My jaw just clonked on the table. And the media error at hand made you buy a new CD-RW. There is precedence for this (remember the blaming X and other programs in the keyboard driver?) so perhaps the kernel people could amend the error like:

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?

Mvh
Mats Johannesson
--

#1 lore raw
Quoted 4 lines · Voluspa

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

author
#2 lore raw
Quoted 7 lines · On Mon, 15 Aug 2005 01:37:08 +0100 Alan Cox wrote:

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).

Quoted 6 lines

Would

hdc: command not supported by drive
ide: failed opcode was: 0xec

have been more helpful

If it was clearly marked as "This is INFO, not a Warning". Most users I've met (myself included) are always expecting their hardware to crash and burn at the drop of a hat. Scary messages just confirm our anguish - especially when it's coming by way of the CD/HD system.

Mvh
Mats Johannesson
--