Wow, guys, I have the fullest respect for your patience and insisting behavior after the long time this bug has been around.
Well, what can I say? Two months ago, I built myself a brand new machine with the following components: Asus P7H57D-V Evo Intel Core i7 875K 4 x 4 GB Corsair PC3-16000 (XMS3) 2 x Corsair Force F120 @ RAID 0 mounted on / 2 x Seagate Constellation ES 2 TB @ RAID 0 mounted on /home BeQuiet Dark Power Pro 750 W Initially I had the SSDs connected to the mainboard's SATA 3 interfaces (provided by a Marvell 88SE9125 chip) and with that setup, I couldn't even finish the installation (Ubuntu Maverick AMD64). So I moved the SSDs to the Intel controller's ports 1 and 2 and hooked the Seagte HDDs up to the Marvell. Installation went fine but ever since I get those freezes that are described on this page. They sometimes last for 20 or so seconds and vanish without doing any harm, but I seem to notice a higher frequency since the kernel package update that took place last week. However, sometimes the drives won't recover and the whole machine gets stuck without even being able to properly shut down. Up to now I've never had any data lost but it's a really annoying issue and I'd like to get rid of it. Desperate as I was, I connected all six drives (2 x SSD, 2 x HDD, 2 x BDD) to the (internal) Intel chipset controller a week ago and what can I say? No freeze since then - and I'm running my machine on average several hours per day currently. Needless to say, all drives are fine. I don't have any other OS installed but I've tested them (the drives) one by one more than once. Even did RW tests but to no avail (other than the fact that there is no hardware issue). So... has anybody from the development team (Kernel?) ever taken a look at this issue and tried to investigate further? I'm more than willing to help but at the moment I don't really see what else I could do. Thanks for reading! :) K1300S -- ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen https://bugs.launchpad.net/bugs/285892 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
