Kernel IRQ alert?

[mhammett]

Nov 26 08:05:36 Fenix kernel:
Nov 26 08:05:36 Fenix kernel: Call Trace:
Nov 26 08:05:36 Fenix kernel: <IRQ> [<ffffffff800c3c58>] __report_bad_irq+0x30/0x7d
Nov 26 08:05:36 Fenix kernel: [<ffffffff800c3e8b>] note_interrupt+0x1e6/0x227
Nov 26 08:05:36 Fenix kernel: [<ffffffff800c337d>] __do_IRQ+0xbd/0x103
Nov 26 08:05:36 Fenix kernel: [<ffffffff8006e1d4>] do_IRQ+0x13f/0x14d
Nov 26 08:05:36 Fenix kernel: [<ffffffff80060665>] ret_from_intr+0x0/0xa
Nov 26 08:05:36 Fenix kernel: <EOI>

The screen had an alert about IRQ 50 and shut down that IRQ. What does that mean?

 

[tom]

post also your pveversion -v as a reference.

 

[mhammett]

Fenix:~# pveversion -v
pve-manager: 1.6-5 (pve-manager/1.6/5261)
running kernel: 2.6.18-2-pve
proxmox-ve-2.6.18: 1.5-5
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-22
pve-firmware: 1.0-9
libpve-storage-perl: 1.0-14
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-8
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm-2.6.18: 0.9.1-8

I did just upgrade, however, I don't think it affected any of the kernels.

 

[SamTzu]

I too have had many kernel oops on my test server. pve-manager: 1.6-5 (pve-manager/1.6/5261)
I was about to try to install OpenQRM and started copying the VM's to safety when I noticed that if all the KVM test machines are shut down then the test server works fine.
Looks like a KVM issue to me. I only have 2 KVM test machines running at the moment. OpenBSD & Windows7.