From owner-freebsd-questions Thu Aug 31 18: 8: 6 2000 Delivered-To: freebsd-questions@freebsd.org Received: from 2711.dynacom.net (2711.dynacom.net [206.107.213.3]) by hub.freebsd.org (Postfix) with ESMTP id 0696037B424 for ; Thu, 31 Aug 2000 18:08:04 -0700 (PDT) Received: from urx.com (dsl1-160.dynacom.net [206.159.132.160]) by 2711.dynacom.net (Build 101 8.9.3/NT-8.9.3) with ESMTP id SAA04896; Thu, 31 Aug 2000 18:07:10 -0700 Message-ID: <39AF013E.36D56411@urx.com> Date: Thu, 31 Aug 2000 18:07:10 -0700 From: Kent Stewart Reply-To: kstewart@urx.com Organization: Dynacom X-Mailer: Mozilla 4.74 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: beemern@telecom.ksu.edu Cc: freebsd-questions@FreeBSD.ORG Subject: Re: locking after upgrading to 4.1-STABLE References: <39AED892.2332659@telecom.ksu.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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 > > now.. i'm having issues with any net services. i've disabled all inetd > services and apachectl. > the system is 'fine' (seemingly) if i log in and run X and do standard > stuff like email, netscape, irc, etc... > > but, if i try to run any network services... something like: > > apachectl start > (try connecting to it via web and get nothing) > apachectl stop (always results in momentary lock, and then spontaneous > reboot) > > if i enable my ftp server and try connecting from another machine.. it > will cause a system freeze which requires hard reset. > > also.. it would hang during boot when loading sshd and i had to reboot > and disable sshd init to even get it to ever boot > > i've tried with both the generic kernel, and my prev kernel config (with > new build tho) and get same thing. i looked in LINT for anything 'new' > that might apply.. but didn't see anything > > any ideas on where to even START with this situation. i'm quite sure it > can't be hardware since this system has run FLAWLESS for the past > several months.. since, ironically, i went from 4.0-RELEASE to > 4.0-STABLE, which went smoothly. > > if it matters, its a dual pIII/550 256MB ram workstation, which, up > until now has just been a GEM of a box to work on... i'd hate to have to > re-install from scratch and patch my system together from backups > > many thanks > nathan > p.s. "if it ain't broke.. DON'T FIX IT!" > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message