Date: Wed, 15 Sep 1999 16:28:43 -0700 (PDT) From: jin@george.lbl.gov To: freebsd-bugs@FreeBSD.ORG, tcole@balsam.methow.com Cc: des@flood.ping.uio.no, ru@ucb.crimea.ua Subject: Re: kern/13739: FreeBSD 3.3-RC panics durring make world Message-ID: <199909152328.QAA08457@george.lbl.gov>
next in thread | raw e-mail | index | archive | help
tcole@balsam.methow.com wrote: > > > > > Also I don't get a panic every time. Sometimes I just get a lot of > > > error, as if the code was broken and wouldn't compile, but always in > > > different places. > > > > > Examples, examples! > > Ok, here are some I got today: > > cd /usr/src/lib/libtermcap; /usr/obj/usr/src/tmp/usr/bin/make all; /usr/obj/usr/ > src/tmp/usr/bin/make -B install > cc -O -pipe -DCM_N -DCM_GT -DCM_B -DCM_D -I/usr/src/lib/libtermcap -I/usr/obj/us > r/src/tmp/usr/include -c /usr/src/lib/libtermcap/termcap.c -o termcap.o > cc -O -pipe -DCM_N -DCM_GT -DCM_B -DCM_D -I/usr/src/lib/libtermcap -I/usr/obj/us > r/src/tmp/usr/include -c /usr/src/lib/libtermcap/tgoto.c -o tgoto.o > stdin:1: parse error at null character > /usr/src/lib/libtermcap/tgoto.c: In function `tgoto': > /usr/src/lib/libtermcap/tgoto.c:103: parse error at null character > *** Error code 1 > > And after a `make clean` I did another `make buildworld` and got: > > cc -pg -O -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/usr/src/tmp/usr/inclu Now, please look the line 103 in file /usr/src/lib/libtermcap/tgoto.c , if that sentence is OK (no corrupted ASCII), then it is your hardware problem. Either you overclocked CPU or you have a bad memory chip. Please check them. If you could not figure out what is the problem, please send your hardware configuration -- inlcuding the overclock if you do. I did see a corrupted file during the installation, but it rarely happens. Some one explained to me that a universal particle was intruding in my system during the installation. I got a constant error at that place. Yous did not seem in this case, because you had random failure, so it is memory problem in either your memory chip or the CPU cache if you over clock your CPU. > t panics or lots and lots > > > of errors. Could those be caused by hardware problems? > > > > > Sure! Maybe your CPU is overlocked? > > Not overclocked. Probably my RAM :( But this RAM has been working > with out a problem for 2 years. > > -- > --Travis > > When it comes to violence, morality and the young, we're the Idiot Nation, > the laughingstock not only of the civilized world but of the highly-wired > generation of kids we're supposedly trying to protect. > Jon Katz 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?199909152328.QAA08457>