From owner-freebsd-questions Sun May 26 15:40:19 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA29197 for questions-outgoing; Sun, 26 May 1996 15:40:19 -0700 (PDT) Received: from iectech.com (netgate.iectech.com [198.136.226.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA29179 for ; Sun, 26 May 1996 15:40:13 -0700 (PDT) Received: by netgate.iectech.com id <6159>; Sun, 26 May 1996 14:39:48 -0400 From: Chris Peltier To: "'Carey Nairn'" Cc: "'freebsd-questions@freebsd.org'" Subject: RE: Arrg!! sig 11 Date: Sun, 26 May 1996 18:32:19 -0400 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.12.736 Encoding: 45 TEXT Message-Id: <96May26.143948edt.6159@netgate.iectech.com> Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >On Sat, 25 May 1996, Nate Williams wrote: > >> > > > Signal 11's are really getting on my nerves! I'm starting to >> > > > wish I didn't upgrade to 2.1r.. >> > > >> > > I *highly* suspect hardware failure, which didn't get tickled by 2.0 >for >> > > reasons of usage or whatever. >> ... >> > > >> > > > cd to?? I used /usr/local/bin >> > > > man -a * |& col -b > /tmp/junk.test >> > >> > Because I was doing nothing else important I decided to give this a try > >> > as well... I got a seg fault. I have also been noticing some other >> > strange behaviour on my home machine when compiling.. things failing >with >> > bus errors or seg faults that work fine when I do the same compile on >my >> > work machine... the only difference between the two is really the way >> > FreeBSD was installed. The home machine was installed over 2.0.5 as an > >> > upgrade and the work machine was installed as a clean 2.1 install. >> > Could this be a cause of these random errors, or do I maybe have some >> > dodgy hardware in the home machine ? >> >> I suspect dodgy hardware. It shouldn't matter if the upgrade was done >> (assuming the upgrade was done correctly ala. 'make world'). If the >> latter was done, then *all* the system binaries except the kernel were >> updated, and I assumed you also upgraded the kernel. I have seen the same compiling problems on 2.1.0 release with similar hardware on several identical machines. These machine were Pentium 100s with an ECS Triton 1 chipset motherboard, 16mb RAM, Diamond S3 PCI video, DE100 PCI NIC. The compiles generated signal 11 at some arbitrary point. The user/process environment was trashed after that. I could restart the operation under a different process and it would it would finish (or maybe crash again). Everything else >seems OK. > > >