On Fri, Jul 25, 2008 at 1:56 PM, Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> wrote: >> > [ 1078.735322] ata3.00: configured for UDMA/133 >> > [ 1078.735336] ata3: EH complete >> > [ 1078.766066] sd 2:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB) > > We timed out, reset the drive and it came back. >> > [ 1078.766442] sd 2:0:0:0: [sda] Write Protect is off >> > [ 1078.766448] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 >> > [ 1078.766957] sd 2:0:0:0: [sda] Write cache: enabled, read cache: >> > enabled, doesn't support DPO or FUA >> > [ 1107.310768] [drm] Loading R300 Microcode > > I notice there is a drm Loading R300 Microcode logged just before each > drive failure. That seems very suspicious to me. Does it ever occur if > you are not in X ? I don't know but I can try it, later today. What is happening is that the movie I am watching with vlc (stored on the drive) stops playing and then the dmesg error comes up, and then it ether freezes X which it did a couple of times but I didnt get the dmesg because it was frozen and i wasnt expecting it, or I just need to restart the movie and it plays again(the error stuff mentioned in the dmesg above). Is there any other info I can provide you with? -Stoyan G > -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
