From owner-freebsd-current  Fri Dec 15 14:01:21 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id OAA20750
          for current-outgoing; Fri, 15 Dec 1995 14:01:21 -0800 (PST)
Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA20742
          for <current@FreeBSD.ORG>; Fri, 15 Dec 1995 14:01:17 -0800 (PST)
Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id PAA17775; Fri, 15 Dec 1995 15:03:33 -0700
Date: Fri, 15 Dec 1995 15:03:33 -0700
From: Nate Williams <nate@rocky.sri.MT.net>
Message-Id: <199512152203.PAA17775@rocky.sri.MT.net>
To: Chuck Robey <chuckr@glue.umd.edu>
Cc: Nate Williams <nate@rocky.sri.MT.net>, current@FreeBSD.ORG
Subject: Re: -current kernel is *very* unusable
In-Reply-To: <Pine.SUN.3.91.951215164349.10416C-100000@cappuccino.eng.umd.edu>
References: <199512151757.KAA16788@rocky.sri.MT.net>
	<Pine.SUN.3.91.951215164349.10416C-100000@cappuccino.eng.umd.edu>
Sender: owner-current@FreeBSD.ORG
Precedence: bulk

[ -current kernel ]

> > I'm getting complete hangs, reboots with no core dumps, and I can't even
> > get into DDB.
> 
> Nate, I had trouble also, but the last 3 ctm updates had a load of kernel 
> fixes, and that stopped the panics.  Can I suggest you make sure you're 
> *very* current?  Maybe that won't help, but it sure did on my systems.

The system is running code that is now 24 hours out of date, but I'll be
updating it to the most recent code as soon as I can get a kernel to
last long enough to allow me to update the kernel code.

However, I haven't seen anything in the commits regarding fixes in the
last 24 hours or so.  All of the changes seemed to be prototype fixes
and Linux compatability fixes.

> BTW, that includes a boatload of fixes changing lkms and ps and the like, 
> so your libs and ps etc. have to be as current as your kernel.

Of course.


Nate