Date: Mon, 28 Apr 1997 23:49:05 +0900 From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> To: "John McLaughlin" <John.McLaughlin@acucobol.ie> Cc: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: bash 1.14.7 Sig 11 on FreeBSD 2.2-970422-RELENG Message-ID: <199704281449.XAA16419@zodiac.mech.utsunomiya-u.ac.jp> In-Reply-To: Your message of "Mon, 28 Apr 1997 11:05:47 %2B0100." <199704281005.LAA27919@guinness.acucobol.ie> References: <199704281005.LAA27919@guinness.acucobol.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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? Is your CPU sufficiently cooled by a fan? I once had a bad CPU cooler (fan) with which my CPU (Pentium 120Mhz) caused sig 11 from time to time under heavy load such as `make world'. Once the CPU is cooled down the problem went away; which made me take quite a while to diagnose the cause. Kazu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199704281449.XAA16419>