I made my own patch (following Mark's example) but also added that printk
in that function.
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata_gen_fixed_sense: failed
ata_op=0x35
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata4: translated ATA stat/err
0x51/04 to SCSI SK/ASC/ASCQ 0xb/00/00
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata_gen_ata_desc_sense:
failed ata_op=0x51
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata4: status=0x51 {
DriveReady SeekComplete Error }
Jul 9 16:37:52 p34 kernel: [4294810.556000] ata4: error=0x04 {
DriveStatusError }
Now that we have found the ata_op code of 0x35, what does this mean? Is
it generated from a bad FUA/unsupported command from the kernel/SATA
driver?
Justin.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
