All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen P. Becker" <geoman@gentoo.org>
To: sparclinux@vger.kernel.org
Subject: nfsroot w/ smp 2.6.7 on ultra2 bug report
Date: Sun, 29 Aug 2004 17:26:36 +0000	[thread overview]
Message-ID: <413211CC.1020207@gentoo.org> (raw)

Hi,

I have an Ultra 2 with dual 200mhz ultrasparc I processors.  I had been 
trying to run nfsroot with kernel 2.6.7 on the machine, and could not 
get it to work:

IP-Config: Guessing netmask 255.255.255.0
IP-Config: Complete:
       device=eth0, addr\x192.168.1.7, mask%5.255.255.0, 
gw%5.255.255.255,
      host\x192.168.1.7, domain=, nis-domain=(none),
      bootserver\x192.168.1.1, rootserver\x192.168.1.1, rootpathLooking up port of RPC 100003/2 on 192.168.1.1
eth0: Link is up using internal transceiver at 100Mb/s, Full Duplex.
portmap: server 192.168.1.1 not responding, timed out
Root-NFS: Unable to get nfsd port number from server, using default
Looking up port of RPC 100005/1 on 192.168.1.1
portmap: server 192.168.1.1 not responding, timed out
Root-NFS: Unable to get mountd port number from server, using default
mount: server 192.168.1.1 not responding, timed out
Root-NFS: Server returned error -5 while mounting /usr/local/sparc
VFS: Unable to mount root fs via NFS, trying floppy.
VFS: Cannot open root device "<NULL>" or unknown-block(2,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown-block(2,0)
  <0>Press Stop-A to return to the boot prom

On a suggestion from Ciaran McCreesh, I recompiled my kernel without SMP 
support, and was able to mount nfsroot with no problems at all.  I also 
successfully compiled and booted a 2.4.27 smp kernel with nfsroot, and 
had no such problems.

Steve Becker

                 reply	other threads:[~2004-08-29 17:26 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=413211CC.1020207@gentoo.org \
    --to=geoman@gentoo.org \
    --cc=sparclinux@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 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.