Re: ACPI notify handler and reentrancy of WMI device.

[Lin Ming <ming.m.lin@intel.com>]

> From: Corentin Chary <corentin.chary@gmail.com>
> Date: Mon, Jan 17, 2011 at 2:18 AM
> Subject: ACPI notify handler and reentrancy of WMI device.
> To: linux acpi <linux-acpi@vger.kernel.org>
> Cc: platform-driver-x86@vger.kernel.org, Len Brown
> <len.brown@intel.com>, Matthew Garrett <mjg@redhat.com>
> 
> 
> Hi,
> I currently trying to fix a bug on the Eeepc 1000H with eeepc-wmi.
> 
> 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

Hi, 

Could you attach the acpidump output?

Thanks,
Lin Ming

> 
> Then it'll work.
> 
> What's the best way to avoid that ?
> - Is there some way to tell acpica that this method should be serialized ?
> - Is there some way to finish the execution of the first WMBC call in
> the notify handler ?
> - Should I use a work queue, and do what I have to do later (when the
> previous call is finished) ?
> - anything else ?
> 
> Thanks,
> 
> --
> Corentin Chary
> http://xf.iksaif.net
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html