Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 80337

Summary: Phoebe dos not boot on IBM Thinkpad A31P
Product: [Retired] Red Hat Linux Reporter: Vidyut Luther <vid>
Component: kernelAssignee: Jeff Garzik <jgarzik>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: high    
Version: 9CC: nitind, peterm
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-21 18:50:33 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:
Bug Depends On:    
Bug Blocks: 79578    
Attachments:
Description Flags
Output of acpidmp
none
output of dmidecode none

Description Vidyut Luther 2002-12-24 18:09:19 UTC
Description of problem:
If a clean install of phoebe is executed, the laptop will not boot, spewing
errors about ACPI, pressing the A key when Grub shows the options for boot, and
entering linux acpi=off lets you boot the sytem without any problems.

Version-Release number of selected component (if applicable):
8.0.92 Kernel version:  2.4.20-2.2

How reproducible: very.. tried 3 times.


Steps to Reproduce:
1. Buy Thinkpad A31P
2. Install Phoebe 
3. Try to boot into Phoebe
    
Actual results:


Expected results:


Additional info:
I have attached the output of dmidecode and acpidmp

Comment 1 Vidyut Luther 2002-12-24 18:10:47 UTC
Created attachment 88892 [details]
Output of acpidmp

Comment 2 Vidyut Luther 2002-12-24 18:11:31 UTC
Created attachment 88893 [details]
output of dmidecode

Comment 3 Jeff Garzik 2003-01-18 23:55:12 UTC

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

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