From owner-freebsd-bugs Fri Jun 19 06:01:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07061 for freebsd-bugs-outgoing; Fri, 19 Jun 1998 06:01:51 -0700 (PDT) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06984 for ; Fri, 19 Jun 1998 06:01:21 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.8.8/8.8.5) id GAA19500; Fri, 19 Jun 1998 06:00:03 -0700 (PDT) Date: Fri, 19 Jun 1998 06:00:03 -0700 (PDT) Message-Id: <199806191300.GAA19500@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.ORG From: Christoph Kukulies Subject: Re: misc/6992: 'cc: Internal compiler error: program as got fatal signal 11' when making world Reply-To: Christoph Kukulies Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR misc/6992; it has been noted by GNATS. From: Christoph Kukulies To: Peter Cornelius Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: misc/6992: 'cc: Internal compiler error: program as got fatal signal 11' when making world Date: Fri, 19 Jun 1998 14:54:55 +0200 On Fri, Jun 19, 1998 at 12:40:16PM +0200, Peter Cornelius wrote: > > >Number: 6992 > >Category: misc > >Synopsis: 'cc: Internal compiler error: program as got fatal signal 11' when making world > >Confidential: no > >Severity: serious > >Priority: medium > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Fri Jun 19 03:40:02 PDT 1998 > >Last-Modified: > >Originator: Peter Cornelius > >Organization: > Arbeitskreis Kultur und Kommunikation, Universitaet Karlsruhe > >Release: FreeBSD 2.2.6-STABLE i386 (RELENG_2_2) > >Environment: > > This is going to be large. Please excuse. > > Main board is an Iwill (http://www.iwill.com.tw/) P54TS w/ P133, AIC7850 > and 96 MB RAM. > > petra:~# uname -a > uname.kernel.980408 > FreeBSD petra.cornelius.org 2.2.5-RELEASE FreeBSD 2.2.5-RELEASE #0: Sun Mar 29 2 > 3:56:20 CEST 1998 root@petra.cornelius.org:/usr/src/sys/compile/PETRA i386 > > but also with 2.2.6-STABLE kernel. I am up to date with RELENG_2_2 src until > last night (June 18th, 18.30 UTC) and have the last world made roughly > a fortnight ago. [...] > petra:/usr/src# make world 2>&1 | tee ~/makeworld.log ; date >> ~/makeworld.log > -------------------------------------------------------------- > make world started on Thu Jun 18 20:54:26 CEST 1998 > -------------------------------------------------------------- > cd /usr/src && make buildworld > > -------------------------------------------------------------- > Cleaning up the temporary build tree > -------------------------------------------------------------- > > ( *** a LOT of output *** ) > > cc -fpic -DPIC -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DYP -I/usr/obj/usr/src/tmp/usr/include -I/usr/src/lib/libc/i386 -c /usr/src/lib/libc/../libc/i386/gen/fabs.S -o fabs.so > fatal process exception: page fault, fault VA = 0x8179fee > cc: Internal compiler error: program as got fatal signal 11 > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > Thu 18 Jun 21:30:02 CEST 1998 > > However, the computer runs for days with little load and also prints rather > large documents (pix, faxes, ps files) running Net's Crap under X the same > time with no obvious problem. So I *think* it's not a memory problem, > although under the second kernel, the error is slightly different suggesting > a complaint to the g++ or gcc developers group. But I suspect that it > not really might be a problem of make world or gcc but a symptom for > something else. > > I do experience some very unspecific errors with the second, newer kernel, > that I hoped to be fixed with a source update, but now it seems > to have broken my world 8-S. There were sudden deaths of X (with sig 6) > and also deadlocks (freezeing) of the whole machine, but I can't tell for > now since I have no evidence (other than the frozen computer). I also > tried to build a kernel for another machine (486) to see whether the frozen > box still responds to the ethernet, but I had no success so far, either. > That was in order to see if there's a relation to prs 6873 and 6914. Just FYI - your problem may be different - I once had a hell of a time getting a system to get through a make world although it ran continously with light load for days w/o problems. It was a newly bought system and I brought it back to the local computer store where I bought it. I proved them that it was memory that was causing the world build process to fail. I connected a similar system to the disks and ran make world fine in a couple of hours. Then we connected the same disk(s) back to the faulty system and the problems where there again. The vendor finally swapped all (64MB that were) memory and it worked. It's hard to convince a computer dealer that hist hardware is faulty when he says "look here, NT runs just fine on it". make world is a hardware burn in process which hardware vendors should make to their duty :-) > > > >How-To-Repeat: > > Make the world. > > > >Fix: > I, unfortunately, have no idea. > > > >Audit-Trail: > >Unformatted: > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-bugs" in the body of the message -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message