From: John Kacur <jkacur@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>, RT <linux-rt-users@vger.kernel.org>
Subject: [BUG-REPORT][PREEMPT-RT] 2.6.33.1-rt11 triggers DEBUG_LOCKS_WARN_ON(!p->hardirqs_enabled), in a 32-bit kvm session
Date: Fri, 26 Mar 2010 13:02:22 +0100 [thread overview]
Message-ID: <520f0cf11003260502o5ecb23adpe69f6eb465142821@mail.gmail.com> (raw)
During boot-up of 2.6.33.1-rt11 in a 32-bit qemu-kvm machine,
The following warning is reliably (every time) triggered.
------------[ cut here ]------------
WARNING: at /home/jkacur/jk-2.6/kernel/fork.c:1065 copy_process+0x299/0x160f()
Hardware name:
Modules linked in:
Pid: 64, comm: khelper Not tainted 2.6.33.1-rt11 #1
Call Trace:
[<c104961a>] warn_slowpath_common+0x83/0x9a
[<c1049643>] warn_slowpath_null+0x12/0x15
[<c1046f89>] copy_process+0x299/0x160f
[<c1048711>] do_fork+0x235/0x4e2
[<c107da08>] ? register_lock_class+0x17/0x22d
[<c107e6dc>] ? mark_lock+0x1e/0x1c0
[<c1064a2f>] ? ____call_usermodehelper+0x0/0x138
[<c100ae09>] kernel_thread+0x79/0x81
[<c1064a2f>] ? ____call_usermodehelper+0x0/0x138
[<c100391c>] ? kernel_thread_helper+0x0/0x10
[<c1064cc7>] __call_usermodehelper+0x75/0xa0
[<c10673b6>] worker_thread+0x1f6/0x2fb
[<c1067374>] ? worker_thread+0x1b4/0x2fb
[<c1064c52>] ? __call_usermodehelper+0x0/0xa0
[<c106a91e>] ? autoremove_wake_function+0x0/0x46
[<c106a740>] kthread+0x6b/0x74
[<c10671c0>] ? worker_thread+0x0/0x2fb
[<c106a6d5>] ? kthread+0x0/0x74
[<c106a6d5>] ? kthread+0x0/0x74
[<c1003922>] kernel_thread_helper+0x6/0x10
---[ end trace a22d306b065d4a66 ]---
I am happy to provide more information to help debug this.
Thanks
next reply other threads:[~2010-03-26 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 12:02 John Kacur [this message]
2010-03-26 19:01 ` [BUG-REPORT][PREEMPT-RT] 2.6.33.1-rt11 triggers DEBUG_LOCKS_WARN_ON(!p->hardirqs_enabled), in a 32-bit kvm session Thomas Gleixner
2010-03-27 22:56 ` John Kacur
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=520f0cf11003260502o5ecb23adpe69f6eb465142821@mail.gmail.com \
--to=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).