Bug 11725 - 2.6.26 regression - no poweroff - ABIT I-45CV mainboard
Summary: 2.6.26 regression - no poweroff - ABIT I-45CV mainboard
Status: CLOSED CODE_FIX
Alias: None
Product: Timers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Thomas Gleixner
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-09 04:25 UTC by Sven Joachim
Modified: 2012-05-22 14:49 UTC (History)
5 users (show)

See Also:
Kernel Version: 2.6.26.6
Subsystem:
Regression: Yes
Bisected commit-id:


Attachments
Output of acpidump (20.71 KB, application/octet-stream)
2008-10-10 02:32 UTC, Sven Joachim
Details
Output of lspci -vxxx (21.47 KB, application/octet-stream)
2008-10-10 02:34 UTC, Sven Joachim
Details

Description Sven Joachim 2008-10-09 04:25:27 UTC
Latest working kernel version: 2.6.26.5
Earliest failing kernel version: 2.6.26.6
Distribution: Debian sid
Hardware Environment: ABIT I-45CV mainboard, Intel Core 2 Duo E8200, 4 GB RAM
Software Environment: util-linux 2.13.1.1, sysv-rc 2.86
Problem Description: Machine does not power off on halt. All shutdown scripts are executed, the last message is that ACPI state S5 is entered.

Steps to reproduce: Enter Runlevel 0.
Comment 1 ykzhao 2008-10-09 22:50:02 UTC
The 2.6.26.6 kernel can't work while 2.6.26.5 can't work. It seems that it is a regression.
Will you please use git-bisect to identify which commit causes the regresssion?
   Will you please attach the output of acpidump, lspci -vxxx?
   
   Will you please use the command of shutdown instead of halt and see whether the system can be powered off?
   thanks.
Comment 2 Sven Joachim 2008-10-10 02:31:28 UTC
Using git bisect, I found out that the following commit is to blame:

commit 92741d2d653769b582015c6a379e7b46e113435d
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Sat Sep 6 03:01:45 2008 +0200

    clockevents: broadcast fixup possible waiters


The last messages with the broken kernels on shutdown are

Mounting root filesystem read-only... done
Will now halt.
sd 1:0:0:0 [sda] Synchronizing SCSI cache
sd 2:0:0:0 [sda] Stopping disk
ACPI: PCI interrupt for device 0000:03:00.0 disabled
ACPI: Preparing to enter system sleep state S5
Disabling non-boot CPUs ...

And then it hangs.
Comment 3 Sven Joachim 2008-10-10 02:32:53 UTC
Created attachment 18238 [details]
Output of acpidump
Comment 4 Sven Joachim 2008-10-10 02:34:58 UTC
Created attachment 18239 [details]
Output of lspci -vxxx
Comment 5 Shaohua 2008-10-14 20:28:51 UTC
Can you try a latest kernel please? There are a lot of time related fixes recently.
Comment 6 Sven Joachim 2008-10-15 01:06:22 UTC
2.6.27-git5 still doesn't power off. :-(
Comment 7 ykzhao 2008-10-23 20:00:42 UTC
Hi, Sven
    Can the system be powered off if you revert the commit mentioned in comment #2?
    thanks.
Comment 8 Sven Joachim 2008-10-23 23:15:31 UTC
Reverting the commit lets the system power off. I don't know what it might break, though.
Comment 9 Daniel Smolik 2008-10-29 03:59:47 UTC
I have the same problem with Supermicro C2SBC-Q with the same CPU and 1GB Ram.
Last message that I see is:

ACPI: Preparing to enter system sleep state S5
Disabling non-boot CPUs ...

I now run 2.6.27.4. When I in config disable Suspend to Ram and Hibernate, all works. I found another interested thig. If I add to kernel command line serial console console=ttyS0,115200n8 all start working !!!! In minicom on other computer I see:


e1000e 0000:0d:00.0: PCI INT A disabled
e1000e 0000:00:19.0: PCI INT A disabled
ACPI: Preparing to enter system sleep state S5
Disabling non-boot CPUs ...
CPU 1 is now offline
SMP alternatives: switching to UP code
CPU1 is down
Power down.
acpi_power_off called

An machine propper power off.
Comment 10 Julien Langer 2008-11-09 02:06:17 UTC
I have the exact same problem with kernel 2.6.27.5 on an ASUS P5Q-E mainboard.
Comment 11 Sven Joachim 2008-12-25 22:45:30 UTC
In 2.6.28 the problem is gone, at least for me.
Comment 12 Thomas Gleixner 2009-01-14 03:07:06 UTC
Julien, Daniel, does 2.6.28 solve the problem for you as well ?
Comment 13 Julien Langer 2009-01-14 10:26:14 UTC
Yeah, the problem is solved for me in 2.6.28.

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