From owner-freebsd-questions Mon Apr 12 10:52:19 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 672A314CF6 for ; Mon, 12 Apr 1999 10:52:11 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id KAA20054; Mon, 12 Apr 1999 10:49:32 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 12 Apr 1999 10:49:32 -0700 (PDT) From: Doug White To: Jack Freelander Cc: Jef , freebsd-questions@FreeBSD.ORG Subject: Re: 3.0 -> 3.1 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 9 Apr 1999, Jack Freelander wrote: > > > FreeBSD 3.0-Release has the tendency to reboot itself, as I mentioned > > > before. Others have the same problem. has this been fixed in 3.1? > > > > Can you be more specific? > > > > I'm not aware of any spontaneous reboots in 3.x releases. > > How can I explain spontaneous reboots? They just happen, and FreeBSD > leaves no record of why. I wrote to questions@FreeBSD.org some time ago, > and several other people replied that they were having the same problem. > I recently found out that hurricane.cs.miami.edu, another FreeBSD machine, > is having a similar problem. What gives? Bad memory? Unfortunately no one can do anything about it until we get a crash dump or something that illustrates the faulty code path(s). It's about impossible to fix unreliably-reproducible faults. It could be bad memory in parity-check systems, for all we know; their reboots may be correct and intended behavior. > Not to be rude, but the upgrade utility sucks. It shouldn't allow you to > even attempt an upgrade when it knows (and now so do I) that running > /stand/sysinstall off the hard disk, even in single user mode, causes a > ton of problems. You should upgrade from the *new* boot floppy; it knows how to deal with new upgrade-isms (except 3.1; the upgrade procedure there doesn't work). > Please let me know what kinds of bug fixes were made in going from 3.0 > to 3.1. There's a few thousand; you can start browsing at http://www.freebsd.org/cgi/cvsweb.cgi/src/. > How, if at all, can I find out why FreeBSD decides to reboot itself (in > case the problem doesn't go away)? Try building a debug kernel (config -g) with 'options DDB', and hopefully instead of rebooting it'll drop to the debugger. I suggest the Handbook section on kernel debugging for more information. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message