I've been trying to dig into the cause of the problem. I shall try to explain what is happening:
Apr 6 12:25:41 UbuntuDesktop kernel: [ 482.226347] ata2: DRQ=1 with device error, dev_stat 0x59 essentially, dev_stat 0x59 means the last ATA command failed and also the controller is indicating that it is ready for data transfer (DRQ=1), however DRQ should not be 1 and the driver catches this error condition. The only thing it can do is a soft reset, which is seen in the next few kernel log messages: Apr 6 12:25:41 UbuntuDesktop kernel: [ 482.226377] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Apr 6 12:25:41 UbuntuDesktop kernel: [ 482.226386] ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0 Apr 6 12:25:41 UbuntuDesktop kernel: [ 482.226387] res 51/20:03:00:00:20/00:00:00:00:00/a0 Emask 0x3 (HSM violation) Apr 6 12:25:41 UbuntuDesktop kernel: [ 482.226422] ata2: soft resetting port Apr 6 12:25:41 UbuntuDesktop kernel: [ 482.873238] ata2.00: configured for MWDMA2 Apr 6 12:25:42 UbuntuDesktop kernel: [ 483.037199] ata2.01: configured for MWDMA2 Apr 6 12:25:42 UbuntuDesktop kernel: [ 483.037228] ata2: EH completee Apparently this condition is experienced with some tape drives, and a work around is included in the driver for tape drives only. I am grasping at straws here, but if the same problem is seen with some buggy tape drives, perhaps the same issue with your system may be an issue between the disc and the controller, rather than a generic driver issue. -- kernel.log syslog filling up with repeated ata2 and cdrom messages https://bugs.launchpad.net/bugs/95105 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
