From: Jarek Poplawski <jarkao2@o2.pl>
To: John M Flinchbaugh <john@hjsoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: inconsistent lock state in 2.6.18.1
Date: Fri, 27 Oct 2006 14:31:11 +0200 [thread overview]
Message-ID: <20061027123111.GA2898@ff.dom.local> (raw)
In-Reply-To: <20061025110024.GA4320@hjsoft.com>
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.
prev parent reply other threads:[~2006-10-27 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 11:00 inconsistent lock state in 2.6.18.1 John M Flinchbaugh
2006-10-27 12:31 ` 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=20061027123111.GA2898@ff.dom.local \
--to=jarkao2@o2.pl \
--cc=john@hjsoft.com \
--cc=linux-kernel@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