From owner-freebsd-current Tue Mar 18 18:09:04 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA25483 for current-outgoing; Tue, 18 Mar 1997 18:09:04 -0800 (PST) Received: from thelab.hub.org (hal-ns3-02.netcom.ca [207.181.94.130]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA25477 for ; Tue, 18 Mar 1997 18:09:00 -0800 (PST) Received: from thelab.hub.org (LOCALHOST [127.0.0.1]) by thelab.hub.org (8.8.5/8.8.2) with SMTP id WAA16667; Tue, 18 Mar 1997 22:06:23 -0400 (AST) Date: Tue, 18 Mar 1997 22:06:23 -0400 (AST) From: The Hermit Hacker To: Michael Smith cc: bde@zeta.org.au, imp@village.org, current@FreeBSD.ORG Subject: Re: 2.2 Kernel Unstable In-Reply-To: <199703190116.LAA20485@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 19 Mar 1997, Michael Smith wrote: > The Hermit Hacker stands accused of saying: > > > > Okay, but this doesn't quite explain why a kernel (2.2, not 3.0) > > from around Feb 7th causes a SegFault, while a kernel generated by > > the 2.2-RELEASE source tree causes a system reboot... > > It all depends on where the fault occurs; if it's in memory used by a > program, the program gets killed. If it's in memory used by the > kernel, the kernel gets killed. > I hate to beat a dead horse here, but so far as I'm able to tell, if I were to plug in the March 18th kernel I created and do a 'make cleandir' on /usr/src, it will cause a panic/reboot. Same thing with the Feb 7th kernel just causes a SegFault...annoying, but liveable. As far as I can tell, this happens *very* consistently... It seems kind of suspicious to me that with the Feb 7th kernel, it consistently *doesn't* reboot where the March 18th one does...I don't know if there is anything in the bug reports I submitted for the March 18th kernel that will help, but they are there, and I still have the appropriate core files...