On Wed, 29 Aug 2007 18:55:55 -0400 Chuck Ebbert <cebbert@xxxxxxxxxx> wrote: > https://bugzilla.redhat.com/show_bug.cgi?id=243568 > > Using kernel 2.6.22: > > Aug 29 17:08:11 itox kernel: ata2.00: ATAPI: Seagate STT8000A, 5.51, max MWDMA2 > Aug 29 17:08:11 itox kernel: ata2.00: configured for MWDMA2 > Aug 29 17:08:11 itox kernel: scsi 1:0:0:0: Sequential-Access Seagate STT8000A 5.51 PQ: 0 ANSI: 2 > Aug 29 17:08:12 itox kernel: scsi 1:0:0:0: Attached scsi generic sg1 type 1 > Aug 29 17:08:12 itox kernel: st: Version 20070203, fixed bufsize 32768, s/g segs 256 > Aug 29 17:08:12 itox kernel: st 1:0:0:0: Attached scsi tape st0 > Aug 29 17:08:12 itox kernel: st 1:0:0:0: st0: try direct i/o: yes (alignment 512 B) > Aug 29 17:08:12 itox kernel: ata2: DRQ=1 with device error, dev_stat 0x59 > Aug 29 17:08:12 itox kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen > Aug 29 17:08:12 itox kernel: ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 > Aug 29 17:08:12 itox kernel: res 51/60:03:00:00:20/00:00:00:00:00/a0 Emask 0x3 (HSM Device Ready, Seek Complete, Data Request, Error DRQ and Error together is a bit odd to say the least It then commits suicide and falls off the bus. That may be due to the fact we use SRST on ATAPI device errors still rather than trying an ATAPI reset first. Shouldn't matter though. Since you are the lucky owner of the object in question can you dump the contents of the packet command going to the device when this occurs ? Alan - To unsubscribe from this list: 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
