Comment 6 for bug 387272

Karmic upgrade killed my laptop too. At first, I thought the HSM violations were related to something botched with the disk encryption that was set up in Jaunty. (I create sda1 for /, and sdb1 as an encrypted partition. I created a logical volume group on top of that and the had swap, /var, and /home created in the volume group) but this seems to be the root issue:

The problem got progressively worse with each reboot, so I'm assuming that there's a whole lot of disk corruption by now (DISCLAIMER: The below "output" was manually typed/copied, I didn't have a way to cut and copy to a file)...

ata2.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata2.01: ST-ATA: DRQ=0 without device error, dev_stat 0x0
ata2.01: cmd 20/00:08:c7:49:7a/00:00:00:00:00/f0 tag 0 pio 4096 in
         res 00/00:00:00:00:00:/00:00:00:00:00:/00 Emask 0x202 (HSM violation)

those messages repeated on the screen for a while and eventually I got:

end_request: I/O error, dev sdb, sector 8014279

Fortunately, everything pre-upgrade was synced to my desktop, but I'm going to try a fresh install of Karmic and see what happens.