Hello: I think this bug is closely related to [0] but I'm not sure.
Bets are, that again in this case, you're facing an unsupported assembler instruction which is not supported by your CPU. The first panic message retrieved from kernel was useful in those days to diagnose the cause of the panic, but unfortunately I've been unable to find that linux-image package version and I couldn't check in the System.map file which function contains the crash. Maybe you can still reproduce it and provide with a fresh panic message and either check yourself which function breaks or providing both the crash info and the running kernel System.map. Anyway, I'd suggest reading my latter comment on [0] and taking conclusions from there. But I have the impression this time again, it's virtualization that's breaking down. I think report should arrive upstream somehow. Regards, [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=488022 -- Raúl Sánchez Siles Departamento de Montaje INFOGLOBAL, S. A. * C/ Virgilio, 2. Ciudad de la Imagen. 28223 Pozuelo de Alarcón (Madrid), España * T: +34 91 506 40 00 * F: +34 91 506 40 01 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
