Messages in this thread | | | Date | Mon, 14 Jul 2008 06:09:33 +0000 | From | Jarek Poplawski <> | Subject | Re: 26-rc9-mmotm lockdep warning initializing loopback interface |
| |
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.
| |