I just went and looked in all my logs (/var/log/messages.*.gz going back to Feb 7, 2010)
It looks like either the problem no longer exists or it is much less frequent than it used to. Part of the reason I'm not sure is that many things have changed on my system from my report: I'm using a different disk and ext4, for example. There were much less SATA reset events in the past month (they used to happen multiple times, every day). Now they appear only 3 times: on Feb 7, Feb 20, and Feb 26. The ones on Feb 20 and Feb 26 look like boot-time events, based on the small (2.17... sec and similar) time-stamps, so I suspect they're ok, e.g.: Feb 26 15:22:44 ze kernel: [ 2.178580] ata6: SATA link down (SStatus 0 SControl 300) Only the Feb 7 ones look different: there are many of them (54 sequences spanning 2-seconds) and the kernel time-stamp is high, e.g.: Feb 7 13:45:05 ze kernel: [87054.205008] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 7 13:45:05 ze kernel: [87054.226586] ata2.00: configured for UDMA/33 Feb 7 13:45:05 ze kernel: [87054.226595] ata2: EH complete Feb 7 13:45:05 ze kernel: [87054.276856] ata2: hard resetting link Feb 7 13:45:06 ze kernel: [87054.804868] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) ... This 2 second sequence also has 'sdc' (backup external disk) instead of 'sda' (my main disk), so I suspect cable socket had a temporary bad contact and this is also a legit reset. Besides, at that time I wasn't yet using the latest kernel. Feb 7 13:44:22 ze kernel: [87010.767936] sd 1:0:0:0: [sdc] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE Bottom line is that I haven't really seen the original problem at all in the past month or so. Looks like I've been using the latest Karmic kernel: 2.6.31-20-generic since Feb 8, 2010: -rw-r--r-- 1 root root 3942624 Jan 27 20:47 /boot/vmlinuz-2.6.31-19-generic -rw-r--r-- 1 root root 3946400 Feb 8 02:57 /boot/vmlinuz-2.6.31-20-generic HTH -- Sata is resetted too often: SATA link down (SStatus 0 SControl 0) https://bugs.launchpad.net/bugs/228581 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
