Re: ACPI notify handler and reentrancy of WMI device.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jan 17, 2011 at 7:51 AM, Corentin Chary
<corentin.chary@xxxxxxxxx> wrote:
>>> I got an acpi notify handler. The notify is triggered when I call WMBC().
>>> In this notify handler, I must re-call WMBC (with some other arguments, it won't
>>> notify again this time).
>>>
>>> If I do that, I'll get:
>>> [ Â176.920391] ACPI Error (dswload-0802): [_T_0] Namespace lookup
>>> failure, AE_ALREADY_EXISTS
>>> [ Â176.920416] ACPI Exception: AE_ALREADY_EXISTS, During name
>>> lookup/catalog (20100428/psloop-231)
>>> [ Â176.920439] ACPI Error (psparse-0537): Method parse/execution
>>> failed [\AMW0.WMBC] (Node f7023b88), AE_ALREADY_EXISTS
>>> [ Â176.920469] ACPI: Marking method WMBC as Serialized because of
>>> AE_ALREADY_EXISTS error
>>
>> Could you attach the acpidump output?
>
> Here it is

Ooops

-- 
Corentin Chary
http://xf.iksaif.net

Attachment: acpidump.gz
Description: GNU Zip compressed data


[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux