Bug 80811 - no poweroff without "acpi=off"
Summary: no poweroff without "acpi=off"
Status: CLOSED DUPLICATE of bug 82123
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel (Show other bugs)
(Show other bugs)
Version: 1.0
Hardware: athlon Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Garzik
QA Contact: Brian Brock
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 79579
TreeView+ depends on / blocked
 
Reported: 2002-12-31 16:44 UTC by Michael Stefaniuc
Modified: 2013-07-03 02:09 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 18:50:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
output of dmidecode (7.77 KB, text/plain)
2002-12-31 16:46 UTC, Michael Stefaniuc
no flags Details

Description Michael Stefaniuc 2002-12-31 16:44:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

Description of problem:
I recompiled the kernel from kernel-source-2.4.20-2.2.i386.rpm on Red Hat Linux
7.3 and this kernel dosn't poweroffs the machine whithout "acpi=off" on a halt -p.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.boot the 2.4.20-2.2 kernel without "acpi=off"
2.login and type as root "halt -p"
3.
    

Actual Results:  The HD's are spinning down but the machine dosn't poweroff.

Expected Results:  The machine should poweroff

Additional info:

output of dmidecode will be attached

Comment 1 Michael Stefaniuc 2002-12-31 16:46:39 UTC
Created attachment 89013 [details]
output of dmidecode

This is the output of dmidecode with the latest stable Asus A7V BIOS

Comment 2 Jeff Garzik 2003-01-17 21:44:41 UTC

*** This bug has been marked as a duplicate of 82123 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:50:48 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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