#75 is correct. My karmic install always gives the error (even with 2.6.29-rc3*). But my jaunty never gives the error, even with 2.6.31-16. However, there is one more difference between my karmic and jaunty installs: karmic uses ext4, while jaunty uses ext2 (and for the record all of those are inside LVM).
Could it be something related to ext4? I notice that the bug triggers during or right after filesystem check/mount (mountall). But I have not been able to reproduce this bug by doing filesystem checks/mounting of the karmic-ext4 partition under jaunty. I have not been able to debug it further. Debugging upstart to see exactly when the bug triggers generates way too much output. I tried disabling ureadahead, but that didn't make any difference. *Note that the error message changed between 2.6.29-6 and 2.6.30-rc1, but it still triggers an error message and the same delay. -- SSD stall during boot https://bugs.launchpad.net/bugs/445852 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
