Bug 229316 - Suspend broken for kernel "2.6.20-1.2932.fc7"
Suspend broken for kernel "2.6.20-1.2932.fc7"
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
rawhide
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-02-20 03:58 EST by Joachim Frieben
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-02-21 13:31:58 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Joachim Frieben 2007-02-20 03:58:21 EST
Description of problem:
After ugrading the kernel on a "IBM ThinkPad T23" to "2.6.20-1.2932.fc7",
"suspend" is broken. It is possible to suspend the system but upon
resume, a single line is issued to the console, namely:
"Stopping tasks ... done." before the screen goes blank, and the system
gets blocked.

Version-Release number of selected component (if applicable):
kernel-2.6.20-1.2932.fc7

How reproducible:
Always.

Steps to Reproduce:
1. Boot system w/kernel "2.6.20-1.2932.fc7".
2. Suspend system by clicking "suspend" button of "GNOME" system menu.
3. Press power button to resume.

Actual results:
System issues "Stopping tasks ... done." and hangs afterwards.

Expected results:
System resumes normal operation.

Additional info:
Downgrading system to kernel "2.6.19-1.2914.fc7" allows to recover a
functional suspend mode. The kernel got broken some time last week
but I am unable to tell when the breakage occurred exactly.
Comment 1 Joachim Frieben 2007-02-21 13:31:29 EST
Fixed in "kernel-2.6.20-1.2936.fc7". Btw, by successive trial, it turned
out that the bug has been introduced in a kernel package later than
"kernel-2.6.20-1.2925.fc7" which also works.

Note You need to log in before you can comment on or make changes to this bug.