Bug 8360 - ACPI Error - Namespace lookup failure, AE_NOT_FOUND
Summary: ACPI Error - Namespace lookup failure, AE_NOT_FOUND
Status: REJECTED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: ACPICA-Core (show other bugs)
Hardware: i386 Linux
: P2 normal
Assignee: Robert Moore
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-22 07:40 UTC by Sunil Naidu
Modified: 2009-12-11 10:10 UTC (History)
3 users (show)

See Also:
Kernel Version: 2.6.20.7 & 2.6.21-rc7
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Sunil Naidu 2007-04-22 07:40:08 UTC
Most recent kernel where this bug did *NOT* occur:
Distribution: FC6
Hardware Environment: Intel P-III
Software Environment: gcc (GCC) 4.1.1 20070105 (Red Hat 4.1.1-51)
Problem Description: ACPI Error, Namespace lookup failure, AE_NOT_FOUND. This
error occurs after 

ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.ICHB._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 11 *12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 9) *11

 
Steps to reproduce: just compile with all relevant ACPI options for Intel/PIII
(sent .config to LKML/Andrew)
Comment 1 Len Brown 2007-04-25 20:20:17 UTC
please attach the output from acpidump.

If it isn't already on your system, you can get it from
the latest pmtools here:
http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/
Comment 2 Adrian Bunk 2007-07-23 04:31:26 UTC
Please reopen this bug if:
- it is still present with kernel 2.6.22 and
- you can provide the requested information.
Comment 3 Oncemore2000 2009-12-11 10:10:26 UTC
Found this issue on kernel 2.6.32.

# dmesg |grep -i error
ACPI Error (dswload-0191): [\_PR_.P001] Namespace lookup failure, AE_NOT_FOUND
nForce2_smbus 0000:00:01.1: Error probing SMB1.
 
-----
CPU: Dual-Core AMD Opteron(tm) Processor 
kernel version: 2.6.32

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