Date: Sat, 11 Jul 1998 09:10:01 -0700 (PDT) From: Peter Cornelius <pc@akk.uni-karlsruhe.de> To: freebsd-bugs@FreeBSD.ORG Subject: Re: misc/6992: 'cc: Internal compiler error: program as got fatal signal 11' when making world Message-ID: <199807111610.JAA28024@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR misc/6992; it has been noted by GNATS. From: Peter Cornelius <pc@akk.uni-karlsruhe.de> To: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE>, jkh@FreeBSD.ORG Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: misc/6992: 'cc: Internal compiler error: program as got fatal signal 11' when making world Date: Sat, 11 Jul 1998 18:02:58 +0200 Hello again, thanks for the replies, and please excuse for the delay, I had to recover from a moderate earth quake 8-S On Fri, Jun 19, 1998 at 02:54:55PM +0200, Christoph Kukulies wrote: > 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 :-) On Fri, Jun 19, 1998 at 07:53:02 -0700, Jordan K. Hubbard wrote: > State-Changed-From-To: open-closed > State-Changed-By: jkh > State-Changed-When: Fri Jun 19 16:52:09 MEST 1998 > State-Changed-Why: > This is indicative of a hardware failure, not an OS problem. > Verify that your cache is good, your ram speed settings and > voltages are correct, etc. Well... As Jordan Hubbard told me, I verified. And after a "quick last reboot" the earth seemed to have shifted (at least for my computer). I not really recently, but more or less, acquired 64 MB of additional ram that was in there for a short while with little problems (a couple of minor X crashes, gimp and such), but no real probs until make world. The tricky bit was that the former 32 MB stayed in the same machine, so it seemed to "work". I swapped banks, no "real" probs, I stuck the "new" ram into an nt box, all seemed fine (as in Christph's case). Also, the "new" rams are part of a charge of six in total all the others of which work fine. But in all cases, never the "new" rams were on their own. Then I removed my old ram (should there be a memory limit for that motherboard ???), and after a couple of seconds I was in for a couple of days of root partition repair (who the fffflame put that tape on top of the monitor, anyways?? I told you.). With some hot air, the modules flew back to where they came from, and after some ten days or so, I received a couple of new ones with no comment (...) Now, my world survives. (...) Thanks again for your help & patience, 'til the next "bug", Peter. --- Peter Cornelius <pc@akk.uni-karlsruhe.de> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807111610.JAA28024>