Hi Jeremy, I already use the current beta of lucid (including all updates) and have not had this issue any more. Every partition gets successfully remounted after S3 and with write permissions...
Still, I also tested the current mainline kernel as you wished ( from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/) linux-headers-2.6.34-999_2.6.34-999.201004211003_all.deb linux-headers-2.6.34-999-generic_2.6.34-999.201004211003_amd64.deb linux-image-2.6.34-999-generic_2.6.34-999.201004211003_amd64.deb While I don't get any messages with the 2.6.32-21 during regular boot (at least not on screen), I do see these messages in the same situation using the daily built: ata5: softreset failed (device not ready) ata4: softreset failed (device not ready) ata3: softreset failed (device not ready) The only thing that pops up before the plymouth boot theme using the regular 2.6.32 is something like: ureadahead blabla (sry but my SSD-Drive makes it nearly impossible to notice things on time) Still, with both kernels I find entries in dmsg log: [ 2.660022] ata5: softreset failed (device not ready) [ 2.660060] ata5: applying SB600 PMP SRST workaround and retrying [ 2.660078] ata4: softreset failed (device not ready) [ 2.660110] ata4: applying SB600 PMP SRST workaround and retrying [ 2.660127] ata3: softreset failed (device not ready) [ 2.660160] ata3: applying SB600 PMP SRST workaround and retrying But as I stated above - Resuming from S3 is not an issue any more! ** Tags removed: needs-upstream-testing -- Partitions unmounted after Resume from S3 https://bugs.launchpad.net/bugs/460907 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
