Comment 18 for bug 253089

Revision history for this message
Jamie Lokier (jamie-shareable) wrote :

Just want to comment that I'm using kernel 2.6.27-2.3 (latest on 2008-09-09) and I am still seeing these sort of symptoms, and specifically these messages occur before it goes strange:

Sep 9 01:28:46 amilo kernel: [20443.532290] irq 219, desc: c04bbb00, depth: 0, count: 0, unhandled: 0
Sep 9 01:28:46 amilo kernel: [20443.532302] ->handle_irq(): c0176a10, handle_bad_irq+0x0/0x2a0
Sep 9 01:28:46 amilo kernel: [20443.532316] ->chip(): c048f0a0, no_irq_chip+0x0/0x40
Sep 9 01:28:46 amilo kernel: [20443.532325] ->action(): 00000000
Sep 9 01:28:46 amilo kernel: [20443.532329] IRQ_DISABLED set
Sep 9 01:28:46 amilo kernel: [20443.532332] IRQ_MASKED set
Sep 9 01:28:46 amilo kernel: [20443.532336] unexpected IRQ trap at vector db

I am not running Intrepid, but Hardy with an Intrepid kernel, libc and couple of other packages. The reason is that several bugs I'm subscribed to suggest I try the Intrepid kernel and report back if they solve other problems. (So far the new kernel causes quite a lot of new problems...).

My laptop is a Fujitsu-Siemens Amilo Si-1520, Core Due (32-bit) 2.0GHz, 2.5MB RAM.

I don't know if it's relevant, but on booting I always get this message with the new kernel:

    ACPI: EC: GPE storm detected, disabling EC GPE

Some other places suggest it's due to a flaw in Acer laptops, but this is not an Acer laptop.

I've attached the output of /proc/interrupts, dmidecode, lspci -v and lsusb -v in case they are useful.
They were made about 10 minutes after the strange behaviour and kernel message about the interrupt started.