From owner-freebsd-questions  Fri Sep  1 14: 0:36 2000
Delivered-To: freebsd-questions@freebsd.org
Received: from gateway.telecom.ksu.edu (gateway-1.telecom.ksu.edu [129.130.63.239])
	by hub.freebsd.org (Postfix) with ESMTP id 2F65137B422
	for <questions@freebsd.org>; Fri,  1 Sep 2000 14:00:34 -0700 (PDT)
Received: from sioux.telecom.ksu.edu(129.130.60.32) by pawnee.telecom.ksu.edu via smap (V2.0)
	id xma017680; Fri, 1 Sep 00 16:00:18 -0500
Message-ID: <39B01910.7688008C@telecom.ksu.edu>
Date: Fri, 01 Sep 2000 16:01:04 -0500
From: nathan <beemern@telecom.ksu.edu>
X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-STABLE i386)
X-Accept-Language: en
MIME-Version: 1.0
To: questions@freebsd.org
Subject: Re: locking after upgrading to 4.1-STABLE
References: <39AED892.2332659@telecom.ksu.edu> <39AF013E.36D56411@urx.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Kent Stewart wrote:

> beemern@telecom.ksu.edu wrote:
> >
> > I decided to "fix" my non-broken system, and go from 4.0-STABLE to
> > 4.1-STABLE
> > i cvsup'd the src tree and following the web instructions for make'ing
> > world.
> > i've also recompiled my kernel and remade devices etc.
>
> It is fixed. You need to recvsup and build the system. If all you get
> is uipc_socket2.c, you might get away with just rebuilding your
> kernel. That is the module that locked your system up.
>
> Kent

SUCCESS !! and 'many thanks' for the help.

Question:  how would i go about determining this on my own ?  is there a
debug or log file?  how could/does a person KNOW that uipc_socket2.c is
crashing the system?





To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message