Bug 26261 - [poweroff] System reboots instead of halt/poweroff
Summary: [poweroff] System reboots instead of halt/poweroff
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: David Lawrence
Whiteboard: Florence Gold
Depends On:
TreeView+ depends on / blocked
Reported: 2001-02-06 00:15 UTC by P. Beltrani
Modified: 2007-04-18 16:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2001-02-14 06:32:05 UTC

Attachments (Terms of Use)

Description P. Beltrani 2001-02-06 00:15:11 UTC
System info from syslog:

 kernel: BIOS Vendor: Award Software, Inc.
 kernel: BIOS Version: ASUS K7V ACPI BIOS Revision 1007
 kernel: BIOS Release: 07/26/2000
 kernel: Board Vendor: ASUSTeK Computer INC..
 kernel: Board Name: <K7V>.
 kernel: Board Version: REV 1.xx.
 kernel: apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)

 kernel: ACPI: System description tables found
 kernel: ACPI: System description tables loaded
 kernel: ACPI: APM is already active, exiting

All attempts to shutdown the system via the OS result in a reboot not a
halt or power off.

  shutdown -h now
  init 0
  telinit 0
  halt -p
 result in reboot.

Additional info:

 I needed to replace glibc i686 with the i386 version as a work around for
other issues.  This had no impact on the problem.

The above commands work as expected with RH 7.0 on the same hardware.

Comment 1 Bill Nottingham 2001-02-06 00:30:00 UTC
This is probably a kernel problem in how it reboots the machine; the associated
code in SysVinit hasn't changed.

Comment 2 Arjan van de Ven 2001-02-06 10:42:31 UTC
Might be ACPI related. (However, using an older kernel, my Asus A7V powers 
down nicely).

Comment 3 Jay Berkenbilt 2001-02-06 18:47:48 UTC
I think it is a kernel problem but it may also be an init problem or a glibc
problem.  I was about to report a similar bug but found this in my query. 
Here's some additional input.  I have an ASUS P2B-LS motherboard with BIOS
revision 1012.  It is APM and ACPI-compliant.  The kernel reports:

apm: BIOS version 1.2 Flags 0x03 (Driver version 1.14)

/proc/apm looks sensible, apmd works, etc.

halt -p results in loss the kernel printing "Power Down" and in keyboard input
not working anymore, but power does not go off.  I've always been able to power
down this way in previous releases.

If I boot into single user mode and do this:

umount -a -t noproc
mount -o ro,remount /
strace halt -f -p

the strace output ends with the following:

       LINUX_REBOOT_CMD_RESTART|0x88888888) = 0
kill(1, SIGTSTP)

Perhaps the first line explais why the original reporter of this bug gets a
reboot.  I haven't looked at the init code to see what it's actually doing or
whether this code comes from something in glibc.  Looking at the reboot(2)
manual page and doing what it says results in EINVAL from reboot().  Perhaps the
documentation is out of date or I did it wrong.  The manual page shows reboot()
having four arguments, but strace only shows three.  Hopefully this additional
information will provide some more clues.

Comment 4 Glen Foster 2001-02-07 00:19:39 UTC
We (Red Hat) should really try to fix this before next release.

Comment 5 Alexei Podtelezhnikov 2001-02-07 09:56:25 UTC
Same problem with MSI 6195 (K7Pro) motherboard...

Comment 6 Arjan van de Ven 2001-02-07 10:09:12 UTC
 halt -p results in loss the kernel printing "Power Down" and in keyboard input
 not working anymore, but power does not go off.  I've always been able to power
 down this way in previous releases.
Sounds like ACPI to me.

Comment 7 P. Beltrani 2001-02-08 02:26:51 UTC
As ACPI was mentioned, I restarted the system with the
kernel parameter "apm=off"

This results in the following on boot:
 kernel: ACPI: System description tables found
 kernel: ACPI: System description tables loaded
 kernel: ACPI: Subsystem enabled
 kernel: ACPI: System firmware supports: C2
 kernel: ACPI: System firmware supports: S0 S1 S3 S4 S5

With this configuration, attempts to power down with "poweroff" etc. result in
the usual power down display ending with:

Power down
ACPI: S5 failed

Then the system is locked and must be reset or powered off manually.

Comment 8 Arjan van de Ven 2001-02-08 09:59:25 UTC
"ACPI: S5 failed" says basically "Ehhh your bios is borked."
Now, this can be the Bioses fault, or a bug in the ACPI code.

Comment 9 Michael K. Johnson 2001-02-08 23:29:10 UTC
We are no longer building ACPI support into the kernel, so
this should go away in future kernels.

Comment 10 Michael K. Johnson 2001-02-09 00:34:58 UTC
*** Bug 26444 has been marked as a duplicate of this bug. ***

Comment 11 P. Beltrani 2001-02-09 03:28:30 UTC
Re: this going away when ACPI is no longer built into the kernel

I know those of you working on this have more clue than I do. Would you help me
understand why you think this is an ACPI issue?

As I understand the log file in the original post, ACPI exits because "APM is
already active" It's not until I turned of APM that I received an actual ACPI error.

Also, for what it's worth, I just built a kernel WITHOUT ACPI support. The
problem is still there. If you care to send me a .config with your build
preferences I would be happy to build a kernel and test it on this hardware.

Comment 12 Jay Berkenbilt 2001-02-11 20:15:49 UTC
I hope someone will reopen this bug.  I can't since I was not the poster.

I tried poweroff with the rawhide kernel (no ACPI support) and with
2.4.1 (with ACPI).  The behavior is unchanged -- on my ASUS P2B-LS rev 1012, I
still do not get power down -- just the message and locking keyboard.

Comment 13 P. Beltrani 2001-02-12 22:12:36 UTC
Somewhere along the line this was flagged as an ACPI issue. The "fix"  then
became the fact that ACPI support will no longer be included in the kernel builds.

Two of us have built kernels without ACPI support yet the problem is still there.

Could we please take another look at this one?

Comment 14 Arjan van de Ven 2001-02-13 10:29:37 UTC
Ok. Not an ACPI issue. The difference between the 7.0 kernel and the
fisher kernel is that the 7.0 kernel has "REAL_MODE_POWEROFF" disabled,
while the fisher kernel has it enabled. It would be real helpful if
someone can confirm changing this option fixes this bug for them.

Comment 15 P. Beltrani 2001-02-13 13:38:51 UTC
This worked for my system, ASUS K7V ACPI BIOS Revision 1007

1) Built quick/dirty kernel:
  Created .config using the defaults from "make xconfig".
  The only change from the defaults was
  Built a bzImage.  Did NOT build/install modules

2) Booted with test kernel.

3) poweroff and init 0 work as expected.

Comment 16 Arjan van de Ven 2001-02-13 15:05:56 UTC
Thanks for testing + confirming this. Newer kernels will have this change.

Comment 17 Jay Berkenbilt 2001-02-13 16:45:00 UTC
I'll test this tonight when I'm at home -- testing power off remotely is pretty
hard! :-) I'll report back with the result regardless.

Comment 18 Jay Berkenbilt 2001-02-14 06:32:02 UTC
Building a kernel with REAL_MODE_POWEROFF disabled worked for me too.  Thanks. 
Just for kicks, I also disabled ACPI, so both of these being off works in my

Comment 19 Arjan van de Ven 2001-02-14 09:54:47 UTC
Ok. That's enough for me. REAL_MODE_POWEROFF is gone for the next build that
will appear in Rawhide.

Comment 20 Elton Woo 2001-03-11 21:39:49 UTC
I reported this to the Wolverine list, and am adding a comment here, in the
hopes that it would
be of use to the development team. My system: AOPEN AX59PRO ATX, rev. 2.35. 
Since installing
the latest updates (including the 2.4.2-0.1.19 kernel), I can halt the system,
but not power *off*.

Comment 21 Arjan van de Ven 2001-03-11 21:49:39 UTC
What was the last working kernel ?
and could you please try adding
to the lilo.conf file ?

Comment 22 Elton Woo 2001-03-12 21:17:52 UTC
The previous working kernel that I had in Wolverine was 2.4.1.-0.1.9  For
the moment, I cannot report on the success or failure WRT the amendment to my
lilo.conf file, which I have edited per your suggestion.

Comment 23 Elton Woo 2001-03-12 22:20:35 UTC
My lilo.conf now contains:

	append="scd0=ide-scsi apm=realmode"

Still no luck. A "shutdown" merely terminates all services, but does NOT power
the machine.

Comment 24 Elton Woo 2001-03-14 17:10:46 UTC
I've just upgraded to kernel 2.4.2.-0,.1.25. The system now powers off without
the need
to add "apm=realmode" ro my lilo.conf.

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