From: "Lee Rhodes" <daddy_rhodes@hotmail.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: kernel thread and NULL active_mm (MPC860)
Date: Fri, 14 May 2004 16:20:00 +0100 [thread overview]
Message-ID: <BAY19-F12mLng8FSZDh0000bc92@hotmail.com> (raw)
Hi,
Can anyone tell me what would cause my kernel thread to have a NULL
active_mm? The thread is waking up from a down_interruptible (it's a DPC
thread) and, in doing so, it triggers the BUG_ON on line 559 of sched.c.
I'm just wondering if anyone can provide me with some theories on what might
be going wrong. The same could runs fine on an i386 Linux desktop machine.
I'm only encountering this issue when I port it to MPC860.
Thanks for any tips,
Lee
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-05-14 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-14 15:20 Lee Rhodes [this message]
2004-05-14 21:33 ` kernel thread and NULL active_mm (MPC860) Dan Malek
-- strict thread matches above, loose matches on Subject: below --
2004-05-17 14:18 Lee Rhodes
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=BAY19-F12mLng8FSZDh0000bc92@hotmail.com \
--to=daddy_rhodes@hotmail.com \
--cc=linuxppc-embedded@lists.linuxppc.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).