Bug 9354
| Summary: | ACPI Error attaching device data | ||
|---|---|---|---|
| Product: | ACPI | Reporter: | robert (robert) |
| Component: | ACPICA-Core | Assignee: | Lin Ming (ming.m.lin) |
| Status: | CLOSED CODE_FIX | ||
| Severity: | normal | CC: | acpi-bugzilla, rufus-azrael, rui.zhang |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.24-rc2 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Attachments: |
acpidump
dmesg log for x86 lspci -vvxxx for x86_64 Debug patch dmesg patch mentioned in comment #4 dmesg |
||
|
Description
robert
2007-11-11 18:02:45 UTC
already mentioned on http://www.mail-archive.com/linux-acpi@vger.kernel.org/msg05865.html Created attachment 13500 [details]
acpidump
Part of AML for the NG machine. Seems like Alias description is reason....
DefinitionBlock ("NG/DSDT.aml", "DSDT", 1, "HP ", "ML115 G1", 0x00000100)
{
:
Scope (_PR)
{
Processor (P001, 0x01, 0x00002010, 0x06) {}
Processor (P002, 0x02, 0x00000000, 0x00) {}
Alias (P001, CPU1)
Alias (P002, CPU2)
}
:
}
This may be fixed in ACPICA 20071019: Fixed a problem with the Alias operator when the target of the alias is a named ASL operator that opens a new scope -- Scope, Device, PowerResource, Processor, and ThermalZone. In these cases, any children of the original operator could not be accessed via the alias, potentially causing unexpected AE_NOT_FOUND exceptions. (BZ 9067) Thank you. I am not familier with ASL. Excuse me, how to check whether the ACPICA 20071019 is ok or not on the above kernels? Regards Will you please attach the following info? a. dmesg b. lspci -vvxxx Thanks. Created attachment 13576 [details]
dmesg log for x86
Created attachment 13577 [details]
lspci -vvxxx for x86_64
The machine is used for other project now.
I only have the output of lspci -vvxxx is for x86_64 on kernel-2.6.18-8
If it has problem for analysis, please let me know.
I will try to send x86 one.
Thank you for help.
Ming and Bob, what's the status of this bug? Is the fix already included in the recent ACPICA release? Created attachment 15421 [details]
Debug patch
Please apply this debug patch and attach the FULL dmesg output after boot. :)
we need to get the fix from ACPICA 20071019 and attach a linux version here. Created attachment 15740 [details]
dmesg
after kernel-2.6.25-rc9 vanilla patched with the proposed patch
"ACPI Error attaching device data" should always be shown if Alias device exists in the ACPI namespace. Linux OS builds a device node for every ACPI device and trys to attach this data to the device node in ACPI namespace. For Linux, alias devices are two devices while they share the same ACPI namespace node, attaching two device data to the same device handle causes the acpi_attach_device returns AE_ALREADY_EXISTS. Ming, do we have a fix for this? Hmm, they don't share the some namespace node, the two nodes share the same attached object. And acpi_attach_data will attach the data to the attached object, which is the same for these two Linux devices. Working with Ming, and we found that in Linux (ACPICA20070126), the type of Alias device CPU1 is "processor", thus Linux will add a duplicate processor device. But when using later ACPICA release, the type of CPU1 is "Alias", in this case, Linux should not add a device node for CPU1. So I think this bug should be fixed in the recent Linux ACPICA update. Ming will check if the patch is already in the patch set Len sent on 4/12/2008. Created attachment 15744 [details] patch mentioned in comment #4 Please give it a try Created attachment 15750 [details]
dmesg
The patch works fine for me, each data is attached to a node.
As the patch is already in Len's tree, I think we can mark this bug as RESOLVED. shipped in 2.6.26-rc1 - closed. commit 53cf174409a24e8388e1d554d27436275fc81fe7 Author: Bob Moore <robert.moore@intel.com> Date: Thu Apr 10 19:06:39 2008 +0400 ACPICA: Fix for Alias operator to see target child objects |