From: Matt Porter <mporter@kernel.crashing.org>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: Yu Bo-BOYU1 <Bo.Yu@motorola.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Busybox of Hardhat preview 2.1 for sandpoint 74xx ?
Date: Mon, 5 May 2003 21:11:54 -0700 [thread overview]
Message-ID: <20030505211154.A12082@home.com> (raw)
In-Reply-To: <20030506031544.GA29462@rover.farnsworth.org>; from dale@farnsworth.org on Mon, May 05, 2003 at 08:15:44PM -0700
On Mon, May 05, 2003 at 08:15:44PM -0700, Dale Farnsworth wrote:
>
> On Mon, May 05, 2003 at 08:31:34PM +0000, Yu Bo-BOYU1 wrote:
> >
> > Did anyone know if busybox of hardhat preview 2.1 for sandpoint 74xx work or
> > not ?
> > I got error "Bad trap at PC: 300162fc, SR: f032, vector=f00 Not tainted"
> > no matter
> > the root is mounted on NFS or ramfs.
>
> It's been a while since I last saw it, but this reminds me of what
> happens when running the 74xx userspace on a kernel that doesn't have
> altivec support enabled.
Just to confirm, with the MSR VEC off on a 74xx core, it will definitely
generate that bad trap (UnknownException) on mvista 74xx userspace. I've
seen it on 7xx's that were unintentionally run on the ppc_74xx userspace,
for example.
Regards,
--
Matt Porter
mporter@kernel.crashing.org
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-06 4:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 20:31 Busybox of Hardhat preview 2.1 for sandpoint 74xx ? Yu Bo-BOYU1
2003-05-05 20:38 ` Mark Hatle
2003-05-06 3:15 ` Dale Farnsworth
2003-05-06 4:11 ` Matt Porter [this message]
2003-05-06 12:45 ` Mark Hatle
-- strict thread matches above, loose matches on Subject: below --
2003-05-06 13:51 Yu Bo-BOYU1
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=20030505211154.A12082@home.com \
--to=mporter@kernel.crashing.org \
--cc=Bo.Yu@motorola.com \
--cc=dale@farnsworth.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.