Date: Tue, 23 Mar 2010 21:31:56 +0800 From: Ganbold <ganbold@micom.mng.net> To: Marcel Moolenaar <xcllnt@mac.com> Cc: powerpc@freebsd.org, embedded@freebsd.org Subject: Re: Anyone using BOOTP with latest current (Book-E)? Message-ID: <4BA8C2CC.3050808@micom.mng.net> In-Reply-To: <B7BAFA66-33DF-4EAB-835D-50BEEF7919D0@mac.com> References: <B7BAFA66-33DF-4EAB-835D-50BEEF7919D0@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar wrote: > I get the following on a recent -current (on a P2020 eval system): > > bootpc_init: wired to interface 'tsec0' > Sending DHCP Discover packet from interface tsec0 (00:e0:0c:02:00:fd) > tsec0: link state changed to DOWN > tsec0: link state changed to UP > Received DHCP Offer packet on tsec0 from 192.168.4.1 (accepted) (no root path) > Sending DHCP Request packet from interface tsec0 (00:e0:0c:02:00:fd) > Received DHCP Ack packet on tsec0 from 192.168.4.1 (accepted) (got root path) > tsec0 at 192.168.4.151 server 192.168.4.1 boot file powerpc/boot/loader > subnet mask 255.255.255.0 router 192.168.4.1 rootfs 192.168.4.1:/net/powerpc > Adjusted interface tsec0 > krpc_call: sosend: 65 > krpc_call: sosend: 65 > panic: nfs_boot: mountd root, error=65 > KDB: enter: panic > [ thread pid 0 tid 100000 ] > Stopped at kdb_enter+0x60: addi r0, r0, 0x0 > db> bt > Tracing pid 0 tid 100000 td 0xc0450360 > 0xc2008ae0: at panic+0x13c > 0xc2008b40: at bootpc_init+0x1910 > 0xc2008c20: at mi_startup+0x11c > 0xc2008c50: at __start+0x140 > > BTW: error 65 is EHOSTUNREACH, which I think is caused by a link flag. > Yes, I've observed it in recent current. Looks like starting order matters for nfs. I tried in following order: /etc/rc.d/rpc_bind start /etc/rc.d/mountd start /etc/rc.d/nfsd start hth, Ganbold -- If people drank ink instead of Schlitz, they'd be better off. -- Edward E. Hippensteel [What brand of ink? Ed.]
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BA8C2CC.3050808>