Bug 167504

Summary: ACPI Error - Invalid owner ID : 00
Product: [Fedora] Fedora Reporter: Parag Warudkar <parag.lkml>
Component: kernelAssignee: Dave Jones <davej>
Status: CLOSED RAWHIDE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: intel-linux-acpi, pfrields, scop, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 2.6.12-1.1450_FC4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-12 17:58:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 165150    

Description Parag Warudkar 2005-09-03 15:39:36 UTC
Description of problem:
I started getting this after upgrading to kernel 2.6.12-1.1447_FC4 -
ACPI-0145: *** Error: Invalid owner_id: 00
    ACPI-0145: *** Error: Invalid owner_id: 00
    ACPI-0145: *** Error: Invalid owner_id: 00
    ACPI-0145: *** Error: Invalid owner_id: 00
    ACPI-0145: *** Error: Invalid owner_id: 00
    ACPI-0145: *** Error: Invalid owner_id: 00
    ACPI-0145: *** Error: Invalid owner_id: 00

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

How reproducible:
Always

Steps to Reproduce:
1. Boot the specified kernel
2. Watch dmesg
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Parag Warudkar 2005-09-05 16:32:03 UTC
New Errors started happening - 

    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.EC0_._Q38]
(Node ffff81005ff408c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.EC0_._Q37]
(Node ffff81005ff40900), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._STA]
(Node ffff81005ff40240), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._STA]
(Node ffff81005ff40240), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.EC0_._Q38]
(Node ffff81005ff408c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.EC0_._Q37]
(Node ffff81005ff40900), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._STA]
(Node ffff81005ff40240), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._STA]
(Node ffff81005ff40240), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BIF]
(Node ffff81005ff40200), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT
    ACPI-0105: *** Error: Could not allocate new owner_id (32 max),
AE_OWNER_ID_LIMIT
    ACPI-0509: *** Error: Method execution failed [\_SB_.PCI0.LPC0.BAT1._BST]
(Node ffff81005ff401c0), AE_OWNER_ID_LIMIT


Comment 2 Parag Warudkar 2005-09-05 16:54:48 UTC
Doesn't happen with 2.6.12-1.1398_FC4

Comment 3 Ville Skyttä 2005-09-11 10:41:07 UTC
I'm seeing similar problems with 2.6.12-1.1447_FC4 on an IBM ThinkPad A30p.    
klaptop says "no power source found", and there's a LOT of the   
above AE_OWNER_ID_LIMIT messages in syslog after a while (not right after  
boot).  

Comment 4 Ville Skyttä 2005-09-11 19:32:36 UTC
2.6.12-1.1450_FC4 from updates/testing seems to fix this for me. 

Comment 5 Parag Warudkar 2005-09-12 17:56:55 UTC
Based on #4 I will close this as fixed. I am using kernel.org kernel for now 
which doesn't have this problem.