Can't stop!!!

os: OpenSUSE 11.1
mb: ASUS P5V-VM DH

$uname -a
Linux resolver 2.6.27.7-9-pae #1 SMP 2008-12-04 18:10:04 +0100 i686 i686 i386 GNU/Linux

$tail -f /var/log/messages
Mar 2 22:26:57 resolver kernel: IRQ_DISABLED set
Mar 2 22:26:57 resolver kernel: unexpected IRQ trap at vector a3
Mar 2 22:26:57 resolver kernel: irq 163, desc: c053af00, depth: 1, count: 0, unhandled: 0
Mar 2 22:26:57 resolver kernel: ->handle_irq(): c0166904, handle_bad_irq+0x0/0x1e8
Mar 2 22:26:57 resolver kernel: ->chip(): c051ae9c, no_irq_chip+0x0/0x40
Mar 2 22:26:57 resolver kernel: ->action(): 00000000
Mar 2 22:26:57 resolver kernel: IRQ_DISABLED set
Mar 2 22:26:57 resolver kernel: unexpected IRQ trap at vector a3
Mar 2 22:26:57 resolver kernel: irq 163, desc: c053af00, depth: 1, count: 0, unhandled: 0
Mar 2 22:26:57 resolver kernel: ->handle_irq(): c0166904, handle_bad_irq+0x0/0x1e8
Mar 2 22:26:58 resolver kernel: ->chip(): c051ae9c, no_irq_chip+0x0/0x40
Mar 2 22:26:58 resolver kernel: ->action(): 00000000
Mar 2 22:26:58 resolver kernel: IRQ_DISABLED set
Mar 2 22:26:58 resolver kernel: unexpected IRQ trap at vector a3
Mar 2 22:26:58 resolver kernel: irq 163, desc: c053af00, depth: 1, count: 0, unhandled: 0
Mar 2 22:26:58 resolver kernel: ->handle_irq(): c0166904, handle_bad_irq+0x0/0x1e8
Mar 2 22:26:58 resolver kernel: ->chip(): c051ae9c, no_irq_chip+0x0/0x40
Mar 2 22:26:58 resolver kernel: ->action(): 00000000
Mar 2 22:26:58 resolver kernel: IRQ_DISABLED set
Mar 2 22:26:58 resolver kernel: unexpected IRQ trap at vector a3
Mar 2 22:26:58 resolver kernel: irq 163, desc: c053af00, depth: 1, count: 0, unhandled: 0
Mar 2 22:26:58 resolver kernel: ->handle_irq(): c0166904, handle_bad_irq+0x0/0x1e8
Mar 2 22:26:58 resolver kernel: ->chip(): c051ae9c, no_irq_chip+0x0/0x40
Mar 2 22:26:58 resolver kernel: ->action(): 00000000
Mar 2 22:26:58 resolver kernel: IRQ_DISABLED set
Mar 2 22:26:58 resolver kernel: unexpected IRQ trap at vector a3
Mar 2 22:26:58 resolver kernel: irq 163, desc: c053af00, depth: 1, count: 0, unhandled: 0
Mar 2 22:26:58 resolver kernel: ->handle_irq(): c0166904, handle_bad_irq+0x0/0x1e8
Mar 2 22:26:58 resolver kernel: ->chip(): c051ae9c, no_irq_chip+0x0/0x40
Mar 2 22:26:58 resolver kernel: ->action(): 00000000
Mar 2 22:26:58 resolver kernel: IRQ_DISABLED set
Mar 2 22:26:58 resolver kernel: unexpected IRQ trap at vector a3
Mar 2 22:26:58 resolver kernel: irq 163, desc: c053af00, depth: 1, count: 0, unhandled: 0
Mar 2 22:26:58 resolver kernel: ->handle_irq(): c0166904, handle_bad_irq+0x0/0x1e8
Mar 2 22:26:58 resolver kernel: ->chip(): c051ae9c, no_irq_chip+0x0/0x40
Mar 2 22:26:58 resolver kernel: ->action(): 00000000
Mar 2 22:26:58 resolver kernel: IRQ_DISABLED set
Mar 2 22:26:58 resolver kernel: unexpected IRQ trap at vector a3
… unlim

Try booting by adding noapic to the end of the boot line in grub (the first screen you see), see if that makes a difference.

You could also try the failsafe mode.

I would also change the kernel to the default one, any particular reason for using the -pae kernel?

Looks familiar. Ive got the same problem.

You could try cat /proc/interrupts and see whats at the ‘unhandled’ irq.

This problem on my machine isnt fixed so I can’t be much of use,
however I’m convinced its mb/BIOS related, and if you can somehow control the irq assignment to your devices with your BIOS or reset/reshuffle the irq assigment (I can’t) then you would prob. be able to make this go away.

Cheap mb components, crappy BIOS/firmware, thats my quess