From: Larry Finger <Larry.Finger@lwfinger.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.34-rc3
Date: Tue, 30 Mar 2010 14:17:51 -0500 [thread overview]
Message-ID: <4BB24E5F.3030703@lwfinger.net> (raw)
Remember our old friend? See also
http://lkml.indiana.edu/hypermail/linux/kernel/1003.1/02769.html and a long
related discussion at
http://lkml.indiana.edu/hypermail/linux/kernel/1003.1/02772.html.
BUG: key ffff8800374d2660 not in .data!
------------[ cut here ]------------
WARNING: at kernel/lockdep.c:2706 lockdep_init_map+0x236/0x5d0()
Hardware name: HP Pavilion dv2700 Notebook PC
Modules linked in: processor(+) ide_pci_generic amd74xx ide_core thermal
Pid: 612, comm: modprobe Not tainted 2.6.34-rc3-Linus #192
Call Trace:
[<ffffffff81046168>] warn_slowpath_common+0x78/0xb0
[<ffffffff810461af>] warn_slowpath_null+0xf/0x20
[<ffffffff810772c6>] lockdep_init_map+0x236/0x5d0
[<ffffffff811649aa>] sysfs_add_file_mode+0x6a/0xc0
[<ffffffff811acaa0>] ? sprintf+0x40/0x50
[<ffffffff81164a0c>] sysfs_add_file+0xc/0x10
[<ffffffff81164ae1>] sysfs_create_file+0x21/0x30
[<ffffffff81247cc4>] device_create_file+0x14/0x20
[<ffffffff8126d7d4>] thermal_zone_bind_cooling_device+0x1c4/0x310
-- dump truncated here --
I understand that you do not want a whole set of such "fix one such bug at a
time" patches, but the bottom line is that these lockdep warnings for known
problems interfere with "normal" debugging because further lockdep checking is
disabled. I do not feel qualified to detect other cases and fix them. Only when
a warning hits my logs am I qualified to fix and test.
Larry
next reply other threads:[~2010-03-30 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 19:17 Larry Finger [this message]
2010-03-31 2:16 ` Linux 2.6.34-rc3 Wolfram Sang
2010-03-31 2:40 ` Larry Finger
2010-04-04 3:39 ` Linus Torvalds
2010-04-04 3:54 ` Wolfram Sang
2010-04-04 4:06 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2010-03-30 17:50 Linus Torvalds
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=4BB24E5F.3030703@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.