http://bugzilla.kernel.org/show_bug.cgi?id=13268
Summary: ACPI interrupt storm
Product: ACPI
Version: 2.5
Kernel Version: 2.6.29.2
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Config-Interrupts
AssignedTo: [email protected]
ReportedBy: [email protected]
Regression: No
Created an attachment (id=21264)
--> (http://bugzilla.kernel.org/attachment.cgi?id=21264)
acpidump output
Further details as requested...
Slight change of conditions - turned off the fglrx kernel module and compiled a
2.6.29.2 kernel. Experienced the same "storm".
interrupts, dmesg and acpi information attached.
The following text is duplicated from the linux-acpi mailing list for
reference:
Subject: System overloaded with ACPI interrupts
Hello,
I think I'm experiencing some kind of ACPI issue, I haven't been able
to identify a series of actions that causes this.
I first noticed the problem when looking at 'top' - seeing kacpi at
the top of the process list (followed by kacpi_notify).
I have powertop installed, the dump is attached - acpi interrupts seem
to be excessive.
The computer is perhaps not the best machine: Arima M620-DC. I think
the same chassis may be used by a number of other manufacturers.
The system does not boot in this state - it occurs rather
unpredictably after high CPU loads. I had thought this was a CPU
temperature issue and replaced the thermal paste of the heatsink,
which improved matters.
I have also blacklisted the following modules:
blacklist i2c_i801
blacklist yenta_socket
The kernel reports a conflict between ACPI SBUS and i2c_i801.
I forget why I disabled yenta_socket, but I don't use the card reader.
The OS is openSuSE 11.1 with the 2.6.27.21-0.1-default kernel installed.
I've also tried booting the system with acpi=noirq. This gives a 'irq
5: nobody cared' and the wireless card (ipw2200) then doesn't work.
My normal kernel command line contains the following parameters:
hpet=force lapic vga=0x317
This is what all the attached logs are generated from and when my
system functions with all devices working.
I have also disassembled the ACPI tables. I can post them if required?
Hopefully someone can suggest a temporary solution or a permanent one?
Thanks,
Chris
The response:
hi,
please try a recent vanilla kernel and see if it's reproducible. 2.6.29
would be a good choice.
if the problem still exists in 2.6.29 kernel, please attach the output
of dmesg and "grep . /sys/firmware/acpi/interrupts/*" after the
interrupt storm occurs.
please also attach the acpidump of this laptop.
it would be great of you can open a new bug report at
http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI
and attach all the info there.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
acpi-bugzilla mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
