Bug 87710 - power button doesn't work as expected
power button doesn't work as expected
Status: CLOSED WONTFIX
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
9
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Arjan van de Ven
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-01 12:14 EST by Carlos Morgado
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-08 10:58:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Carlos Morgado 2003-04-01 12:14:43 EST
The power button of the Toshiba Satellite 3600 is 'soft off' 
so you are supposed to press it for 4 seconds to make it
poweroff. 
With kernel-2.4.20-8 a simple touch to power button turns
it off. This is due to lack of ACPI.

Expected: 
Single touch doesn't do anything, you get reminded there's no
hybernate function

Actual result:
Single touch power off machine == crash
Comment 1 Matt Wilson 2003-04-01 12:23:05 EST
what kind of crash?   Oops?
Comment 2 Carlos Morgado 2003-04-01 12:42:11 EST
Sorry, I meant "power off machine equals crash", as in the machine turns power
off stone cold dead.
Comment 3 Arjan van de Ven 2003-04-11 09:40:50 EDT
"push power button"  -> "machine powers off"

that sounds just like what I would expect from a power button.....
Comment 4 Carlos Morgado 2003-05-16 09:30:45 EDT
No, "press the button 4 seconds" -> "machine powers off" is what is expected for
this machine. For power up you also need to press for a couple of seconds.
A single touch is supposed to do nothing or sleep/hibernate/whatever.
Comment 5 Alan Cox 2003-06-08 10:58:59 EDT
Thats BIOS controlled so beyond our ability to fix. When ACPI is ready enough I
suspect the ACPI kernel will solve this for you

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