From owner-freebsd-current Tue Mar 18 17:17:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA20698 for current-outgoing; Tue, 18 Mar 1997 17:17:34 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA20691 for ; Tue, 18 Mar 1997 17:17:28 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA20485; Wed, 19 Mar 1997 11:46:06 +1030 (CST) From: Michael Smith Message-Id: <199703190116.LAA20485@genesis.atrad.adelaide.edu.au> Subject: Re: 2.2 Kernel Unstable In-Reply-To: from The Hermit Hacker at "Mar 18, 97 08:52:17 pm" To: scrappy@hub.org (The Hermit Hacker) Date: Wed, 19 Mar 1997 11:46:05 +1030 (CST) Cc: bde@zeta.org.au, imp@village.org, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[