Red Hat Bugzilla – Bug 15566
HP OmniBook 6000 reboot hangs system
Last modified: 2008-08-01 12:22:51 EDT
Try to do a shutdown -r now. It goes through all of the init scripts, but when it tries to actually reset the machine, it just ends up locking the
system up rock hard - pop-the-battery required. shutdown -h now works perfectly, though, including powering the system off.
This defect is considered MUST-FIX for Winston Gold-release
Appears to work under 2.2.17pre15 with same .config as stock RH kernel, minus
BTW, pop-the-battery should not be required -- have you tried
holding down the power button for 4 seconds?
CONFIG_FB_ATY=m; are you loading the module?
No, the power for several seconds doesn't seem to work, though now that I've
found it the magic keyhole in the side does =)
And no, doesn't look like the the related module is loaded - with the default
kernel I've got ds, i82365, pcmcia_core, lockd, sunrpc, 3c59x, agpgart,
usb-uhci, and usbcore loaded.
So 2.2.17pre15 with CONFIG_FB_ATY=m still has the problem?
Sorry, should have been clearer - the 2.2.17pre's defaulted to CONFIG_FB_ATY=y.
With this set, I couldn't even get a console at all. So, I disabled it, and
found that I could reboot under the 17pre kernels fine. I haven't tried with =m
yet as I assumed it wouldn't make a difference, but I could if you'd like.
Does (with the rc1 kernel) booting with:
and then running
Yes, that reboots it fine.
OK, I don't think that CONFIG_ATY_FB actually has anything
to do with the problem, probably a red herring.
Does it change anything if you chkconfig apmd off?
Nope, still hangs.
Still present in 7.1 beta 2.
7.1 beta 3. Tried with reboot=warm, cold, bios, and hard, same results - hard
How about apm=no -- does that change it?
Nope - with apm=off ACPI fails to load, and it still locks up on reboot. Also
tried with apm=off, no pcmcia, no apmd, same result.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/