From: Li Zefan <lizf@cn.fujitsu.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>
Subject: [BUG] a WARNING and a BUG from kernel/lockdep.c
Date: Thu, 22 Apr 2010 11:31:39 +0800 [thread overview]
Message-ID: <4BCFC31B.5000706@cn.fujitsu.com> (raw)
Maybe this is caused by commit bd6d29c25bb1a24a4c160ec5de43e0004e01f72b
("lockstat: Make lockstat counting per cpu")
?
============================
------------[ cut here ]------------
WARNING: at kernel/lockdep.c:2301 trace_hardirqs_on_caller+0x210/0x220()
Hardware name: Aspire SA85
Modules linked in: fuse sunrpc ip6t_REJECT nf_conntrack_ipv6 ip6table_filter ip6_tables ipv6 dm_multipath linear ppdev pcspkr parport_pc parport r8169 mii ata_generic pata_acpi sata_sis pata_sis [last unloaded: scsi_wait_scan]
Pid: 2452, comm: java Not tainted 2.6.34-rc5-tip+ #6
Call Trace:
[<c083c276>] ? printk+0x1d/0x1f
[<c044c1e2>] warn_slowpath_common+0x72/0xa0
[<c0482500>] ? trace_hardirqs_on_caller+0x210/0x220
[<c0482500>] ? trace_hardirqs_on_caller+0x210/0x220
[<c042a52c>] ? __bad_area_nosemaphore+0x2c/0x130
[<c044c22a>] warn_slowpath_null+0x1a/0x20
[<c0482500>] trace_hardirqs_on_caller+0x210/0x220
[<c048251b>] trace_hardirqs_on+0xb/0x10
[<c042a52c>] __bad_area_nosemaphore+0x2c/0x130
[<c042a67e>] ? __bad_area+0x2e/0x50
[<c042a68f>] __bad_area+0x3f/0x50
[<c0842bd0>] ? do_page_fault+0x0/0x500
[<c042a6d7>] bad_area_access_error+0x17/0x20
[<c0842df9>] do_page_fault+0x229/0x500
[<c084074f>] ? error_code+0x67/0x70
[<c047e854>] ? trace_hardirqs_off_caller+0x74/0x130
[<c0842bd0>] ? do_page_fault+0x0/0x500
[<c0840753>] error_code+0x6b/0x70
[<c0842bd0>] ? do_page_fault+0x0/0x500
---[ end trace 93d0036abe3ab514 ]---
BUG: using smp_processor_id() in preemptible [00000000] code: java/2452
caller is trace_hardirqs_on_caller+0x18d/0x220
Pid: 2452, comm: java Tainted: G W 2.6.34-rc5-tip+ #6
Call Trace:
[<c083c276>] ? printk+0x1d/0x1f
[<c0627160>] debug_smp_processor_id+0xc0/0xd0
[<c042a52c>] ? __bad_area_nosemaphore+0x2c/0x130
[<c048247d>] trace_hardirqs_on_caller+0x18d/0x220
[<c048251b>] trace_hardirqs_on+0xb/0x10
[<c042a52c>] __bad_area_nosemaphore+0x2c/0x130
[<c042a67e>] ? __bad_area+0x2e/0x50
[<c042a68f>] __bad_area+0x3f/0x50
[<c0842bd0>] ? do_page_fault+0x0/0x500
[<c042a6d7>] bad_area_access_error+0x17/0x20
[<c0842df9>] do_page_fault+0x229/0x500
[<c084074f>] ? error_code+0x67/0x70
[<c047e854>] ? trace_hardirqs_off_caller+0x74/0x130
[<c0842bd0>] ? do_page_fault+0x0/0x500
[<c0840753>] error_code+0x6b/0x70
[<c0842bd0>] ? do_page_fault+0x0/0x500
next reply other threads:[~2010-04-22 3:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-22 3:31 Li Zefan [this message]
2010-04-22 4:29 ` Yong Zhang
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=4BCFC31B.5000706@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=fweisbec@gmail.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
Powered by JetHome