Bug 36978 - apm suspend crash on wakeup with a Toshiba Tecra 8100
Summary: apm suspend crash on wakeup with a Toshiba Tecra 8100
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: apmd   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Aaron Brown
Depends On:
TreeView+ depends on / blocked
Reported: 2001-04-21 14:11 UTC by Alain Wenmaekers
Modified: 2014-03-17 02:20 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-02 22:46:54 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Alain Wenmaekers 2001-04-21 14:11:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.76 [en] (X11; U; Linux 2.4.2-2 i686)

suspending the laptop with apm --suspend works (The control led confirms
this). When powering up, all I get is a blank screen (keyboard doesn't
work....not even the powerbutton. All that is possible is using the
I'm using a Toshiba Tecra 8100 with RH7.1 installed on the loop device (on
a vfat partition). apm --suspend however did work with RH7.0 in the exact
same configuration.

Reproducible: Always
Steps to Reproduce:
1. apm--suspend
2. power back on

Actual Results:  system crashes. Keyboard and powerbutton are not
responsive to input. Power Led stays on.

Expected Results:  system-wake up 

Toshiba Tecra 8100
256 Mb RAM
HD 6G (3+3 vfat, the Redhat.img is on partition 2 with a size of 2G)

Comment 1 Alain Wenmaekers 2001-04-22 11:15:05 UTC
downgrading to the apm rpm from RH7.0 solves the problem

Comment 2 Need Real Name 2002-02-04 21:20:10 UTC
This bug looks old, but it's still open, so here's a comment.

On the Dell Inspiron, this happens when DRI is enabled in X
and the machine is suspended---it does not restore.  See the 
information on suspending in the Linux-Dell-Laptops FAQ at

With the latest 7.1 updates for X and the kernel, this problem
has re-appeared since DRI is now enabled by default.  I'll
probably submit a new bug report.

Comment 3 Alain Wenmaekers 2002-02-04 21:40:32 UTC
The laptop is still running RH7.1 (but not on an vfat partition anymore).
The apm problems still occurs (even with the RH7.0 apm RPM... I though for a 
moment it worked better, but I was wrong)

Because of the previous comment I tried some suspends without X... and it 
seemed to work.
The RH7.0 installation (which didn't have the problem), used a Xfree3.x X-
server not included in RedHat.

So I think the problem can be traced back to X.

Comment 4 Bernhard Rosenkraenzer 2002-02-26 17:47:22 UTC
Are you still seeing this with the current version?

Comment 5 Need Real Name 2002-02-26 20:28:58 UTC
not suring if you're asking about this question as regards Toshiba or Dells,
but this is still a problem on the Dell Inspiron.  one thing to add is that the
agpgart cannot be loaded *before* doing the suspend (i'm not sure what
the relationship is between DRI and agpgart).

Comment 6 Alain Wenmaekers 2002-02-26 21:25:03 UTC
DRI and/or AGPGART are not loaded on the Toshiba 8100 (the S3 Savage only has 
2D accelleration in linux), also no kernel modules are loaded for X.
I am not really able to try a new RH version on this machine because it's now 
used as a "stable" development platform.
If I have time this week I will try the newer X version. I will keep you posted.

Comment 7 Mike A. Harris 2002-06-19 18:03:35 UTC
If downgrading APM solved the problem before, then it most likely is not
an XFree86 issue.  APM related problems usually are not XFree86 related,
but tend to be hardware bugs or BIOS bugs which potentially can and sometimes
do get worked around in kernel updates or fixed in BIOS flash updates.
Also, kernel bugs, apmd bugs.  XFree86 bugs do pop up, but the are indeed
rare.  Almost all APM bugs that get resolved are not resolved via XFree86

Reassigning to apmd

Comment 8 Bill Nottingham 2005-02-02 22:46:54 UTC
Closing out bugs on older unsupported releases. Apologies for any lack
of response. Please reopen if it persists on current releases such as
Fedora Core 3.

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