From owner-freebsd-embedded@FreeBSD.ORG Tue Mar 23 14:20:32 2010 Return-Path: Delivered-To: embedded@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F366B106564A; Tue, 23 Mar 2010 14:20:31 +0000 (UTC) (envelope-from ganbold@micom.mng.net) Received: from publicd.ub.mng.net (publicd.ub.mng.net [202.179.0.88]) by mx1.freebsd.org (Postfix) with ESMTP id A70BC8FC0C; Tue, 23 Mar 2010 14:20:31 +0000 (UTC) Received: from [202.179.21.132] (helo=beastie.micom.mng.net) by publicd.ub.mng.net with esmtpa (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Nu4D7-000NwN-8D; Tue, 23 Mar 2010 21:31:57 +0800 Message-ID: <4BA8C2CC.3050808@micom.mng.net> Date: Tue, 23 Mar 2010 21:31:56 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.23 (X11/20091011) MIME-Version: 1.0 To: Marcel Moolenaar References: In-Reply-To: X-Enigmail-Version: 0.95.7 OpenPGP: id=78F6425E Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: powerpc@freebsd.org, embedded@freebsd.org Subject: Re: Anyone using BOOTP with latest current (Book-E)? X-BeenThere: freebsd-embedded@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Dedicated and Embedded Systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2010 14:20:32 -0000 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.]