Bug 145203 - New-style Thinkpad APM suspend/resume crashes with 2.6.10-1.737_FC3
New-style Thinkpad APM suspend/resume crashes with 2.6.10-1.737_FC3
Status: CLOSED DUPLICATE of bug 144415
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-01-15 04:32 EST by Thomas Roessler
Modified: 2015-01-04 17:15 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:07:57 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Thomas Roessler 2005-01-15 04:32:15 EST
Description of problem:

After a suspend/resume cycle, my thinkpad R40 sometimes does not wake up
properly:  Instead, the machine sits there with a flashing caps lock indicator
light and does not react.  No messages are written to syslog before doing a hard

This is independent of the atkbd.reset setting that took care of 140338 and
142329.  I'm observing this problem on the same R40 on which I observed 140338.

Version-Release number of selected component (if applicable):


How reproducible:

I have not been able to reproduce this problem in a "lab setting" (i.e., by
performing a bunch of suspend/resume cycles in quick succession).  However, I
have observed the crash several times in the morning, when first opening the
thinkpad's lid after the machine had been in suspended state over night.  So I
speculate that this problem may be related to leaving the machine in suspended
state for an extended amount of time (several hours?).

Expected results:

A working system like what I had with FC2's 2.6.8 kernel...
Comment 1 Satish Balay 2005-01-15 14:30:09 EST
Looks like dupe of 144415
Comment 2 Thomas Roessler 2005-01-16 07:15:57 EST

*** This bug has been marked as a duplicate of 144415 ***
Comment 3 Red Hat Bugzilla 2006-02-21 14:07:57 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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