From owner-freebsd-alpha Sun Dec 27 04:16:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16569 for freebsd-alpha-outgoing; Sun, 27 Dec 1998 04:16:50 -0800 (PST) (envelope-from owner-freebsd-alpha@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16564 for ; Sun, 27 Dec 1998 04:16:48 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id NAA27916; Sun, 27 Dec 1998 13:16:28 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA08857 (5.67b/IDA-1.5); Sun, 27 Dec 1998 13:01:19 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id MAA22591; Sun, 27 Dec 1998 12:05:04 +0100 (CET) From: Wilko Bulte Message-Id: <199812271105.MAA22591@yedi.iaf.nl> Subject: Re: kernel make depend failure In-Reply-To: <13954.45089.385336.748730@grasshopper.cs.duke.edu> from Andrew Gallatin at "Dec 24, 98 04:27:17 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Sun, 27 Dec 1998 12:05:04 +0100 (CET) Cc: freebsd-alpha@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Andrew Gallatin wrote... > > Wilko Bulte writes: > > > Are you using NFS ? > > > > Bingo! I built a kernel from -current after copying the /sys tree > > to a local disk on the axp33. That kernel booted just fine. > > > > Strangely enough I have in the meantime built multiple kernels via NFS > > that also worked fine. So, it looks like that 'sometimes' the use of NFS > > results in a non booting kernel. Nasty... > > > > FWIW I'm using a FreeBSD226-release server, running a Kingston 10/100 PCI > > adapter: > > I'd wager the problem lies on the server side. I've built zillions > (well, OK, at least several hundred) kernels via NFS on various alphas > (PW500au, AS500/266, AS200/166) running FreeBSD using a 3.0-current > (x86) NFS server without any problems. Hmm. Interesting... > There have been numerous NFS fixes since 2.2.6. You might consider > upgrading your server to a more recent version of -stable (or even > better, to -current if you understand the ramifications). If that's > not an option, try backing down to NFSv2 if you're mounting /sys via NFSv3. I don't want my server to go to -current, but I may go to a -stable. The strange thing is A. I have only seen this happen on freebsd/axp and B. since a couple of days I have not seen the failure occur again. I use the same setup to build -current on a x86 box hooked up to the same server. And no hardware changes have been made to anything. Strange.... Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message