Distribution: Slackware-based, mostly self-built
Hardware Environment: IBM ThinkPad 240 - Celeron Mendocino 300, 192MB RAM
Problem Description: System "pauses" for up to a second at a time,
approximately every 10-15 seconds when ACPI is enabled. This corresponds to a
block of anything up to 10 "battery BAT1 00000080 00000001" events being
generated. Running top shows "events/0" clocking up a chunk of CPU time
corresponding to the pause duration each time it occurs.
Under 2.4.25, the battery events always appear in twos.
Steps to reproduce: Simply boot the system with an ACPI-enabled kernel :) I
don't know whether it is ThinkPad 240-specific or whether other systems are
also affected. The pauses are most noticeable when playing audio or video, but
affect everything - when typing, characters will briefly stop being echoed "in
real time", then the system will "catch up" when the pause ends.
please attach the acpidmp. i want to check it. thanks
Created attachment 2522 [details]
Output of acpidmp
As requested by Shaohua
Sorry for the later. Could you please try the patch in Bug 1433. Thanks.
Created attachment 2923 [details]
Modified patch for 2.6.6
This is basically the same patch as for Bug 1433, but fixed so it applies to
It seems to fix the pauses, but there are now _no_ battery events except when
plugging in/unplugging the mains adaptor - so the battery charge level never
I've noticed that, with 2.6.6 (without the patch), the events only occur singly
instead of in big blocks, but the pauses still occur. Each event seems to add
about 100ms of CPU time to the events/0 process.
still an issue in linux-2.6.9?
The pauses no longer occur in 2.6.9, but neither are there any battery events,
so the charge level never changes, except when the AC adapter is either plugged
in or unplugged.
The "stuck status" problem mentioned above is described in bug 3851, and the
two "interrupt_based_ec" patches attached to that bug fix it in 2.6.10 (with a
minor tweak to make them apply). The battery events then occur in identical
pairs (like under 2.4.25 in the initial bug report) rather than large groups,
and the "pauses" described in this bug no longer occur.