Bug 155127
| Summary: | 2.6.11-1.14_FC3 poweroff always fails | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Martin <mgansser> | ||||||
| Component: | kernel | Assignee: | Dave Jones <davej> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Brian Brock <bbrock> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 4 | CC: | acpi-bugzilla, akwasi_amponsah, andy.piper, appsdev, barryn, bernhard.jantscher, bubazoo, claude.walston, cwrlau, ed, fonz, gajownik, germano.massullo, hcnegro, jcc103, jroyse, kain, mattdm, mgansser, mitch48, mroch, nphilipp, patrick.pichon, pfrields, philip.r.schaffner, pri.rhl1, rmy, romildo, rtresidd, rvokal, standingbear, tmraz | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | i686 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2006-01-12 23:45:40 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Martin
2005-04-16 18:11:47 UTC
On a Dell N-series 370, issuing poweroff from within X hangs the system (can't switch to a virtual console, but didn't try logging on over the network). If I initiate a shutdown via acpid (by momentarily hitting the power switch), it goes down fine. Just changed my kernel line in grub.conf to
kernel /boot/vmlinuz-2.6.11-1.14_FC3 ro root=LABEL=/1 rhgb quiet
acpi=ht
rebooted, shut down, and achieved power off! Now, can anyone explain
why this works?
AFAIK, "acpi=ht" disables much of the kernel's ACPI support. Maybe that's why it's working for you. It would be good to try a kernel with *both* of the following patches applied, and see if that fixes the problem: http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm4/broken-out/acpi-poweroff-fix.patch http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm4/broken-out/acpi-poweroff-fix-fix.patch (They're in the Linux ACPI BitKeeper tree, so they'll probably be incorporated into the mainline kernel by 2.6.13. I have no idea if they'll be incorporated by 2.6.12 however.) Didn't work for me, the acpi=off or acpi=ht parameters just does my kernel boot freezing very early. Screenshot here https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=115424 I'm a bit reluctant to patch and compile an kernel tough, I hope those patches (if fixes) will be incorporated soon. 2.6.11-1.27_FC3 fixes this for me. An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which may contain a fix for your problem. Please update to this new kernel, and report whether or not it fixes your problem. If you have updated to Fedora Core 4 since this bug was opened, and the problem still occurs with the latest updates for that release, please change the version field of this bug to 'fc4'. Thank you. in the meantime i switched to fc4, kernel-2.6.12-1.1398_FC4 problem still exists with this new kernel. Created attachment 116839 [details]
acpidmp output
acpidmp output
Created attachment 116840 [details]
dmidecode output
kernel-2.6.12-1.1446_FC5 seems to print more messages, but power off fails again: Halting system ... md: md0 switched to read-only mode. ACPI: PCI interrupt for device 0000:02:01.0 disabled ACPI: PCI interrupt for device 0000:00:1f.5 disabled for power-off problem, you should have a look at bug 160775 the problem still exists with 2.6.13 vanilla kernel, the kernel do not poweroff my machine with the MSI Board. Mass update to all FC4 bugs: An update has been released (2.6.13-1.1526_FC4) which rebases to a new upstream kernel (2.6.13.2). As there were ~3500 changes upstream between this and the previous kernel, it's possible your bug has been fixed already. Please retest with this update, and update this bug if necessary. Thanks. Using 2.6.13-1.1526_FC4. Bug still exist. On a Toshiba M50 laptop with Phoenix BIOS. problem still exists with 2.6.13-1.1526_FC4 Why does entering "shutdown -h now" from the command line works but the Gnome/KDE shutdown option will cause this problem? for Comment #16 : I guess Gnome/KDE shutdown gives the same as the command line "poweroff" (with possibly options) and doesn't use "shutdown", now the question is what are the behavious differences between those commands ? 2.6.14-1.1637_FC4 has been released as an update for FC4. Please retest with this update, as a large amount of code has been changed in this release, which may have fixed your problem. Thank you. problem still exists with kernel-2.6.14-1.1636_FC4.i686.rpm a good day for peoples with the mSI MS-6758 (875P Neo) Board. With kernel-2.6.15-1.1823_FC4.i686.rpm the problem doesn't longer exists. 'shutdown -h now' works for me. could you please give a look to https://bugzilla.redhat.com/show_bug.cgi?id=840331 |