[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4298.1268116039@localhost>
Date: Tue, 09 Mar 2010 01:27:19 -0500
From: Valdis.Kletnieks@...edu
To: Tejun Heo <tj@...nel.org>
Cc: Peter Zijlstra <peterz@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: odd lockdep messages
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...
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists