Date: Fri, 21 Feb 1997 21:51:01 -0800 From: Craig Shaver <craig@ProGroup.com> To: "James G. Speth" <speth@scruz.net> Cc: hardware@freebsd.org, speth@nic.scruz.net, matthew@nic.scruz.net Subject: Re: problem with 2.1.7-RELEASE #0 Message-ID: <330E8945.773C2448@ProGroup.com> References: <199702220427.UAA14952@scruz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
James G. Speth wrote: > > I installed FreeBSD release 2.1.7 yesterday, and I've been dealing with some > very strange errors since then. del .... > the install is complete things get really weird. When I attempt to compile > some software that compiles cleanly under an identical system running > FreeBSD 2.1.0-RELEASE #4, I get sporadic internal compiler errors. Every > now and then it will compile cleanly with no errors, but the rest of the > time it gives me errors like these: > > cc -g -c billing.c > assertion "fragP->fr_offset >= 0" failed: file "/usr/src/gnu/usr.bin/as/write.c" > , line 529 > cc: Internal compiler error: program as got fatal signal 6 > *** Error code 1 hmmmmm, yes, I have seen this before .... > > cc -g -c billing.c > cc: Internal compiler error: program cc1 got fatal signal 11 > *** Error code 1 and this .... > > cc -g -c utils.c > /var/tmp/cc000363.s: Assembler messages: > /var/tmp/cc000363.s:6893: Fatal error:Case value 23199812 unexpected at line 380 > of file "/usr/src/gnu/usr.bin/as/write.c" Haven't seen this one -- yet ... > > cc -g -c billing.c > billing.c: In function `undo': > billing.c:3880: internal error--unrecognizable insn: > (jump_insn 155 153 156 (set (pc) > (UnKnown Unknown)) -1 (nil) > (nil)) > cc: Internal compiler error: program cc1 got fatal signal 6 > *** Error code 1 Yup .... > > It is very inconsistent, giving different error messages on different > attempts, and sometimes giving no error at all. That is what makes me think > it is related to the earlier disk problems, or perhaps something in the > caching code. > > Have you seen problems like this, or heard any other reports of problems with > this release? Any help you can give me would be appreciated. > > Thanks. > > -- > Jim Speth > scruz-net engineering I don't think it is anything wrong with FreeBSD 2.1.7. I just built a new machine for Solaris 2.5.1 x86. It is a Tyan Tomcat III dual pentium. I got the p5-150's and overclocked them by using a 3X ratio on a memory bus speed of 66mhz. No problems with the cpus, but I also got 4 pieces of 32mb edo (128MB). The chips were from TI, and I could not run them at 60ns with aggressive settings in the bios for ram related timings. So I took them back and got Mu chips. They worked great at 60ns with default timings, but not at aggressive timings. When I first built the box I tested it by doing simultaneous compiles of several versions of gcc, gdb, perl, etc. With the TI chips at 60ns settings I got the same kind of errors you did. If I set the bios for the 70ns defaults, I did not get the errors. I also swapped in some other memory I had, and the problems disappeared -- at 60ns timing. So, if you have some other memory available, try swapping it around. Try setting your bios to very conservative settings. Disable the cache. etc, etc, .... -- Craig Shaver (craig@progroup.com) (415)390-0654 Productivity Group POB 60458 Sunnyvale, CA 94088
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?330E8945.773C2448>