Date: Sat, 25 May 1996 20:39:07 -0600 From: Nate Williams <nate@sri.MT.net> To: Carey Nairn <cp_nairn@cc.utas.edu.au> Cc: Nate Williams <nate@sri.MT.net>, tcg@ime.net, freebsd-questions <questions@FreeBSD.ORG> Subject: Re: Arrg!! sig 11 Message-ID: <199605260239.UAA22775@rocky.sri.MT.net> In-Reply-To: <Pine.SOL.3.91.960526123139.26238B-100000@wedge.its.utas.edu.au> References: <199605251906.NAA22158@rocky.sri.MT.net> <Pine.SOL.3.91.960526123139.26238B-100000@wedge.its.utas.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > 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. Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199605260239.UAA22775>