Hello, ran into this error for a first time over veru large hardware span/uptime (the server which experienced the error is identical to others, and I had absolutely none of MSI-related problems with this hardware ever). Running 3.10 at host, I had one (of many) VM on it which produced enormous count of context switches due to mess inside (hundreds of active apache-itk workers). All VM threads are pinned to the first sibling for every core on two-head system, e.g. having 24 HT cores and second half is just HT siblings, cpuset cg limits threads only to first. The error itself was produced a second after reset event for this VM (through libvirt, if exact call matters): [7696746.523478] do_IRQ: 11.233 No irq handler for vector (irq -1) Since there are no hints for this exact error recently, and it triggered by critical part of the kernel code, I think it may be interesting to re-raise the issue (or, at least, make a better bound for error source). -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
