Date: Sun, 3 Dec 1995 18:20:38 -0700 From: Nate Williams <nate@rocky.sri.MT.net> To: uhclem@%nemesius@fw.ast.com (Frank Durda IV) Cc: bugs@FreeBSD.ORG, davidg@Root.COM Subject: Re: Mission Impossible-style crashes on 2.1.0 Message-ID: <199512040120.SAA01713@rocky.sri.MT.net> In-Reply-To: <m0tMNus-000CccC@nemesis.lonestar.org> References: <m0tMNus-000CccC@nemesis.lonestar.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> [0]However, in the seven days since upgrading to 2.1.0, the same hardware > [0]has experienced an average of 10 unexpected reboots, or just over > [0]one a day. The systems with more load (news vs no news) crash more often. Not to discount your problems, but I've got 3 boxes used very heavily that *aren't* seeing any problems (except for NFS bugs which I believe David and John are aware of), so I'm trying to figure out what's different about your setup vs. mine. What kind of hardware, what kind of setup (NFS, routers, SLIP/PPP), what kind of problems are these boxes running. > These are *very* stock systems where the operating system is concerned. > Kernels have been recompiled to eliminate drivers not in use, but that is > it. Again, X is not in use. C-news, inn, smail and a few other odds and > ends are the applications that are present. Some have network boards > and drivers loaded, but are not connected to an active network. Obviously the boxes *must* be on somewhat of a loaded network if you're running News. :) Can you give more specific details, since w/out them it's just shooting in the dark? Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512040120.SAA01713>