From owner-freebsd-stable Fri May 15 15:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15926 for freebsd-stable-outgoing; Fri, 15 May 1998 15:31:02 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15918 for ; Fri, 15 May 1998 15:30:58 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id QAA24093; Fri, 15 May 1998 16:26:38 -0600 (MDT) Date: Fri, 15 May 1998 16:26:38 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199805152226.QAA24093@narnia.plutotech.com> To: Werner Griessl cc: stable@FreeBSD.ORG Subject: Re: broken remote boot Newsgroups: pluto.freebsd.stable In-Reply-To: <199805151243.OAA16044@btp1da.phy.uni-bayreuth.de> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk In article <199805151243.OAA16044@btp1da.phy.uni-bayreuth.de> you wrote: > I have a problem with diskless remote boot. > I verified, that the changes preventing remote boot > comes between May 6 and May 7 into the stable sources. > With a client kernel from May 6 remote boot is ok, > with a kernel from May 7 the boot fails with: > > "panic: cannot mount root" > > The kernel loads vio bootp, checks the devices up to > "npx0: INT 16 interface", then comes the panic. > normally followes the lines: > NFS SWAP: ... > NFS ROOT: ... > > Here are all files which change between May 6 and 7 : It was probably the changes I made to autoconf.c, but as I don't perform any diskless booting it will be difficult for me to determine what exactly is causing the problem. Can you instrument i386/i386/autoconf.c and determin why it fails to consider an NFS root? > Werner -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message