From owner-freebsd-stable Fri Jan 5 11: 3:35 2001 From owner-freebsd-stable@FreeBSD.ORG Fri Jan 5 11:03:31 2001 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from smtp.hccnet.nl (smtp.hccnet.nl [193.172.127.93]) by hub.freebsd.org (Postfix) with ESMTP id EA30737B402 for ; Fri, 5 Jan 2001 11:03:30 -0800 (PST) Received: from parmenides.utp.net by smtp.hccnet.nl via uds82-123.dial.hccnet.nl [193.173.123.82] with ESMTP id UAA20503 (8.8.5/1.13); Fri, 5 Jan 2001 20:03:25 +0100 (MET) Received: by parmenides.utp.net (Postfix, from userid 1005) id 3D84914D; Fri, 5 Jan 2001 20:02:23 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by parmenides.utp.net (Postfix) with ESMTP id EEBCF12E; Fri, 5 Jan 2001 20:02:22 +0100 (CET) Date: Fri, 5 Jan 2001 20:02:22 +0100 (CET) From: Janko van Roosmalen To: Keith Jones Cc: Janko van Roosmalen , Odhiambo Washington , FBSD-STABLE Subject: Re: 4.2-STABLE build fails In-Reply-To: <20010105151843.A6570@moose.bri.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 5 Jan 2001, Keith Jones wrote: > On Fri, Jan 05, 2001 at 03:04:55PM +0100, Janko van Roosmalen wrote: > > > > I've seen much of this discussed here but mine seems to break at this > > > point: > > > > > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > > > > > ..and with this msg on the console... > > > > > > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited on > > > signal 11 (core dumped) > > > Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited on > > > signal 11 (core dumped) > > > > > > > > > Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not help. > > > Any pointer what this 13.viref thing is and how I can sort that out will > > > be highly appreciated. > > > > The FreeBSD faq mentions that signal 11 points to hardware problems. > > Could people please STOP spreading this myth that all Signal 11's during > 'make world' are a result of hardware problems. It is highly misleading. How > would you feel if you acted on this advice and shelled out your hard-earned > cash for new hardware only to find that it was a software problem after all? > > The chances are that if a signal occurs as the result of running a particular > program (in this case 'troff'), it's likely to be the version of that program > or a shared library on which it depends that is broken somehow on the user's > machine, not the user's hardware. > > You could try manually recompiling and installing 'troff' et al. (located > in the directory /usr/src/contrib/groff) then rerunning 'make world'. > -- > Keith Jones > E-Business Service Introduction, GBIT-EMEA (Bristol) > E: keith_jones@non.hp.com > T: [+44 117] 312-7602 > > I don't speak for Hewlett-Packard. I think the faq is rather balanced regarding this and points to slow memory, and recommends adapting memory timings in the BIOS. It could be the temperature. Odhiambo lives in Kenia. It is summer there. Recompiling your system in those climatic conditions is the equivalent of a burn-in test. I remember a post from someone who reported a hefty increase increase of the CPU temperature while building world. Many computer "hardware" problems can be fixed by just refitting cables, checking if they have sharp bends, pressing chips in sockets or cleaning card contacts with a pencil eraser if you do not have a contact enhancing spray. Another source can be power. There could have been a surge or sag. Years ago I worked as a temp in a shop where they anodized and welded aluminium. They had some weird problems with their Apple II which were solved by using an UPS. Notwithstanding this, you still have a point. Maybe time to adjust the FAQ?. I am not a native speaker so I have an excuse to not volunteer ;) ===Janko van Roosmalen - Vught - Netherlands=== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message