On Tue, Nov 2, 2010 at 2:16 AM, Zhang Rui <rui.zhang@xxxxxxxxx> wrote: > On Tue, 2010-11-02 at 04:10 +0800, Seblu wrote: >> On Mon, Nov 1, 2010 at 1:44 AM, Zhang Rui <rui.zhang@xxxxxxxxx> wrote: >> > will you please attach the acpidump output of this laptop? >> yes, sure. > > does the error message pop up every time you boot the kernel? If you speak about dmesg error message like the following ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20101013/evregion-474) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV.ECR1] (Node ffff880213058c08), AE_TIME (20101013/psparse-537) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV.ECR2] (Node ffff880213058c30), AE_TIME (20101013/psparse-537)the ACPI Error: Method parse/execution failed [\ECRW] (Node ffff880213058d98), AE_TIME (20101013/psparse-537) ACPI Error: Method parse/execution failed [\ECG1] (Node ffff880213058de8), AE_TIME (20101013/psparse-537) ACPI Error: Method parse/execution failed [\NEVT] (Node ffff88021305a168), AE_TIME (20101013/psparse-537) ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.ECDV._Q66] (Node ffff880213058be0), AE_TIME (20101013/psparse-537) yes, these lines is present at each startup. > >> > please try the patch attached to see if it helps. >> > BTW, the patch is based on today's git tree. and there may be some >> > conflict if you use 2.6.36 kernel. >> Right, i join my version to test it on 2.6.35.8. >> >> I've tested after many startup (from shutdown or reboot) on 2.6.35.8 >> and on linux-next-2010-10-29 and this seems to fix the issue. Thanks! >> > good to know. > But I'm still confused about this problem. > you can get the notifications every time you plug or unplug the AC > adapter, right? > > here is how ACPI AC driver works: > 1. plug/unplug AC > 2. AC driver receives notification (done by BIOS) > 3. update the AC status (in notification hander) > 4. send notification to userspace (in notification handler) > 5. user space query AC status when receiving the notification > thx ! > as we can see, the AC status is already updated in step 3, that's why AC > driver returns a cached value to user space in step 5. > But apparently this is broken in your case. > > This makes me wondering if BIOS forgets to do step 2, thus AC driver > does not update the AC status. But you can catch the AC plug/unplug > event every time which suggest the notification is sent correctly. > > Seblu, > will you please plug and unplug the AC adapter for several times and > attach the output of "grep . /sys/firmware/acpi/interrupts/*" every time > you plug or unplug the AC adapter? > done with 2.6.37-rc1 and your patch (which fix my screen issue \o/) -- Sébastien Luttringer www.seblu.net
Attachment:
plug-test.tar.gz
Description: GNU Zip compressed data
