From: Jon Masters <jonathan@jonmasters.org>
To: Jon Masters <jonathan@jonmasters.org>
Cc: Mike Wellington <wellington@lucent.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: ml300 boot loader question
Date: Wed, 18 Feb 2004 10:52:22 +0000 [thread overview]
Message-ID: <403343E6.7090200@jonmasters.org> (raw)
In-Reply-To: <402F524C.3020009@jonmasters.org>
Hi there,
The breakage is happening inside an mmap call when using dynamically
linked binaries and only when not tracing the process running.
Offset in r8 is broken and I am not sure yet whether this is purely a
hardware corruption of the kernel stack or a subtle kernel bug.
Jon.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-18 10:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 21:49 ml300 boot loader question Lou Rickard
2004-02-13 15:24 ` Peter Ryser
2004-02-14 13:53 ` Jon Masters
2004-02-14 22:43 ` Mike Wellington
2004-02-15 11:04 ` Jon Masters
2004-02-18 10:52 ` Jon Masters [this message]
2004-02-18 12:34 ` Jon Masters
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=403343E6.7090200@jonmasters.org \
--to=jonathan@jonmasters.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wellington@lucent.com \
/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).