From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@elte.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: [BUG] lockdep_init_map error in sysfs
Date: Wed, 24 Mar 2010 13:43:12 -0400 [thread overview]
Message-ID: <1269452592.2957.2852.camel@gandalf.stny.rr.com> (raw)
I'm getting this in latest Linus tree:
BUG: key ffff88002ede4870 not in .data!
------------[ cut here ]------------
WARNING: at kernel/lockdep.c:2706 lockdep_init_map+0xe6/0x576()
Hardware name: Precision WorkStation 470
Modules linked in: radeon ttm drm_kms_helper drm i2c_algo_bit autofs4 hidp rfcomm l2cap crc16 bluetooth ip6t_REJECT xt_tcpudp ip6table_filter ip6_tables x_tables ipv6 sbs sbshc battery ac snd_intel8x0 snd_ac97_codec ac97_bus snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss sg snd_mixer_oss e1000 snd_pcm snd_timer button snd floppy serio_raw e752x_edac i2c_i801 ata_generic iTCO_wdt iTCO_vendor_support i2c_core shpchp edac_core pcspkr soundcore snd_page_alloc dm_snapshot dm_zero dm_mirror dm_region_hash dm_log dm_mod ata_piix libata sd_mod scsi_mod ext3 jbd ehci_hcd ohci_hcd uhci_hcd
Pid: 3335, comm: Xorg Not tainted 2.6.34-rc1 #2533
Call Trace:
[<ffffffff81056a88>] warn_slowpath_common+0x7c/0x94
[<ffffffff81056ab4>] warn_slowpath_null+0x14/0x16
[<ffffffff81087536>] lockdep_init_map+0xe6/0x576
[<ffffffff811830d1>] ? sysfs_new_dirent+0x8f/0x104
[<ffffffff811824fe>] sysfs_add_file_mode+0x66/0xae
[<ffffffff81182557>] sysfs_add_file+0x11/0x13
[<ffffffff81184a0b>] sysfs_create_bin_file+0x5f/0x68
[<ffffffff812a5fb3>] _request_firmware+0x613/0x623
[<ffffffff812a603e>] request_firmware+0x13/0x15
[<ffffffffa04a9c03>] radeon_cp_init+0xd0a/0xf07 [radeon]
[<ffffffff813d1e27>] ? _lock_kernel+0x10e/0x1b3
[<ffffffffa0473608>] drm_ioctl+0x290/0x364 [drm]
[<ffffffffa04a8ef9>] ? radeon_cp_init+0x0/0xf07 [radeon]
[<ffffffff81130537>] vfs_ioctl+0x32/0xa6
[<ffffffff81130af6>] do_vfs_ioctl+0x4c2/0x508
[<ffffffff8112252d>] ? fget_light+0x53/0x17e
[<ffffffff8107fb15>] ? current_kernel_time+0x2d/0x55
[<ffffffff8100c4ea>] ? sysret_check+0x2e/0x69
[<ffffffff81130b98>] sys_ioctl+0x5c/0x9a
[<ffffffff8100c4b2>] system_call_fastpath+0x16/0x1b
---[ end trace f0b271065a87e572 ]---
-- Steve
next reply other threads:[~2010-03-24 17:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-24 17:43 Steven Rostedt [this message]
2010-03-24 17:45 ` Steven Rostedt
2010-03-24 18:02 ` Steven Rostedt
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=1269452592.2957.2852.camel@gandalf.stny.rr.com \
--to=rostedt@goodmis.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®