From: Valdis.Kletnieks@vt.edu
To: Tejun Heo <tj@kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: odd lockdep messages
Date: Tue, 09 Mar 2010 01:27:19 -0500 [thread overview]
Message-ID: <4298.1268116039@localhost> (raw)
In-Reply-To: Your message of "Tue, 09 Mar 2010 10:54:20 +0900." <4B95AA4C.2030303@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
On Tue, 09 Mar 2010 10:54:20 +0900, Tejun Heo said:
> On 03/09/2010 03:43 AM, Peter Zijlstra wrote:
> >> [ 1.899537] BUG: key ffff88011c57e670 not in .data!
> >>
> >> (-0302 threw BUG: 3 times, the first 2 and the last. In -0304, the third
> >> one appears as well).
> >>
> >> Worth instrumenting and chasing down? If so, what should a crash test dummy
> >> be doing here? ;)
> >
> > Can that be wreckage due to the new per-cpu stuff?
> >
> > Its a message printed when the below function fails, and that per-cpu
> > stuff seems the one most likely to break, given that there was quite a
> > lot of churn in that department recently.
>
> Yeap, PERCPU_ENOUGH_ROOM test doesn't hold anymore. Does the
> following patch fix the problem?
Doesn't seem to make a difference, sorry.
For what it's worth, adding the iwlwifi-5000-2.ucode to the builtin firmware
list fixed the two BUG: messages related to the firmware load. Not sure if
that tells you anything or not.
However, I still have left:
[ 0.997904] Monitor-Mwait will be used to enter C-1 state
[ 0.998045] Monitor-Mwait will be used to enter C-2 state
[ 0.998184] Monitor-Mwait will be used to enter C-3 state
[ 0.998300] Marking TSC unstable due to TSC halts in idle
[ 0.998476] Switching to clocksource hpet
[ 1.030681] BUG: key ffff88011c8c1d00 not in .data!
[ 1.030787] BUG: key ffff88011c8c1d48 not in .data!
[ 1.035288] thermal LNXTHERM:01: registered as thermal_zone0
[ 1.035405] ACPI: Thermal Zone [THM] (54 C)
[ 1.041622] Real Time Clock Driver v1.12b
[ 1.041955] Linux agpgart interface v0.103
[ 1.042266] Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
I'll stick a 'WAR_ON(1)' next to that BUG printk so we get an idea where it's
happening, probably be morning before that happens though...
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2010-03-09 6:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-08 18:30 odd lockdep messages Valdis.Kletnieks
2010-03-08 18:43 ` Peter Zijlstra
2010-03-08 20:00 ` Valdis.Kletnieks
2010-03-09 1:54 ` Tejun Heo
2010-03-09 6:27 ` Valdis.Kletnieks [this message]
2010-03-09 6:44 ` Tejun Heo
2010-03-09 8:51 ` Valdis.Kletnieks
2010-03-09 14:18 ` Greg KH
2010-03-09 9:12 ` [PATCH] percpu,lockdep: implement and use is_static_percpu_address() Tejun Heo
2010-03-09 11:25 ` Peter Zijlstra
2010-03-09 11:42 ` Tejun Heo
2010-03-09 11:46 ` Tejun Heo
2010-03-09 11:52 ` Peter Zijlstra
2010-03-10 9:56 ` [PATCH 1/2] module: encapsulate percpu handling better and record percpu_size Tejun Heo
2010-03-10 9:57 ` [PATCH 2/2] percpu,module: implement and use is_kernel/module_percpu_address() Tejun Heo
2010-03-10 10:42 ` Peter Zijlstra
2010-03-29 8:26 ` [PATCH 1/2] module: encapsulate percpu handling better and record percpu_size Rusty Russell
2010-03-29 14:12 ` Tejun Heo
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=4298.1268116039@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tj@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).