Red Hat Bugzilla – Bug 357711
kernel update 18.104.22.168-10.fc7 breaks resume on Dell Inspiron 9400
Last modified: 2008-01-16 18:45:17 EST
Description of problem:
Suspend to RAM appears to work correctly, but attempting to resume results in a
black screen (no backlight) at which point the only remedy appears to be a power
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Use "Stand By" metakey to activate suspend to RAM
2. Press power button to resume.
After a few seconds of activity, the machine stops with a black screen.
Resumption of previous session
Works fine if I boot the previous kernel (kernel-22.214.171.124-91.fc7).
May well be a duplicate of bug #312981.
kernel-126.96.36.199-21.fc7 has the same problem.
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
Yes, still having problems with the latest F7 kernel (kernel-188.8.131.52-52.fc7).
Thanks for the update. Please can you attach contents of:
as separate attachments to this bug of type text/plain.
Created attachment 291884 [details]
Output of dmidecode
Output of dmidecode running kernel-184.108.40.206-52.fc7
Created attachment 291885 [details]
Output of lspci -vvxxx
Output of lspci -vvxxx running kernel kernel-220.127.116.11-52.fc7
Created attachment 291886 [details]
Output of lsmod
Output of lsmod running kernel kernel-18.104.22.168-52.fc7
Information requested provided (random comment to get status back to NEW).
Thank you for that. Could you take a look at:
and review the section entitled Suspend/Resume to RAM Failure as this will help
is debug the issue further. In particular running:
pm-suspend ; dmesg > dmesg.out ; sync
as this writes a dmesg.out file which, if you could attach to this bug, would
Created attachment 291899 [details]
dmesg output just after rebooting with pm_trace enabled
Ok, having read that page, I see that that Caps Lock key is non-functional. I
tried to use pm_trace as suggested, but while my date gets corrupted, there are
no entries in dmesg as described. I attach the full dmesg output in case it is
You could try unloading the iwl3945 module before suspend:
# modprobe -r iwl3945
You may need to being down the network interface first. If you still have the
same issue try also removing the b44 and firewire modules.
Removing the b44 module solves the problem. Sadly this kills my network interface!
And adding SUSPEND_MODULES="b44" to /etc/pm/config.d/unload_modules fixes the
problem properly so this is a duplicate of bug #242234.
*** This bug has been marked as a duplicate of 242234 ***