On Thu, Jul 25, 2013 at 6:32 PM, Ilia Mirkin <imir...@alum.mit.edu> wrote: > Hi, > > I just built a 3.11-rc2 kernel (+ a few patches, but nothing > arch-related), and I saw the following: http://i.imgur.com/dCTqOyR.jpg > > The rough transcription is > > Call Trace: > <IRQ> > generic_smp_call_fucntion_single_interrupt > smp_call_function_single_interrupt > call_function_single_interrupt > <EOI> > ? default_idle > ? default_idle > arch_cpu_idle > cpu_startup_entry > rest_init > start_kernel > ? repair_env_string > x86_64_start_reservations > x86_64_start_kernel > Code: ... cc 81 8b 0f <0f> 32 48 c1 e2 20 89 c0 ... > RIP: __rdmsr_on_cpu+0x2e/0x44 > Kernel panic - not syncing: Fatal exception in interrupt > > A 3.10-rc7 kernel booted just fine. Is this likely a real issue? Or > perhaps a mis-build of some sort?
FWIW this is repeatable. I did a clean build (make clean && make) and I still see the same thing. I have a Core i7-920 cpu, not sure what other information would be relevant. I'd love to avoid a bisect, so some likely candidates would be most welcome. Thanks, -ilia -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
