On Wed, 2011-06-01 at 19:20 +0200, Arne Jansen wrote: > On 01.06.2011 18:35, Peter Zijlstra wrote: > > On Wed, 2011-06-01 at 15:58 +0200, Arne Jansen wrote: > >> git bisect blames this commit for a problem I have with v3.0-rc1: > >> If I printk large amounts of data, the machine locks up. > >> As the commit does not revert cleanly on top of 3.0, I haven't been > >> able to double check. > >> The test I use is simple, just add something like > >> > >> for (i=0; i< 10000; ++i) printk("test %d\n", i); > >> > >> and trigger it, in most cases I can see the first 10 printks before > >> I have to power cycle the machine (sysrq-b does not work anymore). > >> Attached my .config. > > > > I've made me a module that does the above, I've also changed my .config > > to match yours (smp=y, sched-cgroup=y, autogroup=n, preempt=n, no_hz=y), > > but sadly I cannot reproduce, I get all 10k prints on my serial line. > > > > Even without serial line it works (somehow booting without visible > > console is scary as hell :) > > > > Which makes me ask, how are you observing your console? > > > > They don't go out to the serial line, I only observe them with a > tail -f on messages. Default log level doesn't go the console here. Right ok, so I used your exact .config, added a few drivers needed for my hardware and indeed, it doesn't even finish booting and gets stuck someplace. Sadly it looks like even the NMI watchdog is dead,.. /me goes try and make sense of this. -- To unsubscribe from this list: send the line "unsubscribe linux-tip-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html