On Tue, 2009-11-03 at 11:02 -0500, Steven Rostedt wrote: > [ Added Peter Zijlstra ] > > On Tue, 2009-11-03 at 10:48 -0500, Eric Paris wrote: > > Linux-next from Oct 30 did not have this problem. Linux next from > > yesterday (and today) I always hit this on boot. > > Could you also give the SHA1 of Linux-next, as well as the config you > used. cb9267934a27b149416762308a36e8a61f04ecb2 > > > > [ 7.989630] BUG: unable to handle kernel paging request at 00000000000160de > > [ 7.990538] IP: [<ffffffff8123cdbf>] strcmp+0xf/0x30 > > [ 7.990538] PGD 77f7e067 PUD 77ff1067 PMD 0 > > [ 7.990538] Oops: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC > > [ 7.990538] last sysfs file: /sys/devices/platform/i8042/serio0/input/input2/event2/uevent > > [ 7.990538] CPU 0 > > [ 7.990538] Modules linked in: ata_piix(+) > > [ 7.990538] Pid: 1024, comm: modprobe Not tainted 2.6.32-rc5-fanotify-next-20091102 #150 > > Just curious, what module were you loading? Looking at strace of the modprobe command it shows at the bottom I believe it was ata_generic. But I don't really know. > Hmm, event_mutex is defined with > > DEFINE_MUTEX(event_mutex); > > in trace_events.c (well, in my kernel, I'm not looking at linux-next > right now). This should set up lockdep without any issues. It's a DEFINE_MUTEX in linux-next as well. > Would be better to get more info (as asked above). You can send > the .config privately to me, as not to spam LKML with it. Incoming along will full dmesg. -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
