[REGRESSION] Resume from suspend fails on Dell Latitude C400

Bug #303584 reported by Patrick Burke
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Using intrepid with any 2.6.27 series kernel and intel video driver, my Dell Latitude C400 does not resume correctly -- everything seems to come back up fine, except the screen remains black (no backlight). Hibernate still works fine.

 If I revert to kernel 2.6.24-19, resume from suspend works perfectly.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Patrick,

Is this still an issue for you? Are you able to ssh into the machine after you resume? If so, can you please attach the following information after an attempted suspend/resume cycle. Please be sure to attach each file as a separate attachment.

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
* /var/log/Xorg.0.log

Thanks again and we appreciate your help and feedback.

Changed in linux:
status: New → Incomplete
Revision history for this message
Patrick Burke (pburke-gmail) wrote :

Yes, I'm still having the same problem, even with the recent 2.6.27-11 kernel. Thanks for your help!

Revision history for this message
Patrick Burke (pburke-gmail) wrote :
Revision history for this message
Patrick Burke (pburke-gmail) wrote :
Revision history for this message
Patrick Burke (pburke-gmail) wrote :
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Patrick,

Sorry for such a delayed response. I'm curious if you could do an additional test and try the latest Jaunty 9.04 pre-release, currently Alpha5 - http://cdimage.ubuntu.com/releases/jaunty/ . It contains a newer 2.6.28 based kernel. You should be able to test suspend via a LiveCD. I'm also curious what happens if you switch to say vt1 first (ctrl-alt-F1) and then run pm-suspend, what the result is - https://wiki.ubuntu.com/DebuggingKernelSuspend . Thanks.

Revision history for this message
Alex Denvir (coldfff) wrote :

We are closing this bug report because it has not been updated for some time. Please reopen it if you have more information to submit, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.