RE: root nfs boot problems

RE: root nfs boot problems

[Stephan Ruettiger (r0337c)]

Hello Simon,

i have actually the same problem as you have in NOV 99 (showing below),
but i don't find the answer to your problem in the mailinglist-archive
(linuxppc-embedded). So i hope you can tell me how you have solved this
problem. I use a 2.2.13 kernel with math emulation.
The same configuration with the old kernel (2.1.119 - no module support)
works fine.

> I am trying to boot embedded-2.2.5 kernel using a nfsr root filesystem.
> Here is a log of the console session.  I get a "neighbour table
> overflow" error.  What does this mean ?  I have a look in the source but
> can't figure out what is happening.
>
> Thanks,
> Brendan Simon.
>
> loaded at:     FF801000 FF813BAC
> relocated to:  00100000 00112BAC
> board data at: 001001F8 00100214
> relocated to:  00200100 0020011C
> zimage at:     FF808000 FF8690B9
> avail ram:     00201000 00400000
>
> Linux/PPC load: root=/dev/nfs nfsaddrs=203.21.127.132:203.21.127.160
> nfsroot=203.21.127.160:/sys/ads-root
> Uncompressing Linux...done.
> Now booting the kernel
> Linux version 2.2.5 (root@k9) (gcc version egcs-2.91.66 19990314
> (egcs-1.1.2 rel
> ease)) #39 Fri Nov 12 17:49:11 EST 1999
> Boot arguments: root=/dev/nfs nfsaddrs=203.21.127.132:203.21.127.160
> nfsroot=203
> .21.127.160:/sys/ads-root
> time_init: decrementer frequency = 93750000/60
> Calibrating delay loop... 24.52 BogoMIPS
> Memory: 15188k available (700k kernel code, 464k data, 32k init)
> [c0000000,c1000
> 000]
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> Starting kswapd v 1.5
> CPM UART driver version 0.02
> ttyS00 at 0x0280 is a SMC
> ttyS01 at 0x0100 is a SCC
> ttyS02 at 0x0200 is a SCC
> pty: 256 Unix98 ptys configured
> RAM disk driver initialized:  16 RAM disks of 4096K size
> eth0: CPM ENET Version 0.2, 00:d0:1f:11:22:33
> IP-Config: Guessing netmask 255.255.255.0
> neighbour table overflow
> neighbour table overflow
> neighbour table overflow
> neighbour table overflow
> portmap: server 203.21.127.160 not responding, timed out
> Root-NFS: Unable to get nfsd port number from server, using default
> Looking up port of RPC 100005/1 on 203.21.127.160
> neighbour table overflow
> neighbour table overflow
> neighbour table overflow
> neighbour table overflow
> portmap: server 203.21.127.160 not responding, timed out
> Root-NFS: Unable to get mountd port number from server, using default
> neighbour table overflow
> neighbour table overflow
> neighbour table overflow
> neighbour table overflow
> mount: server 203.21.127.160 not responding, timed out
> Root-NFS: Server returned error -5 while mounting /sys/ads-root
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device 02:00
> Kernel panic: VFS: Unable to mount root fs on 02:00
> Rebooting in 180 seconds..<0>Kernel panic: Kernel Mode Software FPU
> Emulation
> Rebooting in 180 seconds..Machine check in kernel mode.
> Caused by (from msr): regs c0f4bb30 Machine check signal - probably due
> to mm fa
> ult


------------------------
Stephan Ruettiger
Motorola Munich
r0337c@email.sps.mot.com
------------------------

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

RE: root nfs boot problems

[Don Holmgren]

I don't believe the "neighbour table overflow" errors are the problem.  I
get them frequently but otherwise have success.

It looks like a problem on your nfs server.  The "unable to get nfsd port
number from server" and "unable to get mountd port number from server"
messages indicate that at minimum, the portmapper is not running on your
server.  Perhaps mountd and/or nfsd are also not running.

If you've not done this already, you should verify from another machine
that you can mount the root file system from your server.  Also, it's
always been useful for me to monitor system logs on my server when
debugging nfs root mounts - make sure your target board actually is making
contact, make sure your server grants access, etc...

Don Holmgren
Fermilab


On Tue, 21 Mar 2000, Stephan Ruettiger (r0337c) wrote:

>
> Hello Simon,
>
> i have actually the same problem as you have in NOV 99 (showing below),
> but i don't find the answer to your problem in the mailinglist-archive
> (linuxppc-embedded). So i hope you can tell me how you have solved this
> problem. I use a 2.2.13 kernel with math emulation.
> The same configuration with the old kernel (2.1.119 - no module support)
> works fine.
>
> > I am trying to boot embedded-2.2.5 kernel using a nfsr root filesystem.
> > Here is a log of the console session.  I get a "neighbour table
> > overflow" error.  What does this mean ?  I have a look in the source but
> > can't figure out what is happening.
> >
> > Thanks,
> > Brendan Simon.
> >
> > loaded at:     FF801000 FF813BAC
> > relocated to:  00100000 00112BAC
> > board data at: 001001F8 00100214
> > relocated to:  00200100 0020011C
> > zimage at:     FF808000 FF8690B9
> > avail ram:     00201000 00400000
> >
> > Linux/PPC load: root=/dev/nfs nfsaddrs=203.21.127.132:203.21.127.160
> > nfsroot=203.21.127.160:/sys/ads-root
> > Uncompressing Linux...done.
> > Now booting the kernel
> > Linux version 2.2.5 (root@k9) (gcc version egcs-2.91.66 19990314
> > (egcs-1.1.2 rel
> > ease)) #39 Fri Nov 12 17:49:11 EST 1999
> > Boot arguments: root=/dev/nfs nfsaddrs=203.21.127.132:203.21.127.160
> > nfsroot=203
> > .21.127.160:/sys/ads-root
> > time_init: decrementer frequency = 93750000/60
> > Calibrating delay loop... 24.52 BogoMIPS
> > Memory: 15188k available (700k kernel code, 464k data, 32k init)
> > [c0000000,c1000
> > 000]
> > POSIX conformance testing by UNIFIX
> > Linux NET4.0 for Linux 2.2
> > Based upon Swansea University Computer Society NET3.039
> > NET4: Unix domain sockets 1.0 for Linux NET4.0.
> > NET4: Linux TCP/IP 1.0 for NET4.0
> > IP Protocols: ICMP, UDP, TCP
> > Starting kswapd v 1.5
> > CPM UART driver version 0.02
> > ttyS00 at 0x0280 is a SMC
> > ttyS01 at 0x0100 is a SCC
> > ttyS02 at 0x0200 is a SCC
> > pty: 256 Unix98 ptys configured
> > RAM disk driver initialized:  16 RAM disks of 4096K size
> > eth0: CPM ENET Version 0.2, 00:d0:1f:11:22:33
> > IP-Config: Guessing netmask 255.255.255.0
> > neighbour table overflow
> > neighbour table overflow
> > neighbour table overflow
> > neighbour table overflow
> > portmap: server 203.21.127.160 not responding, timed out
> > Root-NFS: Unable to get nfsd port number from server, using default
> > Looking up port of RPC 100005/1 on 203.21.127.160
> > neighbour table overflow
> > neighbour table overflow
> > neighbour table overflow
> > neighbour table overflow
> > portmap: server 203.21.127.160 not responding, timed out
> > Root-NFS: Unable to get mountd port number from server, using default
> > neighbour table overflow
> > neighbour table overflow
> > neighbour table overflow
> > neighbour table overflow
> > mount: server 203.21.127.160 not responding, timed out
> > Root-NFS: Server returned error -5 while mounting /sys/ads-root
> > VFS: Unable to mount root fs via NFS, trying floppy.
> > VFS: Cannot open root device 02:00
> > Kernel panic: VFS: Unable to mount root fs on 02:00
> > Rebooting in 180 seconds..<0>Kernel panic: Kernel Mode Software FPU
> > Emulation
> > Rebooting in 180 seconds..Machine check in kernel mode.
> > Caused by (from msr): regs c0f4bb30 Machine check signal - probably due
> > to mm fa
> > ult
>
>
> ------------------------
> Stephan Ruettiger
> Motorola Munich
> r0337c@email.sps.mot.com
> ------------------------
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: root nfs boot problems

[Wolfgang Denk]

In message <Pine.SGI.3.95.1000321111628.2421C-100000@hppc.fnal.gov> you wrote:
>
> I don't believe the "neighbour table overflow" errors are the problem.  I
> get them frequently but otherwise have success.

I have never seen such errors when the ethernet  inrface  is  working
correclty.

> It looks like a problem on your nfs server.  The "unable to get nfsd port
> number from server" and "unable to get mountd port number from server"
> messages indicate that at minimum, the portmapper is not running on your
> server.  Perhaps mountd and/or nfsd are also not running.

Well, IMHO it's more likely that no packets were  ever  sent  to  the
ethernet  at  all.  This  type  of problemppens for instance when the
Transmit Enable signal is not asserted.

It might be useful to check with a sniffer if the box is transmitting
at all...

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
Don't put off for tomorrow what you can  do  today,  because  if  you
enjoy it today you can do it again tomorrow.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: root nfs boot problems

[Don Holmgren]

On Tue, 21 Mar 2000, Wolfgang Denk wrote:

>
> In message <Pine.SGI.3.95.1000321111628.2421C-100000@hppc.fnal.gov> you wrote:
> >
> > I don't believe the "neighbour table overflow" errors are the problem.  I
> > get them frequently but otherwise have success.
>
> I have never seen such errors when the ethernet  inrface  is  working
> correclty.

>From a boot this morning on an MVME-2307:

  eth0: DC21140 at 0x11000 (PCI bus 0, device 14), h/w address 08:00:3e:2a:1d:42,
      and requires IRQ18 (provided by PCI BIOS).
  de4x5.c:V0.544 1999/5/8 davies@maniac.ultranet.com
  Looking up port of RPC 100003/2 on 131.225.84.99
  neighbour table overflow
  eth0: media is TP.
  Looking up port of RPC 100005/1 on 131.225.84.99
  VFS: Mounted root (NFS filesystem) readonly.
  . . .

I almost always get this single "neighbour table overflow" message, but
subsequently no ethernet problems.


>
> > It looks like a problem on your nfs server.  The "unable to get nfsd port
> > number from server" and "unable to get mountd port number from server"
> > messages indicate that at minimum, the portmapper is not running on your
> > server.  Perhaps mountd and/or nfsd are also not running.
>
> Well, IMHO it's more likely that no packets were  ever  sent  to  the
> ethernet  at  all.  This  type  of problemppens for instance when the
> Transmit Enable signal is not asserted.
>
> It might be useful to check with a sniffer if the box is transmitting
> at all...
>
> Wolfgang Denk
>

I definitely agree.  tcpdump on the nfs server (or strace on
rpc.mountd/rpc.nfsd tasks) would do the trick.

Don Holmgren


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

Re: root nfs boot problems

[Stephan Ruettiger (r0337c)]

The tcpdump during the boot sequence shows me the error. I see at the
host the packets during tftp download of the zImage file. As the NFS
client try to connect i see nothing. So i changed the default setting
for ethernet from SCC2 to SCC1 (as described in the manual for the board
:-) and it
works.

Wolfgang Denk wrote:
>
> In message <Pine.SGI.3.95.1000321111628.2421C-100000@hppc.fnal.gov> you wrote:
> >
> > I don't believe the "neighbour table overflow" errors are the problem.  I
> > get them frequently but otherwise have success.
>
> I have never seen such errors when the ethernet  inrface  is  working
> correclty.
>
> > It looks like a problem on your nfs server.  The "unable to get nfsd port
> > number from server" and "unable to get mountd port number from server"
> > messages indicate that at minimum, the portmapper is not running on your
> > server.  Perhaps mountd and/or nfsd are also not running.
>
> Well, IMHO it's more likely that no packets were  ever  sent  to  the
> ethernet  at  all.  This  type  of problemppens for instance when the
> Transmit Enable signal is not asserted.
>
> It might be useful to check with a sniffer if the box is transmitting
> at all...

Thanks,

     Stephan Ruettiger

------------------------
Stephan Ruettiger
Motorola Munich
r0337c@email.sps.mot.com
------------------------

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/