Red Hat Bugzilla – Bug 230853
2.6.19* kernels won't suspend / resume laptop; 2.6.18 works fine.
Last modified: 2008-02-07 23:26:25 EST
Description of problem:
Kernel on FC6 DVD distro (2.6.18) works fine on Dell Inspiron 700m. However,
the auto-upgrade (if allowed to run) installs various 2.6.19 which will
either not suspend the laptop or not allow the laptop to resume or get it
wedged in some intermediate non-responsive but display-off state.
I've reinstalled twice now. This is getting boring.
Version-Release number of selected component (if applicable):
# uname -a
Linux localhost.localdomain 2.6.19-1.2911.fc6 #1 SMP Sat Feb 10 15:03:33 EST
2007 i686 i686 i386 GNU/Linux
Steps to Reproduce:
Install from FC6 dvd.
Boot. Note solid-on LED for "run".
Laptop suspends. (note flashing "on" LED for suspend)
Open lid. Laptop resumes.
Allow auto-upgrade to run, which installs 2.6.19 kernel.
Laptop doesn't suspend (led stays on solid, current drain stays high).
Open lid. Laptop stays with display off and is non responsive except
to hard power-off (pull battery and AC connection, then reboot).
Laptop does not suspend. It becomes nonresponsive but continues
drawing power from battery at normal rates.
It should suspend. Note that the FC6 DVD kernel works fine.
Allowing the upgrade to run ONCE but keeping around the kernel allows
demonstration of 2.6.18 working and 2.6.19 not working, even tho other
software has been updated too.
This behavior reproducible both on mfg. level A02 BIOS flash (which also
works fine on Fedora Core 4 and Ubuntu) and also on the newest A07 bios
This new tonight:
Realization that under 2.6.18 (actually:
# uname -a
Linux localhost.localdomain 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT
2006 i686 i686 i386 GNU/Linux
it actually does not suspend on EVERY lid-closing - but dependably on every
OTHER lid closing.
No log appears in /var/log/messages for half of the lid closings! This is
more and more perplexing.
- Bill Yerazunis
(This is a mass-update to all current FC6 kernel bugs in NEW state)
I'm reviewing this bug list 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, however this version of Fedora is no longer
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!
Per the previous comment in this bug, I am closing it as INSUFFICIENT_DATA,
since no information has been lodged for over 30 days.
Please re-open this bug or file a new one if you can provide the requested data,
and thanks for filing the original report!