From: Peter Zijlstra <peterz@infradead.org>
To: Christian Kujau <lists@nerdbynature.de>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
mpe@ellerman.id.au, kda@linux-powerpc.org,
benh@kernel.crashing.org
Subject: Re: DEBUG_LOCKS_WARN_ON(1) / lockdep.c:3134 lockdep_init_map+0x1e8/0x1f0
Date: Wed, 4 Jan 2017 11:12:08 +0100 [thread overview]
Message-ID: <20170104101208.GF25813@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.20.99.1701031806120.31470@trent.utfs.org>
On Tue, Jan 03, 2017 at 06:11:20PM -0800, Christian Kujau wrote:
> Hi,
>
> booting v4.10-rc2 on this PowerPC G4 machine prints the following early
> on, but then continues to boot and the machine is running fine so far:
>
>
> BUG: key ef0ba7d0 not in .data!
> DEBUG_LOCKS_WARN_ON(1)
> ------------[ cut here ]------------
> WARNING: CPU: 0 PID: 1 at
> /usr/local/src/linux-git/kernel/locking/lockdep.c:3134 lockdep_init_map+0x1e8/0x1f0
> Modules linked in:
> CPU: 0 PID: 1 Comm: swapper Not tainted 4.10.0-rc2 #4
> task: ef04aa60 task.stack: ef042000
> NIP: c005eb78 LR: c005eb78 CTR: 00000000
> REGS: ef043d70 TRAP: 0700 Not tainted (4.10.0-rc2)
> MSR: 02029032 <VEC,EE,ME,IR,DR,RI>
> CR: 48000022 XER: 20000000
> GPR00: c005eb78 ef043e20 ef04aa60 00000016 00000001 c0068b24 00000000 00000001
> GPR08: 00000000 00000000 00004ead 000000d6 28000024 00000000 c00047f0 00000000
> GPR16: 00000000 00000000 c08b9280 effedfa0 c078d6ac c1070000 c078eddc c078ee14
> GPR24: c078ed24 c078ee24 00000002 ef085a00 00000000 c08b0000 ef0ba7d0 ef0ba7b4
> NIP [c005eb78] lockdep_init_map+0x1e8/0x1f0
> LR [c005eb78] lockdep_init_map+0x1e8/0x1f0
> Call Trace:
> [ef043e20] [c005eb78] lockdep_init_map+0x1e8/0x1f0 (unreliable)
> [ef043e40] [c083adb4] kw_i2c_add+0xc0/0x134
Commit 9e607f72748d ("i2c_powermac: shut up lockdep warning") it utter
crap and should never have been merged.
/me glares at mpe, why do you merge things that state: 'its unclear
why, just make it go-away' wrt to locking?
prev parent reply other threads:[~2017-01-04 10:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-04 2:11 DEBUG_LOCKS_WARN_ON(1) / lockdep.c:3134 lockdep_init_map+0x1e8/0x1f0 Christian Kujau
2017-01-04 10:12 ` Peter Zijlstra [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=20170104101208.GF25813@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=kda@linux-powerpc.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lists@nerdbynature.de \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.