Re: inconsistent lock state in 2.6.18.1

[Jarek Poplawski]

On 25-10-2006 13:00, John M Flinchbaugh wrote:
> I see this OOPS on boot with 2.6.18.1/amd64:

You mean this INFO?

> [  113.147347] =================================
> [  113.147561] [ INFO: inconsistent lock state ]
> [  113.147668] ---------------------------------
> [  113.147775] inconsistent {in-hardirq-W} -> {hardirq-on-W} usage.
> [  113.147883] dhclient3/1787 [HC0[0]:SC0[1]:HE1:SE0] takes:
> [  113.147991]  (&ei_local->page_lock){+...}, at: [<ffffffff88080fbb>] ei_start_xmit+0x95/0x24e [8390]
> [  113.148274] {in-hardirq-W} state was registered at:
> [  113.148382]   [<ffffffff802443d5>] lock_acquire+0x7a/0xa1
> [  113.148556]   [<ffffffff80438c09>] _spin_lock+0x2e/0x3c
> [  113.148730]   [<ffffffff880808e0>] ei_interrupt+0x44/0x2fb [8390]

It looks there is a patch for this in 2.6.19-rc (8390.c). 

Jarek P.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/