From: Vitaly Bordug <vitb@kernel.crashing.org>
To: John Charles Tyner <jtyner@cs.ucr.edu>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: oops trying to execute sh
Date: Fri, 23 Nov 2007 01:06:01 +0300 [thread overview]
Message-ID: <20071123010601.415b5761@kernel.crashing.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0711211149210.3338@eon.cs.ucr.edu>
On Wed, 21 Nov 2007 11:54:01 -0800 (PST)
John Charles Tyner wrote:
> I'm trying to boot linux 2.6.22.9 on an mpc860c rev d4.
>
ppc or powerpc?
> When init trys to spawn sh, during the exec, the kernel oopses as
> seen below:
This looks like coherency problem, or kernel picks wrong entry off cputable.
I think I recall something similar when I lost a hunk applying patch for new e300 core.
... or not. The game across that ff8.. value is very confusing.
>
--
Sincerely, Vitaly
next prev parent reply other threads:[~2007-11-22 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 19:54 oops trying to execute sh John Charles Tyner
2007-11-22 22:06 ` Vitaly Bordug [this message]
2007-11-24 14:26 ` John Tyner
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=20071123010601.415b5761@kernel.crashing.org \
--to=vitb@kernel.crashing.org \
--cc=jtyner@cs.ucr.edu \
--cc=linuxppc-dev@ozlabs.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).