From owner-freebsd-current Sun Aug 16 19:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24178 for freebsd-current-outgoing; Sun, 16 Aug 1998 19:08:26 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24170 for ; Sun, 16 Aug 1998 19:08:24 -0700 (PDT) (envelope-from bright@www.hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.8.8) with SMTP id WAA10312; Sun, 16 Aug 1998 22:08:48 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 16 Aug 1998 22:08:48 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "J. W. Ballantine" cc: freebsd-current@FreeBSD.ORG Subject: Re: signal 11 on bootup In-Reply-To: <9808131924.AA19126@akiva.homer.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG if all you've done is change the memory, looks like hardware no? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's BSD. -- http://www.freebsd.org/ On Thu, 13 Aug 1998, J. W. Ballantine wrote: > > I'm running 3.0-980804-SNAP with an AHA-2490 scsi controller board, and I > just replaced the memory with new memory. Today when I rebooted the > system I received: > > pid 10 (fsck), uid 0: Exited on signal 11. > > Now I've been having problems with scsi 0 going into hard lock when I tried > to access the disk during install (either during the prob prior to the > the menu appearing or during the partitioning update write). > > Is this a hardware or software error?? > > Jim Ballantine > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message