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? > > 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 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? > I think we have the same bug on battery module, because sometimes i > need to cat /proc/acpi/battery/BAT*/state do have a proper report of > battery level. Do you have a patch for this too? > I'll cook up one soon. :) thanks for remindering. thanks, rui -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
