From owner-freebsd-current Fri Mar 3 1:58:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 78F9E37B55C for ; Fri, 3 Mar 2000 01:58:27 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id BAA02685 for current@freebsd.org; Fri, 3 Mar 2000 01:40:14 GMT (envelope-from nik) Date: Fri, 3 Mar 2000 01:40:12 +0000 From: Nik Clayton To: current@freebsd.org Subject: Kernel hangs booting fresh -current Message-ID: <20000303014011.A754@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do, I just tried to go from -stable (built on Feb 24th) to -current, fresh yesterday (Thursday). "make buildworld" completed cleanly, and following /usr/src/UPDATING I made and installed a fresh kernel, and updated /dev (by running "MAKEDEV da0s1a" and "MAKEDEV da1s1a" with a -current mknod). Then I rebooted (without doing an "installworld", UPDATING says you do this *after* the reboot). The new kernel boots, but fails to mount the disks. Thinking this was just a mismatch between the kernel and the mount binary, I dug out my fixit floppy, got back in to the system, installed the new mount binaries (including the mount_* ones), and tried to reboot. This time, the system froze after the last kernel message was printed, but before the "swapon" message appears. This was a complete lock, the LED keys didn't work, neither did CTRL-ALT-DEL. Thinking there was something odd in my kernel config file, I recovered the system again, got back in, and built a -current GENERIC kernel, figuring that it should definitely work. I tried rebooting with this, and got an error message from the npx probe and an immediate reboot. That happened so quickly I couldn't get a good look at it, but the word "nexus" was in there somewhere. I stress this was with a stock GENERIC -current kernel (but built on a 3.4 system). Have I just hit a bad patch? I've been following the -current list for years, and watch for problems religiously -- I figured with the OpenSSL stuff out of the way, this was as good a time as any. On a related note, why does UPDATING say to build and install the kernel, and then reboot, before doing the "installworld"? That contradicts the advice in the Handbook (which I wrote), and I would've thought it's wrong precisely because it allows for things like kernel/mount mismatches to occur. I'd be very surprised if this is hardware failure. This system has been rock solid on all versions of 3.x, and gets stressed quite highly most days. I realise I haven't been able to provide a great deal of information about this, but I hope it rings bells with someone. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message