From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Stephen Hemminger <shemminger@linux-foundation.org>,
Bernhard Walle <bwalle@suse.de>
Subject: Re: locking api self-test hanging
Date: Mon, 04 Feb 2008 14:14:52 +0100 [thread overview]
Message-ID: <1202130892.32654.81.camel@lappy> (raw)
In-Reply-To: <20080204050421.0febc754.akpm@linux-foundation.org>
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.
next prev parent reply other threads:[~2008-02-04 13:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 23:02 locking api self-test hanging Andrew Morton
2008-02-03 23:07 ` Andrew Morton
2008-02-04 12:43 ` Andrew Morton
2008-02-04 13:04 ` Andrew Morton
2008-02-04 13:14 ` Peter Zijlstra [this message]
2008-02-05 13:23 ` Bernhard Walle
2008-02-04 13:18 ` Andrew Morton
2008-02-06 8:34 ` Andrew Morton
2008-02-06 9:16 ` Andrew Morton
2008-03-04 5:05 ` Andrew Morton
2008-03-04 8:06 ` [patch] mark netconsole broken Ingo Molnar
2008-03-04 16:19 ` Randy Dunlap
2008-03-04 20:30 ` David Miller
2008-03-04 20:52 ` Ingo Molnar
2008-03-04 8:40 ` locking api self-test hanging Jarek Poplawski
2008-03-04 9:10 ` Andrew Morton
2008-03-04 15:51 ` Stephen Hemminger
2008-03-04 20:30 ` David Miller
2008-03-05 8:23 ` Andrew Morton
2008-03-05 8:27 ` David Miller
2008-03-04 19:04 ` Marcin Slusarz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1202130892.32654.81.camel@lappy \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bwalle@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.