> Today I encountered a "BUG: scheduling while atomic" from kvm.ko when > resuming the host from suspend-to-RAM. I captured as much of the oops as > was displayed on screen: > > http://vmsplice.net/~stefan/panic1.jpg > http://vmsplice.net/~stefan/panic2.jpg > > It looks like the iwlagn driver may have crashed in an interrupt handler and > the > kvm-related panic was triggered in the aftermath. Any ideas?
This doesn't look like iwlagn is involved at all -- the fact that it comes up in the backtrace seems to be an artifact of backtracing not being perfect. The RIP points to kvm_arch_vcpu_ioctl_run+0x927 and there's no reason to believe that iwlagn should crash kvm. johannes -------------------------------------------------------------------------------------- Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/Muenchen, Deutschland Sitz der Gesellschaft: Feldkirchen bei Muenchen Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer Registergericht: Muenchen HRB 47456 Ust.-IdNr./VAT Registration No.: DE129385895 Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052 -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
