I can confirm the same problems on a Compaq Presario CQ60-219EA with 4GB
RAM running 64-bit Jaunty, installed and updated a couple of hours ago.
The console shows disk I/O errors, and ext4 eventually decides to
remount the disk read-only.
When this first happened, I have the NVidia proprietary driver installed
and:
- Suspend took a long time. I think about 10-20 seconds.
- Resume also took a long time in a blank screen phase, and
eventually the X mouse pointer appeared, but the remaining desktop didn't,
it was all black.
- I was able to Control-Alt-F1 to a text console, and that showed disk I/O
errors
and ext4 remounting read-only.
- I was not able to login on the console. Each time I tried, a couple of
disk I/O
error messages appeared, and then after a few seconds the login: prompt
reappeared.
On that occasion, after the post-resume broken state, I held down the
power button for 5 seconds to power down. Then pressed the power button
to start up again, and booted back into Linux.
Despite the theoretical power cycle, Linux was unable to complete the boot
process, at some point showing messages about CPU#0 and CPU#1 both
being stuck and detected by soft-locked.
I held down the power button again, to power cycle again, and this time Linux
did boot successfully back to the desktop.
Then I removed the NVidia proprietary driver, and logged out then into X
again. Perhaps unsurprisingly, the screen was a mess, showing neither a
good picture as with NVidia, nor the low-resolution extremely slow
picture without the drive. Fair enough, who tests driver removal. So I
power cycled again.
This time it booted and showed the low-resolution extremely slow
desktop, confirming the NVidia's driver had gone. So I tried
suspend/resume, and got similar results:
- Long time to suspend
- Nothing useful on resume
For one last test, I power cycled again, and this time instead of
logging in to X, I switched to a text console after the X login window
appeared. (This is still without the NVidia proprietary driver loaded
at all during this session).
>From the text console, I did "pm-suspend", which took a while but did suspend.
Then when I pressed the power button to resume, the power light came on, and
eventually the wireless light (very slowly - about 30 seconds to the wireless
light), but a blank screen with no backlight. Caps Lock did not respond
either, so it wasn't simply a case of no screen.
I can only do quite occasional testing of this laptop from here, because
all this was in preparing it for someone else. For whom my advice is
obviously going to be "don't use suspend, at least for now".
--
[Compaq Presario CQ60] suspend/resume problem
https://bugs.launchpad.net/bugs/323733
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
