On Fri, Oct 16, 2015 at 7:05 AM, Borislav Petkov <b...@alien8.de> wrote: > > On Fri, Oct 16, 2015 at 12:52:29PM +0200, Borislav Petkov wrote: > > > > Just triggered this here on rc5+tip/master, 32-bit. Any ideas? > > > > > > > > ------------[ cut here ]------------ > > > > WARNING: CPU: 1 PID: 1 at > > > > /mnt/kernel/kernel/linux-2.6/kernel/locking/lockdep.c:2639 > > > > trace_hardirqs_off_caller+0xef/0x150() > > > > DEBUG_LOCKS_WARN_ON(!irqs_disabled()) > > > > Modules linked in: > > Hmm, something more is b0rked with this. I'm attaching a #GP splat from > the intel laptop. Yeah, the box has paniced and the only way to catch it > is a photo (how convenient that cameras are ubiquitous nowadays...). > > I see prepare_exit_to_usermode and do_signal ... > > Fun stuff :-\
Is this AMD or Intel? If it's Intel, can you see if booting with nosep fixes it? --Andy -- 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/
