Comment 13 for bug 253089

Now I got it again, first time after 5 hours 40 minutes uptime:

[19486.431597] irq 219, desc: c0481c00, depth: 0, count: 0, unhandled: 0
[19486.431597] ->handle_irq(): c016f730, handle_bad_irq+0x0/0x2a0
[19486.431597] ->chip(): c04562c0, no_irq_chip+0x0/0x40
[19486.431597] ->action(): 00000000
[19486.431597] IRQ_DISABLED set
[19486.431597] IRQ_MASKED set
[19486.431597] unexpected IRQ trap at vector db

I have done archive admin all the day, i. e. just worked with ssh, firefox, and gnome-terminal. The only thing I changed over the lunch break was to switch off my monitor.

I attach my current /proc/interrupts now. Mostly the diff is just higher counts (which is to be expected), but there's one additional line:

  219: 8 0 none-edge

which seems to correspond to the "unexpected IRQ trap":

$ dmesg |grep "unexpected IRQ trap"|wc -l
8