From: Mark Hatle <fray@mvista.com>
To: Pawel Zawora <pzawora@fideltronik.com>
Cc: linuxppc <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: illegal intruction
Date: Fri, 22 Sep 2000 10:45:28 -0700 [thread overview]
Message-ID: <39CB9AB8.27CBD412@mvista.com> (raw)
In-Reply-To: 39CB0FDD.2E5C8DF7@fideltronik.com
We need a lot more information to understand what the problem might be.
I see it's Linux PPC, kernel version 2.2.13... but what CPU, what board,
how much ram, etc.
>From not knowing anything about this, it sounds like you are trying to
run software that is using floating point on a system that doesn't
have an FPU. But that is just a guess.
--Mark
Pawel Zawora wrote:
>
> I'm working with Linux PPC, kernel version 2.2.13 with nfs as a root
> file system. When I try to run any software sometimes a exeption
> undefined instruction code 0xffffffda occurs (kernel try it emulate),
> sometimes everything works.
> Does anybody know what can be a reason of behavior like this?
> It isn't a problem of limited RAM memory space.
> What is the best way to find this error?
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-09-22 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-22 7:53 illegal intruction Pawel Zawora
2000-09-22 17:45 ` Mark Hatle [this message]
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=39CB9AB8.27CBD412@mvista.com \
--to=fray@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=pzawora@fideltronik.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 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.