From: Jarek Poplawski <jarkao2@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Valdis.Kletnieks@vt.edu, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Alexander Beregalov <a.beregalov@gmail.com>
Subject: Re: 26-rc9-mmotm lockdep warning initializing loopback interface
Date: Mon, 14 Jul 2008 06:09:33 +0000 [thread overview]
Message-ID: <20080714060933.GA4034@ff.dom.local> (raw)
In-Reply-To: <20080713210755.ed9257aa.akpm@linux-foundation.org>
On 14-07-2008 06:07, Andrew Morton wrote:
> On Sun, 13 Jul 2008 06:00:03 -0400 Valdis.Kletnieks@vt.edu wrote:
...
>> Found this in the dmesg:
>>
>> [ 0.418581] system 00:0b: iomem range 0xfed00000-0xfed003ff has been reserved
>> [ 0.421109]
>> [ 0.421110] =============================================
>> [ 0.421123] [ INFO: possible recursive locking detected ]
>> [ 0.421132] 2.6.26-rc9-mm1 #2
>> [ 0.421138] ---------------------------------------------
>> [ 0.421147] swapper/1 is trying to acquire lock:
>> [ 0.421154] (&queue->lock){-...}, at: [<ffffffff804b81d5>] qdisc_lock_tree+0x27/0x2c
>> [ 0.421176]
>> [ 0.421177] but task is already holding lock:
>> [ 0.421186] (&queue->lock){-...}, at: [<ffffffff804b81cd>] qdisc_lock_tree+0x1f/0x2c
...
> (otoh, many of these problems are also in linux-next. Who's testing
> that? Hopefully it's a weekend*summer thing.)
http://permalink.gmane.org/gmane.linux.kernel.next/1514
Jarek P.
PS: it's only about lockdep annotation, and could be fixed with
other way finally.
prev parent reply other threads:[~2008-07-14 6:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 10:00 26-rc9-mmotm lockdep warning initializing loopback interface Valdis.Kletnieks
2008-07-14 4:07 ` Andrew Morton
2008-07-14 6:09 ` Jarek Poplawski [this message]
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=20080714060933.GA4034@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=a.beregalov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--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).