From: Ben Greear <greearb@candelatech.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: lockdep: Invalid subclass: 31, related to mousedev_create
Date: Tue, 26 Oct 2010 14:48:15 -0700 [thread overview]
Message-ID: <4CC74C9F.6040801@candelatech.com> (raw)
This is coming out of today's wireless-testing tree:
BUG: looking up invalid subclass: 31
turning off the locking correctness validator.
Pid: 1, comm: swapper Not tainted 2.6.36-wl+ #33
Call Trace:
[<c076af55>] ? printk+0xf/0x12
[<c045535f>] look_up_lock_class+0x2d/0x9e
[<c0455bb7>] register_lock_class+0x17/0x2ac
[<c0455ed2>] ? lockdep_init_map+0x86/0xf1
[<c0454fbe>] ? debug_mutex_init+0x28/0x33
[<c0455f2c>] lockdep_init_map+0xe0/0xf1
[<c0686d0d>] mousedev_create+0x8d/0x196
[<c09b4215>] mousedev_init+0x15/0x51
[<c040115e>] do_one_initcall+0x71/0x121
[<c09b4200>] ? mousedev_init+0x0/0x51
[<c098838c>] kernel_init+0x126/0x1a7
[<c0988266>] ? kernel_init+0x0/0x1a7
[<c0403586>] kernel_thread_helper+0x6/0x1a
mice: PS/2 mouse device common for all mice
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next reply other threads:[~2010-10-26 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 21:48 Ben Greear [this message]
2010-10-26 22:00 ` lockdep: Invalid subclass: 31, related to mousedev_create Randy Dunlap
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=4CC74C9F.6040801@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.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