Comment 17 for bug 431963

i finally got a SATA cable today that enables me to debiug the issue ...
i see the same behavior as everybody else on the bug, i dont have to fiddle with sreadahed though, just adding "text" to teh cmdline gets me a properly running and stable system (i did plenty of testbuilds and kept the disk busy)

no I/O errors can be spotted at all in that mode ...

trying to launch X though gets me a locked up system ...

i then created an ~/.xsession file that only fires up metacity and xterm ... this works fine as well, no I/O errors, system is rock-stable ...

now firing up gnome-session from the xterm locks the system, no commands can be run apart from dmesg ...
running dmesg shows the following immediately after gnome-session tries to start:

usb 1-1.6: reset high speed USB device using fsl-ehci and address 4
usb 1-1.6: reset high speed USB device using fsl-ehci and address 4
usb 1-1.6: reset high speed USB device using fsl-ehci and address 4
usb 1-1.6: reset high speed USB device using fsl-ehci and address 4
usb 1-1.6: reset high speed USB device using fsl-ehci and address 4
usb 1-1.6: reset high speed USB device using fsl-ehci and address 4
usb 1-1.6: reset high speed USB device using fsl-ehci and address 4
sd 0:0:0:0: [sda] Unhandled error code
sd 0:0:0:0: [sda] Result: hostbyte=0x05 driverbyte=0x00
end_request: I/O error, dev sda, sector 2022791
Buffer I/O error on device sda1, logical block 252841
lost page write due to I/O error on sda1
JBD2: Detected IO errors while flushing file data on sda1: