From owner-freebsd-hackers Thu Jun 1 21:47:24 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA02487 for hackers-outgoing; Thu, 1 Jun 1995 21:47:24 -0700 Received: from temptation.interlog.com (temp@temptation.interlog.com [198.53.146.54]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA02481 for ; Thu, 1 Jun 1995 21:47:21 -0700 Received: (from temp@localhost) by temptation.interlog.com (8.6.9/8.6.9) id AAA13292; Fri, 2 Jun 1995 00:45:30 -0400 Date: Fri, 2 Jun 1995 00:45:29 -0400 From: Temptation Subject: Re: 2.0.5-ALPHA: Memory fault, sig 11 To: Charles Henrich cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199506020114.SAA18996@freefall.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: hackers-owner@FreeBSD.ORG Precedence: bulk Yes I had that same problem, Justin made me a kernel for my machine, and no more core dumps, everything works great now. Tho, I'm still testing the newest floppies by deleted everything and starting over, but I've finally got a install and programs working. On Thu, 1 Jun 1995, Charles Henrich wrote: > It appears that the 2.0.5-ALPHA kernel has several massive conflicts that cause > endless core dumps and signal 11 traps during the boot phase, and then during > execution of codes such as systat. Once a custom kernel is rebuilt however, > things are much cleaner. > > I dont know whats different between the kernel config for the snapshots and for > 2.05A but whatever it is, we need to get it back to the snapshot phase, we're > thing never (for me anyway) screwed up on a dozen different machines.. > > -Crh > -- > > Charles Henrich Michigan State University henrich@crh.cl.msu.edu > > http://rs560.msu.edu/~henrich/ >