Re: System overloaded with ACPI interrupts

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Rui,

as requested - further details here:

http://bugzilla.kernel.org/show_bug.cgi?id=13268

Chris

On Wed, May 6, 2009 at 6:48 AM, Zhang Rui <rui.zhang@xxxxxxxxx> wrote:
> 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.
>
> thanks,
> rui
>
>
> On Mon, 2009-05-04 at 18:00 +0800, Christopher HORLER wrote:
>> 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
>
>
--
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

[Index of Archives]     [Linux IBM ACPI]     [Linux Power Management]     [Linux Kernel]     [Linux Laptop]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux