linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: "Andriy Korud" <a.korud@vector.com.pl>
Cc: Roland Dreier <rdreier@cisco.com>, linuxppc-embedded@ozlabs.org
Subject: Re: Anyone success with 440GR Rev.B (1.1)?
Date: Fri, 2 Feb 2007 21:26:25 +0100	[thread overview]
Message-ID: <200702022126.25872.sr@denx.de> (raw)
In-Reply-To: <adafy9o4l74.fsf@cisco.com>

On Friday 02 February 2007 16:45, Roland Dreier wrote:
>  > I have complete system (U-Boot, Linux, userspace) running on 440GR
>  > Rev.A. However after mounting newer chip revision (Rev.B, 1.1) U-Boot
>  > and Linux boots fine, however when trying to execute first userland
>  > application (init), I get:
>  >
>  > Freeing unused kernel memory: 112k init
>  > init has generated signal 4 but has no handler for it
>  > Kernel panic - not syncing: Attempted to kill init!
>
> signal 4 is SIGILL.  Just a guess but do you have a cputable entry for
> 440GR rev B in your arch/powerpc/kernel/cputable.c?

Good idea. That's probably it.

> If you don't then 
> I think the default kernel settings will result in the wrong cacheline
> size being used, which leads to userspace often dying with illegal
> instruction traps.
>
> (I don't see any 440GR entries in cputable.c, neither rev A nor rev B,
> in the upstream kernel so I'm assuming you're patching your kernel
> somehow.  So checking that your patch covers rev B would be the first
> thing to do)

440GR has the same PVR as 440EP:

440EP Rev B == 440GR Rev A
440EP Rev C == 440GR Rev B

So your kernel should support 440EP Rev. C. The denx kernel has support for 
those CPU's included. I'll try to send some patches in the next few days to 
support them in the kernel.org version.

Best regards,
Stefan

  reply	other threads:[~2007-02-02 20:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-02 11:35 Anyone success with 440GR Rev.B (1.1)? Andriy Korud
2007-02-02 15:45 ` Roland Dreier
2007-02-02 20:26   ` Stefan Roese [this message]
2007-02-02 20:37     ` Andriy Korud

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=200702022126.25872.sr@denx.de \
    --to=sr@denx.de \
    --cc=a.korud@vector.com.pl \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rdreier@cisco.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).