Messages in this thread | | | Subject | Re: locking api self-test hanging | From | Peter Zijlstra <> | Date | Mon, 04 Feb 2008 14:14:52 +0100 |
| |
On Mon, 2008-02-04 at 05:04 -0800, Andrew Morton wrote:
> After disabling both CONFIG_DEBUG_LOCKING_API_SELFTESTS and netconsole > (using current mainline) I get a login prompt, and also...
> [ 7.819146] WARNING: at kernel/lockdep.c:2033 trace_hardirqs_on+0x9b/0x10d()
> That warning in lockdep.c should have a comment explaining to readers under > which circumstances it will trigger, and what they did wrong. In fact if > I've interpreted it correctly I don't see why it's a DEBUG_LOCKS_WARN_ON > thing at all? It should be a first-class lockdep warning?
Agreed, I'll make lockdep print a nice error.
| |