From: Peter Zijlstra <peterz@infradead.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.23-rc5: possible irq lock inversion dependency detected
Date: Mon, 10 Sep 2007 14:03:33 +0200 [thread overview]
Message-ID: <1189425813.21778.13.camel@twins> (raw)
In-Reply-To: <alpine.DEB.0.999.0709021455510.7103@sheep.housecafe.de>
On Sun, 2007-09-02 at 15:11 +0200, Christian Kujau wrote:
> Hi,
>
> after upgrading to 2.6.23-rc5 (and applying davem's fix [0]), lockdep
> was quite noisy when I tried to shape my external (wireless) interface:
>
> [ 6400.534545] FahCore_78.exe/3552 just changed the state of lock:
> [ 6400.534713] (&dev->ingress_lock){-+..}, at: [<c038d595>] netif_receive_skb+0x2d5/0x3c0
> [ 6400.534941] but this lock took another, soft-read-irq-unsafe lock in the past:
> [ 6400.535145] (police_lock){-.--}
>
> This happened when I executed: http://nerdbynature.de/bits/2.6.23-rc5/qos.sh.txt
> (using iproute2-ss070313). The is still running, I just noticed a short
> hickup, probably when it was busy writing the warning to the disk.
>
> More details and .config: http://nerdbynature.de/bits/2.6.23-rc5/
seems unavailable at this time, please submit the whole lockdep report
if possible.
next prev parent reply other threads:[~2007-09-10 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-02 13:11 2.6.23-rc5: possible irq lock inversion dependency detected Christian Kujau
2007-09-10 12:03 ` Peter Zijlstra [this message]
2007-09-10 13:00 ` Herbert Xu
2007-09-11 0:04 ` jamal
2007-09-11 2:18 ` Herbert Xu
2007-09-11 12:01 ` jamal
2007-09-11 12:43 ` Herbert Xu
2007-09-12 14:33 ` David Miller
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=1189425813.21778.13.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=netdev@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).