linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "wilbur.chan" <wilbur512@gmail.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	"chen.yu10" <chen.yu10@zte.com.cn>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: kernel init exception
Date: Thu, 1 Jul 2010 08:10:39 +0800	[thread overview]
Message-ID: <AANLkTilNpYjhM5NRevXBcsAb-MFw55A8iSrDcRvTgoLO@mail.gmail.com> (raw)
In-Reply-To: <47F80BE0-6596-4A3D-B95F-72ABE2E0228C@kernel.crashing.org>

2010/7/1 Segher Boessenkool <segher@kernel.crashing.org>:
>> Maybe it was caused by floating exception.I found that,system received
>> a program check exception,the reason for it was REASON_ILLEGAL.
>>
>> I also use show_regs to print the NIP in exception,it seemed that
>> ,this exception was caused by 'vmhaddshs' instruction in user mode of
>> init process .
>>
>> Is vmhaddshs avaliable on e500mc? My cross compile tool is
>> gcc-4.1.2-glibc-2.5.0
>
> This isn't vmhaddshs (which is an AltiVec instruction), but something else
> that also uses primary opcode 4.
>
> It sounds like your toolchain isn't set up correctly for e500mc.
>
>
> Segher
>
>

I 've used cross_tool (powerpc_mc)  that freescale provided,  to
compile the kernel image, and

use an ordinary powerpc cross tool to compile busybox into cpio ramdisk.

      reply	other threads:[~2010-07-01  0:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-29 15:21 kernel init exception wilbur.chan
2010-06-29 16:51 ` Segher Boessenkool
2010-06-30  0:46   ` David Gibson
2010-06-30 14:35     ` wilbur.chan
2010-06-30 22:31       ` Segher Boessenkool
2010-07-01  0:10         ` wilbur.chan [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=AANLkTilNpYjhM5NRevXBcsAb-MFw55A8iSrDcRvTgoLO@mail.gmail.com \
    --to=wilbur512@gmail.com \
    --cc=chen.yu10@zte.com.cn \
    --cc=david@gibson.dropbear.id.au \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=segher@kernel.crashing.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).