Net booting current snapshot on openrd and sheevaplug

Ian Lepore ian at FreeBSD.org
Fri Mar 29 14:17:35 UTC 2013


On Mon, 2013-03-25 at 22:28 +0000, Jeff Penn wrote:
> On Sat, Mar 23, 2013 at 08:40:48PM -0600, Ian Lepore wrote:
> 
> > What was the value before you changed it to -1?  It looks like it probed
> > and found both 0 and 1, maybe that confused it.  If the value wasn't
> > zero originally, I'd say change it to that.  If that amounts to changing
> > it back to what it was, the problem must be elsewhere.
> 
> The original value was 8.  I've tried several values and setting it to
> 0 appears to get the furthest, performing a successful DHCP request:
> 
> ...
> mge0: link state changed to UP
> Received DHCP Offer packet on mge0 from 192.168.0.10 (accepted) (no root path)
> Received DHCP Offer packet on mge0 from 192.168.0.10 (ignored) (no root path)
> ugen0.2: <vendor 0x05e3> at usbus0
> uhub1: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/77.32, addr 2> on usbus0
> uhub1: MTT enabled
> uhub1: 4 ports with 4 removable, self powered
> ugen0.3: <vendor 0x05e3> at usbus0
> uhub2: <vendor 0x05e3 USB2.0 Hub, class 9/0, rev 2.00/77.32, addr 3> on usbus0
> uhub2: MTT enabled
> uhub2: 4 ports with 4 removable, self powered
> Sending DHCP Request packet from interface mge0 (f0:ad:4e:00:61:58)
> Received DHCP Ack packet on mge0 from 192.168.0.10 (accepted) (got root path)
> mge0 at 192.168.0.16 server 192.168.0.10 boot file openrd/kernel.bin
> subnet mask 255.255.255.0 router 192.168.0.1 rootfs 192.168.0.10:/mnt/work/nfsroot/arm-8-le hostname openrd
> Adjusted interface mge0
> krpc_call: sosend: 64
> krpc_call: sosend: 64
> panic: nfs_boot: mountd root, error=64
> KDB: enter: panic
> [ thread pid 0 tid 100000 ]
> Stopped at      kdb_enter+0x48: ldrb    r15, [r15, r15, ror r15]!
> db>
> 
> Jeff

Have you managed to make any progress on this?  It seems strange that it
can talk to the dhcp server okay, but then when it tries to do the mount
rpc it gets EHOSTDOWN.  If it were something like ECONNREFUSED I'd want
to blame an nfs config error, but EHOSTDOWN seems very strange.

-- Ian




More information about the freebsd-arm mailing list