Albert Lee wrote:
Mark Lord wrote:
..
(1) When ejecting a disk, either with the "eject /dev/sdc" command
or using the front-panel soft-eject button on the drive,
I get the following in syslog from libata:
sdc: Spinning up disk...<3>ata4.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x2
res 00/00:03:00:00:20/00:00:00:00:00/a0 Emask 0x2 (HSM violation)
ata4: soft resetting port
ATA: abnormal status 0x7F on port 0x00010177
ATA: abnormal status 0x7F on port 0x00010177
ata4.00: configured for PIO2
ata4: EH complete
The device status of 0x00 looks strange.
Not to me. The device likely generated an unsolicitied interrupt,
and status==0x00 is correct for a few seconds here: the drive is
not busy with a command, not in an error state, and not ready
for a new command since it is busy ejecting a disc.
Could you please apply the attached debugging patch for
clue about what caused the HSM violation, thanks.
I'll unpack the drive and hook it up again.
Cheers
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
