Well, I read in another thread that there are some issues with this patches. Anyway, I'm now running .26 with your patch since yesterday, tried 3 suspend/resume cycles and 2 hibernate/resume cycles and everything seems to be fine. It looks that it's really solving the problem for me. Thanks for your work. Cheers, Fabio On Sat, Jul 19, 2008 at 2:22 PM, Alan Jenkins <aj504@xxxxxxxxxxxxx> wrote: > Fabio Comolli wrote: >> Hi Alex. >> Well, I read the bug report but still can't understand why in any >> kernels < 2.6.26 I don't have any problems with battery reports and in >> 2.6.26 as soon as the message appears g-p-m starts to behave >> incorrectly. >> >> Anyway, I got back to 25.11 for now, if you have any other workarounds >> for me to test please let me know. > > Hi Fabio. > > I wrote some GPE fixes for my Asus laptop and they need some wider > testing :-). I think I found why we get GPE storms and how to deal > with them. > > I posted them on the lists a series of three patches, but I neglected > to CC any potential testers. For convenience I squished them into a > single patch and posted them in Bugzilla. > > My bug: <http://bugzilla.kernel.org/show_bug.cgi?id=11089> > Patch: <http://bugzilla.kernel.org/attachment.cgi? > id=16886&action=view> > > The risky part of the fixes removes the GPE interrupt storm check and > the GPE polling mode. So you won't see the "disabling EC GPE" message, > and I'm hoping this will stop g-p-m misbehaving for you. > > I'm not sure what could happen if it's broken somehow :-). If you > have ACPI hotkeys (i.e. running acpi_listen shows events when you > press hotkeys), please check they still work. If not, you should have > at least one button that generates an ACPI event - the power button. > So it would be great if you could check the power button still works > as normal. (On my computer, g-p-m handles the power button and pops > up a logout/shutdown prompt). > > Thanks > Alan > -- 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
