From: Jim Potter <jrp@wvi.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: mm in user space
Date: Mon, 22 Jan 2001 18:05:08 -0800 [thread overview]
Message-ID: <3A6CE6D4.83AD3800@wvi.com> (raw)
I think I'm missing something here...
I'm porting Linux over to an embedded PPC project and I'm getting a DSI
crash when the kernel starts executing elf programs (specifically at
NEW_AUX_ENT in create_elf_tables() in fs/binfmt_elf.c; the stack
accesses are at 0x80000000, and the BATs are only expecting references
at 0xC0000000).
It's been a long day -- what am I missing?
--
Sincerely,
Jim Potter
45th Parallel Processing
jrp@wvi.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2001-01-23 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 2:05 Jim Potter [this message]
2001-01-24 19:19 ` mm in user space Jim Potter
-- strict thread matches above, loose matches on Subject: below --
2001-02-01 22:20 Sébastien Côté
[not found] <3A79EBF9.6534E50D@wvi.com>
2001-02-02 19:39 ` Sébastien Côté
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=3A6CE6D4.83AD3800@wvi.com \
--to=jrp@wvi.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).