Ultralinux archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Erik de Castro Lopo <nospam@mega-nerd.com>
To: ultralinux@vger.kernel.org
Subject: Troubles booting sparc64 SMP 2.4.18 kernel
Date: Sun, 17 Mar 2002 00:11:32 +0000	[thread overview]
Message-ID: <marc-linux-ultrasparc-101632405919252@msgid-missing> (raw)

Hi all,

I've got linux running on an dual CPU E220R. The base system is Debian Woody and 
I've installed the sparc64 compiler and binutils

    root@razor > sparc64-linux-gcc -v
    Reading specs from /usr/lib/gcc-lib/sparc-linux/3.0.3/specs
    Configured with: ../src/configure -v --enable-languages=c --prefix=/usr 
      --infodir=/share/info --mandir=/share/man --enable-shared --with-gnu-as 
      --with-gnu-ld --with-system-zlib --enable-long-long --enable-nls --without-x 
      --without-included-gettext --disable-checking --with-cpu=v7 sparc-linux
    Thread model: single
    gcc version 3.0.3
    root@razor > ld -V
    GNU ld version 2.11.92.0.12.3 20011121 Debian/GNU Linux
      Supported emulations:
       elf32_sparc
       sparclinux
       elf64_sparc
       sun4

I am able to build a working uni-processor sparc64 kernel which boots and works 
as expected :

    root@razor > cat sizeof.c 
    #include <stdio.h>
    
    int main (void)
    {	printf ("sizeof (void*) = %d\n", sizeof (void*)) ;
        return 0 ;
    } /* main */

    root@razor > sparc64-linux-gcc -m64 sizeof.c -o sizeof
    root@razor > ./sizeof 
    sizeof (void*) = 8

This seems to suggest that this is a 64 bit aware kernel.

If I then take the working uni-processor kernel tree, switch
on SMP support and then do 

    make dep ; make clean ; make ; make modules ; 
    make modules_install

and copy the kernel to /boot, run SILO and reboot, it starts off
OK but the seems to fail just after init is run. This is the last 
part of the boot messages:

    IP: routing cache hash table of 4096 buckets, 64Kbytes
    TCP: Hash tables configured (established 32768 bind 32768)
    NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
    VFS: Mounted root (ext2 filesystem) readonly.
    version 2.84 booting
    cannot ®¨Høcannot fork, retry..
    cannot fork, retry..
    cannot fork, retry..
    ¹½Ñ™½É­É•ÑÉåÿ

I have also tried to boot a 32 bit only SMP kernel but that fails in the
same way. Anybody have any clues?

Cheers,
Erik
-- 
+-----------------------------------------------------------+
  Erik de Castro Lopo  nospam@mega-nerd.com (Yes it's valid)
+-----------------------------------------------------------+
Seen on usenet (possibly a quote from an IBM exec):
"Each large company needs its Vietnam, and Microsoft will
 experience it with NT..."

             reply	other threads:[~2002-03-17  0:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-17  0:11 Erik de Castro Lopo [this message]
2002-03-17  1:17 ` Troubles booting sparc64 SMP 2.4.18 kernel Keith Owens
2002-03-19  7:35 ` Erik de Castro Lopo
2002-03-19  8:19 ` David S. Miller
2002-03-19 19:59 ` Erik de Castro Lopo
2002-03-19 22:30 ` David S. Miller
2002-03-19 23:55 ` Erik de Castro Lopo
2002-03-20  1:22 ` David S. Miller
2002-03-20  4:11 ` Erik de Castro Lopo
2002-03-20  4:23 ` David S. Miller
2002-04-11  4:32 ` David S. Miller

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=marc-linux-ultrasparc-101632405919252@msgid-missing \
    --to=nospam@mega-nerd.com \
    --cc=ultralinux@vger.kernel.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