From: "Miles Lane" <miles.lane@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Herbert Xu" <herbert@gondor.apana.org.au>,
"Andrew Morton" <akpm@osdl.org>,
LKML <linux-kernel@vger.kernel.org>,
"Arjan van de Ven" <arjan@infradead.org>
Subject: Re: [patch] lockdep, annotate slocks: turn lockdep off for them
Date: Fri, 30 Jun 2006 17:14:05 -0700 [thread overview]
Message-ID: <a44ae5cd0606301714h5890718and0062354f4870c65@mail.gmail.com> (raw)
In-Reply-To: <a44ae5cd0606301545s33496174lcd7136d8bf41897@mail.gmail.com>
i just hit this again. The stacktrace is identical except for this bit:
other info that might help us debug this:
2 locks held by usplash_write/2182:
#0: (&tty->atomic_write_lock){--..}, at: [<c11fff5e>]
mutex_lock_interruptible+0x1c/0x1f
#1: (&dev->_xmit_lock){-+..}, at: [<c11a5118>] dev_queue_xmit+0x183/0x24b
next prev parent reply other threads:[~2006-07-01 0:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 19:01 2.6.17-mm3 -- BUG: illegal lock usage -- illegal {softirq-on-W} -> {in-softirq-R} usage Miles Lane
2006-06-29 19:26 ` Andrew Morton
2006-06-29 19:42 ` Arjan van de Ven
2006-06-29 19:56 ` Andrew Morton
2006-06-30 2:57 ` Herbert Xu
2006-06-30 6:50 ` Ingo Molnar
2006-06-30 6:59 ` Ingo Molnar
2006-06-30 7:22 ` [patch] lockdep, annotate slocks: turn lockdep off for them Ingo Molnar
2006-06-30 9:18 ` Ingo Molnar
2006-06-30 11:17 ` Herbert Xu
2006-06-30 11:37 ` Ingo Molnar
2006-06-30 11:46 ` Herbert Xu
2006-06-30 20:21 ` Miles Lane
2006-06-30 20:38 ` Ingo Molnar
2006-06-30 22:45 ` Miles Lane
2006-07-01 0:14 ` Miles Lane [this message]
2006-07-01 5:32 ` Ingo Molnar
2006-07-01 9:41 ` Arjan van de Ven
2006-07-01 14:06 ` Miles Lane
2006-07-01 14:07 ` Herbert Xu
2006-07-01 14:10 ` Miles Lane
2006-07-01 14:19 ` Miles Lane
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=a44ae5cd0606301714h5890718and0062354f4870c65@mail.gmail.com \
--to=miles.lane@gmail.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®