io/fs errors when launching gdm on imx51 with sata
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-fsl-imx51 (Ubuntu) |
Fix Released
|
High
|
Bryan Wu | ||
Karmic |
Fix Released
|
High
|
Bryan Wu | ||
Lucid |
Fix Released
|
High
|
Bryan Wu |
Bug Description
With the imx51 image on babbage 2.5, if I boot with USB as a disk, everything works fine. With a sata drive attached, it's a different story.
My current configuration is that I have a 2.5" sata disk (tested and shown to work on other systems) connected to the babbage for data, and the power is coming from an external source.
I can boot the live image, and go all the way through the installation with no problems. On reboot, when gdm starts to come up, I get as far as the spinning mouse cursor and it appears to hang.
If I eliminate sreadahead from starting, I'm able to get it to take longer before hanging, but it still eventually does hang.
If I eliminate both sreadahead and gdm, I'm able to boot to a text console and use the system just fine.
Starting sreadahead by itself, I didn't see any problems, no hang, no io errors in dmesg.
Starting gdm by itself, it hangs after several seconds and I start to see errors like this on the serial console within a few minutes:
end_request: I/O error, dev sda, sector 71319871
EXT4-fs error (device sda1): __ext4_
Aborting journal on device sda1:8.
EXT4-fs error (device sda1): ext4_journal_
EXT4-fs (sda1): Remounting filesystem read-only
end_request: I/O error, dev sda, sector 71319879
end_request: I/O error, dev sda, sector 71319887
end_request: I/O error, dev sda, sector 239343983
end_request: I/O error, dev sda, sector 239344223
When this happens, I cannot even switch between virtual consoles.
Kernel version signature is 2.6.31-100.7-imx51
tags: | added: armel |
affects: | linux (Ubuntu) → linux-fsl-imx51 (Ubuntu) |
Changed in linux-fsl-imx51 (Ubuntu): | |
assignee: | nobody → Amit Kucheria (amitk) |
Changed in linux-fsl-imx51 (Ubuntu Karmic): | |
milestone: | none → ubuntu-9.10 |
importance: | Undecided → Medium |
Changed in linux-fsl-imx51 (Ubuntu Karmic): | |
importance: | Medium → High |
status: | New → Confirmed |
Changed in linux-fsl-imx51 (Ubuntu Karmic): | |
milestone: | ubuntu-9.10 → none |
Changed in linux-fsl-imx51 (Ubuntu Karmic): | |
status: | Confirmed → Triaged |
tags: | added: iso-testing |
Changed in linux-fsl-imx51 (Ubuntu Karmic): | |
assignee: | Amit Kucheria (amitk) → Bryan Wu (cooloney) |
Changed in linux-fsl-imx51 (Ubuntu): | |
assignee: | Amit Kucheria (amitk) → Bryan Wu (cooloney) |
Changed in linux-fsl-imx51 (Ubuntu Lucid): | |
milestone: | karmic-updates → lucid-alpha-2 |
Changed in linux-fsl-imx51 (Ubuntu Karmic): | |
status: | Triaged → In Progress |
Changed in linux-fsl-imx51 (Ubuntu Lucid): | |
status: | Triaged → In Progress |
tags: |
added: verification-done removed: verification-needed |
To me this looks like your disk is dying (or perhaps your SATA controller is buggy)