From owner-freebsd-hardware Mon Apr 28 03:06:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA05130 for hardware-outgoing; Mon, 28 Apr 1997 03:06:19 -0700 (PDT) Received: from gatekeeper.acucobol.ie (gatekeeper.acucobol.ie [194.125.135.194]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA05096; Mon, 28 Apr 1997 03:06:14 -0700 (PDT) Received: (from daemon@localhost) by gatekeeper.acucobol.ie (8.8.5/8.8.5) id LAA08666; Mon, 28 Apr 1997 11:05:31 +0100 (BST) Received: from guinness.acucobol.ie(194.125.135.195) by gatekeeper.acucobol.ie via smap (V2.0beta) id xma008457; Mon, 28 Apr 97 11:05:01 +0100 Received: from guinness (localhost [127.0.0.1]) by guinness.acucobol.ie (8.8.5/8.8.5) with ESMTP id LAA27919; Mon, 28 Apr 1997 11:05:47 +0100 (BST) Message-Id: <199704281005.LAA27919@guinness.acucobol.ie> From: "John McLaughlin" To: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: bash 1.14.7 Sig 11 on FreeBSD 2.2-970422-RELENG Date: Mon, 28 Apr 1997 11:05:47 +0100 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, Not sure if this belongs on hardware, but it did involve a sig 11, so... Basically, bash dumped core on the above when just installed from the standard 2.2 packages, which haven't been updated for the snap (or hadn't last Friday anyway). Pulling over the source and recompiling made the problem go away, and a kernel compile worked fine, which leads me to suspect the packages may need recompiling. The hardware is: ExpertBoard i430VX motherboard 16Mb EDO RAM Tekram 390F SCSI adaptor 2.1 Gb Quantum Fireball Genius NE2000 compatible network card. Which has worked fine in a number of other machines that I've configured Has anybody else come across this problem with bash or any of the other packages, or does it sound more like bas SIMMs? Could anyone suggest a means of testing the RAM to some *reasonable* extent? Regards,