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 102581

Summary: (ACPI) ThinkPad T30: ACPI panic on halt
Product: [Retired] Red Hat Linux Beta Reporter: Robert de Rooy <rderooy>
Component: kernelAssignee: Jeff Garzik <jgarzik>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: beta1CC: acpi-bugzilla, peterm, riel
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-01-18 08:16:40 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: 100644    
Attachments:
Description Flags
system log incl. panic none

Description Robert de Rooy 2003-08-18 12:41:09 UTC
Description of problem:

Doing a shutdown -h now on my IBM ThinkPad T30 results in a panic when the 
system is supposed to power itself down.
The same action works fine on an IBM NetVista A30p

Attached is a log I captured with the panic.
Also note that there is an error in the log for the Embedded Controller
The system has the latest available BIOS version (2.05) and Embedded 
Controller firmware (1.03).

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


How reproducible:
every time

Steps to Reproduce:
1. Install on IBM ThinkPad
2. Issue 'shutdown -h now'
3. watch panic
    
Actual results:
panic

Expected results:
power down

Additional info:

Comment 1 Robert de Rooy 2003-08-18 12:42:39 UTC
Created attachment 93708 [details]
system log incl. panic

Comment 2 Len Brown 2003-08-22 00:51:08 UTC
Perhaps you can test the patch attached to bug 98849 ? 
 

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