I'm not convinced this recent problem is related to devkit-disks-probe-ata-smart (the original bug). I have experienced the recent problem once - during an 'apt-get update'.
From what I see it's typified by the kernel giving a READ DMA or WRITE DMA command, to which the drive responds in an unexpected manner (HSM Violation). After a suitable timeout the drive is reset and things continue.
Also, the bug does not occur at boot, but randomly during use. And using the probing with 'Disk Utility' has no affect for me.
I'm not convinced this recent problem is related to devkit- disks-probe- ata-smart (the original bug). I have experienced the recent problem once - during an 'apt-get update'.
From what I see it's typified by the kernel giving a READ DMA or WRITE DMA command, to which the drive responds in an unexpected manner (HSM Violation). After a suitable timeout the drive is reset and things continue.
Also, the bug does not occur at boot, but randomly during use. And using the probing with 'Disk Utility' has no affect for me.