Red Hat Bugzilla – Bug 473542
Can't resume from suspend/hibernate on Dell Vostro 1310
Last modified: 2013-01-10 02:09:48 EST
Description of problem:
Can't resume from suspend or hibernate.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. System -> Shutdown -> Suspend
2. Wait until the system is suspended
3. Resume the system
System seems to return, but the screen shows only a black background with the mouse cursor. Mouse and keyboard input are ignored. System locked, forced reboot needed.
Resume correctly from suspend.
It's the same thing for hibernate.
My Smolt Profile: http://www.smolts.org/client/show/pub_f1bd23a9-5220-4fbd-becc-b83e07c99cb4
Confirmed, I see the exact same behaviour with F10 (KDE version) on a Lenovo ThinkPad X61s.
I had no problems suspending/resuming the same laptop when running Ubuntu 8.10. I'm a long-time Debian/Ubuntu user trying to convert to Fedora (just to see what it's like) but if this bug is a blocker; working suspend/resume is very important to me.
Follow-up: it seems to be related to compiz somehow. If desktop-effects is turned off, Fedora resumes from suspend nicely.
On KDE also, if "Desktop Effects" is off everything works normally.
This update seems to have solved the problem for me:
Also, changing to a text VT and then returning to X is working too.
I confirm 220.127.116.11-130.fc10.i686 and the intel patch it includes from koji resolves this issue
This is not working for me. I installed 18.104.22.168-130.fc10.i686 from koji and the problem with suspend still persists, even though desktop-effects are disabled. Maybe of relevance is that I have a Mobility Radeon HD 2400 video adapter using the "radeon" or the "radeonhd" driver. The system suspends fine, but upon resume the screen remains black (doesn't even flash, nor does the backlight come on), the system is frozen (caps lock key causes no lighting of the caps light).
I still cannot resume from a suspend-to-ram even with the new kernel. I have Vostro 1400 with Nvidia 8400M GS . On opening the lid , I just see the screen turned off completely and keyboard not responding. On the default kernel (22.214.171.124-117), I had also tried with the nv driver instead of nvidia (ver 180.08) driver ,I got the same result .
I have the same problem with an HP Compaq nx7400. This is a Core 2 Duo 1.8GHz, with an Intel 915/945 Integrated Graphics Controller. I'm running F10 final with kernel 126.96.36.199-117.fc10.x86_64. Graphics card driver is xorg-x11-drv-i810-2.5.0-3.fc10.x86_64
When resuming from Suspend-to-RAM, I get a black screen with a mouse cursor, but the system is completely unresponsive and I have to hard-reboot.
Apologies - should have added this in my first comment :
The problem only occurs when compiz is enabled (which has its own slowness problems as noted in Bug 444328 - compiz slow with Intel i810 driver).
With compiz disabled suspend and resume DOES work for me.
(In reply to comment #6)
> This is not working for me. I installed 188.8.131.52-130.fc10.i686 from koji and
> the problem with suspend still persists, even though desktop-effects are
> disabled. Maybe of relevance is that I have a Mobility Radeon HD 2400 video
> adapter using the "radeon" or the "radeonhd" driver. The system suspends fine,
> but upon resume the screen remains black (doesn't even flash, nor does the
> backlight come on), the system is frozen (caps lock key causes no lighting of
> the caps light).
(In reply to comment #7)
> I still cannot resume from a suspend-to-ram even with the new kernel. I have
> Vostro 1400 with Nvidia 8400M GS . On opening the lid , I just see the screen
> turned off completely and keyboard not responding. On the default kernel
> (184.108.40.206-117), I had also tried with the nv driver instead of nvidia (ver
> 180.08) driver ,I got the same result .
The fix is only for Intel cards as per the Koji changelog
(In reply to comment #8)
> I have the same problem with an HP Compaq nx7400. This is a Core 2 Duo 1.8GHz,
> with an Intel 915/945 Integrated Graphics Controller. I'm running F10 final
> with kernel 220.127.116.11-117.fc10.x86_64. Graphics card driver is
> When resuming from Suspend-to-RAM, I get a black screen with a mouse cursor,
> but the system is completely unresponsive and I have to hard-reboot.
This should be resolved by downloading the kernel from Koji
(In reply to comment #10)
> The fix is only for Intel cards as per the Koji changelog
Do you know if this is a confirmed kernel bug in regard to the radeon driver too?
I tried getting some additional information using the guide here:
and trying the pm_trace trick, but I got no useful "hash matches" grepping dmesg. So I suppose it is not a particular module causing the problem.
Regression: this new kernel from koji seems to be problematic too. It will boot to gdm screen, but will ignore keyboard and touchpad.
If I boot 2.26.5 and then reboot to 2.26.7-130, everything works. Odd.
Update: same thing with -134. It seems to be a issue with iwl3945. This patch is likely to fix it:
You may be correct, as on resuming , I cant see the wifi light come on , I have a Intel 3945 too. I will try suspending with iwl3945 module removed .
I'm using kernel 18.104.22.168-132.fc10.x86_64 from koji, and I have an Intel 3945 wireless card :
lspci : 10:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
iwl3945 151908 0
rfkill 17316 2 iwl3945
mac80211 213872 1 iwl3945
cfg80211 32400 2 iwl3945,mac80211
I'm NOT using compiz, due to the i810 slowness problem, and suspend and resume DOES work fine for me. The laptop is an HP Compaq nx7400.
I've just got the same freezing with kernel-22.214.171.124-117.fc10.x86_64. System boots up to gdm screen and stays there until I force a reboot. It seems that the bug is present in this kernel too, but is hit less often.
I just created a new report for this bug as these are likely to be different issues.
Check bug #474357.
I just wanted to say that I've had this exact problem with a GMA 4500, but it was solved with the latest kernel in koji, i.e. kernel-126.96.36.199-135.fc10, with no visible regressions (that I've noticed, at least).
(In reply to comment #18)
> I just wanted to say that I've had this exact problem with a GMA 4500, but it
> was solved with the latest kernel in koji, i.e. kernel-188.8.131.52-135.fc10, with
> no visible regressions (that I've noticed, at least).
Same experience here. 184.108.40.206-134.fc10.x86_64 from updates-testing fixes this issue for me.
Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)
I just wanted to clarify as this bug report has become confusing. I have a Lenovo T60. I am seeing both the inability to resume from suspend, and the intel 3945 system hang.
From what I can tell the hang on resume is completely unrelated to the 3945 issue. It is just an X windows issue. It does not happen if you disable compiz / Desktop effects. The box is not hung, and you can ssh into it, and shut it down. I haven't seen any work related to this issue. I can re-enable and provide additional logfiles, or testing. I am using the intel driver.
There also appears to be other drivers that hang X on resume whether or not compiz is enabled. It looks like these are Radeon. Should we fork a new ticket for the compiz issue, and treat it separate from the Radeon issue?
The second issue is that the entire system can hang when using the intel 3945 wireless module. This was spun off into it's own issue (bug #474357).
Let me know if I have misunderstood the text in the bug...
I believe this issue is fixed with the latest kernel update (at least on Intel video, not sure about ATI).
The other bug is still running and is unrelated to this one.
By latest I assume you mean 220.127.116.11-134.fc10.x86_64? If so I can re-enable compiz and test.
I tested running 18.104.22.168-134.fc10.x86_64 and I was able to resume without the hang.
I'm using F12 beta with kernel 22.214.171.124-115.fc12.i686.PAE and the problems seems to be more frequent now. Every single suspend renders the black screen of death. Definetly the system is not dead. When the screensaver is activated i can see it moving but my keyboard doesn't work, neither my mouse. I can't use suspend anymore, too sad. I have a Dell Vostro 1400. Do i need to open a bug against Rawhide?
Updating summary per comment #24.
It's less frequent now after the last kernel updates but i can't say for sure when it will not resume.
*** Bug 542379 has been marked as a duplicate of this bug. ***
*** Bug 517480 has been marked as a duplicate of this bug. ***
*** Bug 542317 has been marked as a duplicate of this bug. ***
*** Bug 492740 has been marked as a duplicate of this bug. ***
*** Bug 508571 has been marked as a duplicate of this bug. ***
*** Bug 471711 has been marked as a duplicate of this bug. ***
Michael, I really appreciate the fact that you found all those suspend/resume bugs. But they are not all the same bug, because suspend/resume fails on different systems for different reasons.
For example, my desktop has never been able to suspend/resume with Fedora, while it has always worked on my laptop.
I suggest you reopen all those bugs and perhaps create (or find, it may already exist) a single suspend/resume issues meta-bug. Then just add all those mentioned as blockers of this meta-bug.
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '12'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 12's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.