Bug 433854 - System hangs without acpi=off
System hangs without acpi=off
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
i686 Linux
low Severity high
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-02-21 13:58 EST by Alexander
Modified: 2008-06-16 23:01 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-06-16 23:01:47 EDT
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 Alexander 2008-02-21 13:58:32 EST
Description of problem:

I upgraded my FC6 to FC7 recently. With new kernels I can successfully boot, but
when gdm is starting (in runlevel 5) system hangs without any records in
/var/log/messages. If I booted in runlevel 3, I can do some actions, but if i
type, for example, "set" and try tab-completion, system hangs too, guaranteed.
If I boot with acpi=off, all are ok, but ACPI don't work.
When I boot with any last FC6 kernels (, for example), all are
ok. FC6 had this problem some period, after 2.6.19-1.2911.6.5.fc6, but it was
repaired in several kernel releases.
I tried compile vanilla kernels and 2.6.25-rc2, and system hangs too.
My machine is LG LS75 Express notebook, Intel Pentium M 760 processor, Intel
915PM + ICH6-M chipset, IDE hdd, Nvidia GF Go 6600, intel-hda + CMI9880 sound
and etc.

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

How reproducible:
Boot in runlevel 5 with gdm, or boot in runlevel 3, login and try to work some time.

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Bug Zapper 2008-05-14 11:20:27 EDT
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '7'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 7's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 7 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug. If you are unable to change the version, please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 2 Bug Zapper 2008-06-16 23:01:45 EDT
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 is no longer maintained, which means that it will not 
receive any further security or bug fix updates. As a result we 
are closing this bug. 

If you can reproduce this bug against a currently maintained version 
of Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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