Il 22/08/2014 18:44, Andrey Korolyov ha scritto: >> >> I`m running 3.10, so patches are not here, will try 3.16 soon. Even if >> problem will be fixed, it still will be specific for 2.1, earlier >> releases working well and I`ll bisect at a time. > > Thanks, using 3.16 helped indeed. Though the bug remains as is at 2.1 > on LTS 3.10, should I find the breaking commit, or it is better to > backport kvm subsystem changes related to apic to 3.10?
I think I'd suggest the latter. If the fix was brought by those ioapic patches, the bug has always been latent as far as I could see. I'm afraid that bisection would be pretty time consuming, also because the bug didn't reproduce 100% for me (and at some point stopped reproducing even on 3.10, causing some serious wtf...). Paolo
