From: Sebastien Dugue <sebastien.dugue@bull•net>
To: Nathan Lynch <ntl@pobox•com>
Cc: linuxppc-dev@ozlabs•org, Arnd Bergmann <arnd@arndb•de>
Subject: Re: lockdep badness
Date: Fri, 25 Jul 2008 14:59:13 +0200 [thread overview]
Message-ID: <20080725145913.64904640@bull.net> (raw)
In-Reply-To: <20080724192300.GE9594@localdomain>
Hi,
On Thu, 24 Jul 2008 14:23:00 -0500 Nathan Lynch <ntl@pobox•com> wrote:
> I'm seeing warnings from the lockdep code itself in recent kernels on
> a Power6 blade (v2.6.26 and benh's -next branch).
>
> Something to do with powerpc's "lazy" interrupt-disabling, perhaps?
>
> A couple of stack traces below, the first is from benh's tree, the
> second is from 2.6.26. The lockdep self-tests all pass at boot.
>
> RTAS daemon started
> RTAS: event: 295, Type: Dump Notification Event, Severity: 2
> ------------[ cut here ]------------
> Badness at kernel/lockdep.c:2719
<snip>
I'm observing nearly the same thing (minus the ipr related badness) here with
Ben's powerpc.git (master) on a JS22 blade:
Freeing initrd memory: 2676k freed
RTAS daemon started
RTAS: event: 94, Type: Platform Information Event, Severity: 1
------------[ cut here ]------------
Badness at kernel/lockdep.c:2079
NIP: c0000000000846dc LR: c0000000000846c0 CTR: 0000000000000000
REGS: c0000001e353f9c0 TRAP: 0700 Not tainted (2.6.26)
MSR: 8000000000029032 <EE,ME,IR,DR> CR: 24000042 XER: 20000010
TASK = c0000000efa58640[115] 'rtasd' THREAD: c0000001e353c000 CPU: 3
GPR00: 0000000000000000 c0000001e353fc40 c0000000004efe50 0000000000000001
GPR04: 0000000000000001 c00000000003cc94 0000000000000001 636820202d203230
GPR08: 3465303000000000 c0000000009627a8 c0000000efa58e88 0000000000000001
GPR12: 3465303038200d0a c000000000525900 c000000000395ba0 4000000000c00000
GPR16: c0000000003943c8 0000000000000000 000000000029d000 000000000101c920
GPR20: 0000000000000000 0000000000000001 0000000000000744 0000000000000001
GPR24: c000000000538cf0 c0000001e3e74000 c00000000041b48c c0000000004c0060
GPR28: c0000000000847a4 c0000000efa58640 c0000000004b18d0 c0000001e353fc40
NIP [c0000000000846dc] .trace_hardirqs_on_caller+0xc4/0x170
LR [c0000000000846c0] .trace_hardirqs_on_caller+0xa8/0x170
Call Trace:
[c0000001e353fcd0] [c0000000000847a4] .trace_hardirqs_on+0x1c/0x30
[c0000001e353fd50] [c0000000002df554] ._spin_unlock_irqrestore+0x68/0xb8
[c0000001e353fde0] [c00000000003cc94] .pSeries_log_error+0x3a4/0x400
[c0000001e353fef0] [c00000000003cf28] .rtasd+0x98/0x100
[c0000001e353ff90] [c0000000000295f8] .kernel_thread+0x4c/0x68
Instruction dump:
901d07ec 880d01ca 2fa00000 41be002c 481300a1 60000000 2fa30000 419e00a0
e93e80f8 80090000 2f800000 409e0090 <0fe00000> 48000088 e92d01a0 8009082c
Installing knfsd (copyright (C) 1996 okir@monad•swb.de).
msgmni has been set to 15071
Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254)
...
Sebastien.
prev parent reply other threads:[~2008-07-25 12:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 19:23 lockdep badness Nathan Lynch
2008-07-24 19:38 ` Nathan Lynch
2008-07-24 22:47 ` Benjamin Herrenschmidt
2008-07-24 22:44 ` Benjamin Herrenschmidt
2008-07-24 23:00 ` Nathan Lynch
2008-07-24 23:04 ` Arnd Bergmann
2008-07-25 12:59 ` Sebastien Dugue [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=20080725145913.64904640@bull.net \
--to=sebastien.dugue@bull$(echo .)net \
--cc=arnd@arndb$(echo .)de \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=ntl@pobox$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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