https://bugzilla.novell.com/show_bug.cgi?id=387207
User trenn@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=387207#c40
--- Comment #40 from Thomas Renninger
Then just waited for the ACPI interrupts to show a spike How often does that happen? Do the interrupts also calm down for a while, do you have to wait for something that triggers the irq storm? You can also use: watch -n1 cat /proc/interrupts The ACPI interrupts should increase rapidly? Can you give an estimation how much there are per second by e.g. cat /proc/interrupts;sleep 10; cat /proc/interrupts
Does it help if you unload or better not load the battery module? Best copy away battery.ko temporarily: mv /lib/modules/`uname -r`/kernel/drivers/acpi/battery.ko /lib/modules reboot. Do not forget to move the battery.ko driver back when you finished tests(especially if it is not the problem or you will miss battery status): mv /lib/modules/battery.ko /lib/modules/`uname -r`/kernel/drivers/acpi/battery.ko I wonder if this is really related to battery or whether we still do not see what kind of ACPI interrupts/GPEs are processed. If the problem persists, maybe you can again increase acpi debug level, but this time set to 0x21f instead 0x1f (with battery still unloaded). Better copy away the relvant parts from /var/log/messages now, then we have the time how often things happen. You may want to do: logger XXXXXXXXXX before the commands you increase acpi_debug level. Then you can search /var/log/messages for it and know when you started debugging. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.