http://bugzilla.kernel.org/show_bug.cgi?id=9998
------- Comment #24 from [EMAIL PROTECTED] 2008-02-26 01:59 ------- (In reply to comment #23) > On a working system, you should be able to kill acpid > (simply to disable the action on the interrupt) > and press the power or lid buttons and see /proc/interrupts increment. Yup. > I expect with acpi_sci=edge, "grep acpi /proc/interrupts" will stay at 1. Yup. > If you boot 2.6.24 with CONFIG_ACPI_SBS=n, does "grep acpi /proc/interrupts" > still show the acpi interrupt increasing at a high rate? No, it stay's quite low (<10.000 after a few minutes). However the storm seems to be caused by accessing the battery, which is not possible without the sbs module. What I mean is: Possibly there is something wrong outside the sbs-code, but it doesn't get triggered. Anyway, you're the expert here :) > # cd /sys/firmware/acpi/interrupts > # grep . * error:0 ff_gbl_lock:0 ff_pmtimer:0 ff_pwr_btn:0 ff_rt_clk:1 ff_slp_btn:0 gpe00:0 gpe01:0 gpe02:0 gpe03:0 gpe04:0 gpe05:0 gpe06:0 gpe07:0 gpe08:0 gpe09:0 gpe0A:0 gpe0B:0 gpe0C:0 gpe0D:0 gpe0E:0 gpe0F:0 gpe10:0 gpe11:0 gpe12:0 gpe13:0 gpe14:0 gpe15:0 gpe16:0 gpe17:0 gpe18:0 gpe19:0 gpe1A:0 gpe1B:0 gpe1C:0 gpe1D:443152 gpe1E:0 gpe1F:0 gpe_all:443152 sci:443153 > # grep acpi /proc/interrupts 9: 559889 XT-PIC-XT acpi Typing was quite difficult, so several seconds passed between the two commands. -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
