Andrew Morton wrote: > I said that because the damn thing went away when I was hunting it down > because I lost the config and was unable to remember the right combination > of debug settings. Fortunately it later came back so I took care to > preserve the config. >
sched_clock doesn't *do* anything except flap interrupts. Oh, wait, have you got Andi's bugfixed version of the sched_clock patch? The first version did a local_save_flags rather than a local_irq_save. >> Hm, is it caused by using sched_clock() to generate the printk >> timestamps while generating the lock test output? >> > > Conceivably. What does that locking API test do? > Didn't make a difference here. Building your config now. > I was using printk timestamps and netconsole at the time. > Ah, great, now you're going to make me setup netconsole... J - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/