Re: [debug patch] printk: Add a printk killswitch to robustify NMIwatchdog messages

[Arne Jansen]

On 05.06.2011 18:07, Arne Jansen wrote:
> On 05.06.2011 17:32, Ingo Molnar wrote:
> > one more thing, could you please add this call:
> >
> > debug_show_all_locks();
> >
> > to after the WARN(), in watchdog.c?
> >
> > Please surround the whole printout portion by the
> > spin_lock()/unlock() protection code i suggested, full-lock-state
> > printouts are slow and other CPUs might start printing their NMI
> > ticks ...
> >
> > With the all-locks-printed output we can double check what locks are
> > held.
>
> Hm, on first try:
>
> INFO: lockdep is turned off.
>
> Recompiling...

same after a full recompile.

# grep LOCKDEP .config

CONFIG_LOCKDEP_SUPPORT=y
CONFIG_LOCKDEP=y
# CONFIG_DEBUG_LOCKDEP is not set


-Arne

> > Thanks,
> >
> > Ingo
> > --
> > To unsubscribe from this list: send the line "unsubscribe
> > linux-kernel" in
> > the body of a message to majordomo@xxxxxxxxxxxxxxx
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/