Hibernation fails with blank screen on a Dell Dimension 5100 when using fglrx driver

Bug #148080 reported by Paul Meathrel
8
Affects Status Importance Assigned to Milestone
linux-restricted-modules-2.6.22 (Ubuntu)
Won't Fix
Low
Unassigned
Nominated for Gutsy by Paul Meathrel
linux-restricted-modules-2.6.24 (Ubuntu)
Incomplete
Undecided
Unassigned
Nominated for Gutsy by Paul Meathrel

Bug Description

Using the latest Gutsy beta with all updates applied - on a Dell Dimension 5100 hibernation fails. After selecting Hibernate the screen goes blank and the cursor flashes in the top left hand corner. No text is displayed and the only resolution is to reboot the machine.

Revision history for this message
Juksu (jluostar) wrote :

I have exactly this same problem on a (Gutsy) HP nc8430 laptop, so it is not limited to Dell? My laptop has the Mobility X1600 Radeon.

So the lappy never suspends/hibernates properly.
The cursor is left blinking to the top left corner of the screen and then - nothing (without a hard reboot).

This happens both when closing the lid or choosing to hibernate from the menu.

Jukka

Revision history for this message
Paul Meathrel (paulmeathrel) wrote :

I've tried hibernating with both S1 and S3 set in the bios and it makes no difference the result is the same.

Revision history for this message
Brian Murray (brian-murray) wrote : Re: Hibernation fails with blank screen on a Dell Dimension 5100

Juksu as your bug is about different hardware please submit a separate bug report. Thanks in advance.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include as attachments the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' after a fresh boot and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Changed in linux-source-2.6.22:
status: New → Incomplete
Revision history for this message
Paul Meathrel (paulmeathrel) wrote :

Thanks for the reply Brian. Here are the relevant files etc:

Output of uname -a: Linux exodus 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux

Revision history for this message
Paul Meathrel (paulmeathrel) wrote :
Revision history for this message
Paul Meathrel (paulmeathrel) wrote :
Revision history for this message
Brian Murray (brian-murray) wrote :

Do you have the same issue if you do not use the proprietary fglrx driver? Could you post dmesg output after failing to hibernate? Thanks again.

Revision history for this message
Juksu (jluostar) wrote :
Revision history for this message
Paul Meathrel (paulmeathrel) wrote :

After disabling the fglrx driver from restricted drivers the machine hibernates fine.

Revision history for this message
Paul Meathrel (paulmeathrel) wrote :

In order to generate the log of dmesg you wanted I've re-enabled fglrx rebooted, hibernated, restarted again and run: dmesg > dmesg.log

I hope that this gives you want you need.

Changed in linux-source-2.6.22:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Low
status: Incomplete → Triaged
Revision history for this message
Marc Quinton (mquinton) wrote :

this may be a duplicate bug from : https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-2.6.22/+bug/121653. If true, please update duplicate status for this bug.

Revision history for this message
Henrik Nilsen Omma (henrik) wrote :

This will be retargeted towards the Hardy kernel once it is released. I've tagged this as "hardy-kernel-candidate" so that we make sure to retarget this report once the new release is out. However against the linux-source-2.6.22 package this is being marked as "Won't Fix" as it does not meet the criteria for a stable release update. To learn more about the stable release update process please refer to https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Changed in linux-restricted-modules-2.6.22:
status: Triaged → Won't Fix
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hardy Heron Alpha2 was recently released. It contains an updated version of the kernel. You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. If you can, please verify if this bug still exists or not and report back your results. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

Changed in linux-restricted-modules-2.6.24:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

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.