On Tue, 20 Jun 2006, Mark Lord wrote:
Justin Piszcz wrote:
Should someone comment this code out that produces the printk()'s as these
are useless information as there is no problem with the disk?
MMm.. probably "barrier" commands that the drive doesn't like.
Pity those messages don't also dump the failed opcode.
Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: status=0x51 { DriveReady
SeekComplete Error }
Jun 20 03:14:20 p34 kernel: [4339456.678000] ata3: error=0x04 {
DriveStatusError }
Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: status=0x51 { DriveReady
SeekComplete Error }
Jun 20 03:20:27 p34 kernel: [4339823.900000] ata3: error=0x04 {
DriveStatusError }
Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: no sense translation for
status: 0x51
Jun 20 03:36:44 p34 kernel: [4340801.772000] ata3: status=0x51 { DriveReady
SeekComplete Error }
Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: no sense translation for
status: 0x51
Jun 20 03:41:04 p34 kernel: [4341061.844000] ata3: status=0x51 { DriveReady
SeekComplete Error }
Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: no sense translation for
status: 0x51
Jun 20 03:46:27 p34 kernel: [4341384.974000] ata3: status=0x51 { DriveReady
SeekComplete Error }
Mark, what would be the proper direction to move towards? Is Jeff or
another SATA/ATA maintainer going to have to look at this or is there
something else I can do, or?
Justin.
-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
