From: ebiederm@xmission.com (Eric W. Biederman)
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sachin Sant <sachinp@in.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@redhat.com>,
Linux/PPC Development <linuxppc-dev@ozlabs.org>,
Wolfram Sang <w.sang@pengutronix.de>
Subject: Re: 2.6.34-rc3: Badness at kernel/lockdep.c:2706
Date: Fri, 02 Apr 2010 07:59:48 -0700 [thread overview]
Message-ID: <m14ojtrjbv.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <1270218533.5109.525.camel@twins> (Peter Zijlstra's message of "Fri\, 02 Apr 2010 16\:28\:53 +0200")
Could you try the fix Wolfram Sang sent to linux-kernel yesterday?
Peter Zijlstra <peterz@infradead.org> writes:
> On Fri, 2010-04-02 at 11:33 +0530, Sachin Sant wrote:
>> With 2.6.34-rc3 boot on a Power5 box :
>>
>> loop: module loaded
>> BUG: key 6b6b6b6b6b6b6b6b not in .data!
>> ------------[ cut here ]------------
>> Badness at kernel/lockdep.c:2706
>> NIP: c00000000010a0a8 LR: c00000000010a08c CTR: c0000000000704a4
>> REGS: c0000001096d76f0 TRAP: 0700 Not tainted (2.6.34-rc3)
>> MSR: 8000000000029032 <EE,ME,CE,IR,DR> CR: 28000082 XER: 00000009
>> TASK = c0000001fa6f8000[1] 'swapper' THREAD: c0000001096d4000 CPU: 12
>> GPR00: 0000000000000000 c0000001096d7970 c000000001322e38 0000000000000001
>> GPR04: 0000000000000001 c0000000000c1ea8 0000000000000000 0000000000000002
>> GPR08: 0000000000000000 c000000001cc5a00 0000000000002422 c00000000137d768
>> GPR12: 0000000000000002 c00000000f66e400 0000000000d47940 0000000001c00000
>> GPR16: ffffffffffffffff 0000000002673148 00000000018ff984 0000000000000060
>> GPR20: 0000000000000000 ffffffffffffffff 000000000253a291 00000000018ff990
>> GPR24: 00000000018ff988 c000000001229ef0 0000000000000000 c00000010793a730
>> GPR28: 6b6b6b6b6b6b6b6b c00000010793afd8 c000000001299de0 c0000001096d7970
>> NIP [c00000000010a0a8] .lockdep_init_map+0x12c/0x538
>> LR [c00000000010a08c] .lockdep_init_map+0x110/0x538
>> Call Trace:
>> [c0000001096d7970] [c00000000010a074] .lockdep_init_map+0xf8/0x538 (unreliable)
>> [c0000001096d7a30] [c000000000274eac] .sysfs_add_file_mode+0x90/0x124
>> [c0000001096d7af0] [c000000000274f7c] .sysfs_add_file+0x3c/0x50
>> [c0000001096d7b90] [c0000000002750d8] .sysfs_create_file+0x5c/0x74
>> [c0000001096d7c30] [c0000000004b36a0] .device_create_file+0x40/0x5c
>> [c0000001096d7cd0] [c0000000004db384] .wf_register_control+0x108/0x178
>> [c0000001096d7d80] [c000000000a5f7cc] .wf_cpufreq_clamp_init+0x11c/0x16c
>> [c0000001096d7e20] [c00000000000a104] .do_one_initcall+0xb0/0x208
>> [c0000001096d7ed0] [c000000000a12568] .kernel_init+0x230/0x2f0
>> [c0000001096d7f90] [c000000000033b20] .kernel_thread+0x54/0x70
>> Instruction dump:
>> e93e8190 80090000 2f800000 409e03f8 48280539 60000000 2fa30000 419e03e8
>> e93e8198 80090000 2f800000 409e03d8 <0fe00000> 480003d0 e93e8140 fb9d0000
>> Uniform Multi-Platform E-IDE driver
>
> 0x6b is POISON_FREE, so it seems to me sysfs made a boo-boo.
Interesting combination of debugging options there. First time I have
seen BUG: xyz not in .data with a 0x6b address...
Eric
next prev parent reply other threads:[~2010-04-02 15:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 6:03 2.6.34-rc3: Badness at kernel/lockdep.c:2706 Sachin Sant
2010-04-02 14:28 ` Peter Zijlstra
2010-04-02 14:59 ` Eric W. Biederman [this message]
2010-04-03 8:34 ` Sachin Sant
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=m14ojtrjbv.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sachinp@in.ibm.com \
--cc=w.sang@pengutronix.de \
/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