From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: kernel-testers@vger.kernel.org
Subject: [X86] Watchdog lockdep warning with next-20080529
Date: Thu, 29 May 2008 23:25:53 +0100 [thread overview]
Message-ID: <g1namq$qk5$1@ger.gmane.org> (raw)
<posted & mailed>
While using linux-next-20080529 the following warning was printed:
[ 1108.103357] ------------[ cut here ]------------
[ 1108.103370] WARNING: at kernel/lockdep.c:2680 check_flags+0x8a/0x12d()
[ 1108.103377] Modules linked in:
[ 1108.103384] Pid: 5, comm: watchdog/0 Not tainted
2.6.26-rc4-next-20080529skw #134
[ 1108.103392] [<c0122f80>] warn_on_slowpath+0x41/0x6a
[ 1108.103402] [<c013cc30>] ? trace_hardirqs_off+0xb/0xd
[ 1108.103411] [<c013ea60>] ? trace_hardirqs_on+0xb/0xd
[ 1108.103419] [<c013ea19>] ? trace_hardirqs_on_caller+0xe8/0x124
[ 1108.103428] [<c013ea60>] ? trace_hardirqs_on+0xb/0xd
[ 1108.103436] [<c011d428>] ? hrtick_set+0xce/0xd6
[ 1108.103445] [<c013c87e>] check_flags+0x8a/0x12d
[ 1108.103452] [<c013f9a0>] lock_acquire+0x3b/0x89
[ 1108.103459] [<c0361ada>] _read_lock+0x1c/0x49
[ 1108.103467] [<c01538b2>] ? watchdog+0x97/0x1a9
[ 1108.103475] [<c015381b>] ? watchdog+0x0/0x1a9
[ 1108.103483] [<c01538b2>] watchdog+0x97/0x1a9
[ 1108.103489] [<c015381b>] ? watchdog+0x0/0x1a9
[ 1108.103497] [<c0133044>] kthread+0x3b/0x63
[ 1108.103504] [<c0133009>] ? kthread+0x0/0x63
[ 1108.103512] [<c01038ab>] kernel_thread_helper+0x7/0x10
[ 1108.103520] =======================
[ 1108.103525] ---[ end trace bf12fd91b8f59e65 ]---
[ 1108.103529] possible reason: unannotated irqs-on.
[ 1108.103534] irq event stamp: 18
[ 1108.103538] hardirqs last enabled at (17): [<c013ea60>]
trace_hardirqs_on+0xb/0xd
[ 1108.103548] hardirqs last disabled at (18): [<c013cc30>]
trace_hardirqs_off+0xb/0xd
[ 1108.103558] softirqs last enabled at (0): [<c01216ab>]
copy_process+0x2dd/0xf9a
[ 1108.103568] softirqs last disabled at (0): [<00000000>] 0x0
--
Sitsofe | http://sucs.org/~sits/
reply other threads:[~2008-05-29 22:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='g1namq$qk5$1@ger.gmane.org' \
--to=sitsofe@yahoo.com \
--cc=kernel-testers@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).