From owner-freebsd-current  Sun Aug 16 17:34:10 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id RAA14369
          for freebsd-current-outgoing; Sun, 16 Aug 1998 17:34:10 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from att.com (kcgw2.att.com [192.128.133.152])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA14362
          for <freebsd-current@freebsd.org>; Sun, 16 Aug 1998 17:34:07 -0700 (PDT)
          (envelope-from jwb@homer.att.com)
Received: from kcig2.att.att.com by kcgw2.att.com (AT&T/UPAS)
	for freebsd.org!freebsd-current
	sender homer.att.com!jwb (homer.att.com!jwb); Thu Aug 13 14:04 CDT 1998
Received: from ulysses.homer.att.com (ulysses.homer.att.com [135.205.212.4])
	by kcig2.att.att.com (AT&T/GW-1.0) with ESMTP id OAA25625
	for <freebsd-current@freebsd.org>; Thu, 13 Aug 1998 14:24:31 -0500 (CDT)
Received: from akiva.homer.att.com (akiva.homer.att.com [135.205.213.77])
	by ulysses.homer.att.com (8.8.8/8.8.8) with SMTP id PAA29037
	for <freebsd.org!freebsd-current>; Thu, 13 Aug 1998 15:24:25 -0400 (EDT)
Received: by akiva.homer.att.com (4.1) id AA19126; Thu, 13 Aug 98 15:24:26 EDT
Message-Id: <9808131924.AA19126@akiva.homer.att.com>
Received: from localhost.homer.att.com [127.0.0.1] by akiva; Thu Aug 13 15:24:25 EDT 1998
X-Mailer: exmh version 2.0.2 2/24/98
To: freebsd-current@FreeBSD.ORG
Subject: signal 11 on bootup
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 13 Aug 1998 15:24:24 -0400
From: "J. W. Ballantine" <jwb@homer.att.com>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


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