Date: Sun, 23 Apr 2006 11:27:49 -0700 From: Garrett Cooper <youshi10@u.washington.edu> To: freebsd-questions@freebsd.org Subject: Re: Same error with all ports install! Message-ID: <444BC725.5050403@u.washington.edu> In-Reply-To: <BAY20-F1384F2A2658790329358DD9AB90@phx.gbl> References: <BAY20-F1384F2A2658790329358DD9AB90@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
Marwan Sultan wrote: > > > Hello Bill, Hello Garrett, > > First I would like to thank you for the support and time you are giving > me and to everyone. > > Yes I ran memtest86 from a bootable cd on the two DDR chipsets and > after like 10+ hours > It found 3 errors! is it reasnable? > > Anyhow I replaced the two DDR with diffrent 1 256 DDR chipset and it > start to give the error I > wrote in my email. > But I didnot run the memtest86 on the new RAM (well it not brand new) i > had it somewhere. > I will run the memtest86 on the new installed ram, and let you know. > > Thank you again. > Marwan. >> >> >> I want to direct the focus in the correct direction on this. >> >> Based on your described symptions, bad RAM is the _most_ likely >> cause. There >> are other things that could cause it, however. >> >> So _before_you_do_anything_else_, run memtest86. I recommend the >> standalone >> boot-from-CD version, as it's more thorough in its testing. Let it >> run for >> at least _8_ hours (or until you see errors). Any errors from >> memtest86 are >> bad. Even just a few errors per hour is unacceptable. >> >> If memtest86 produces errors, you can then start experimenting with >> different >> chips in different slots. After each change, use _memtest86_ to see >> if the >> problem is solved. I don't recommend using port compiles to test your >> RAM, >> it's not a reliable approach. >> >> Also, read the docs on memtest86. There's a lot of good advice on >> finding >> RAM problems. >> >> Garrett Cooper <youshi10@u.washington.edu> wrote: >> > Marwan, >> > >> > Did you run memtest86+? That is the true tell-tale sign that >> > something RAM-related does or does not work. >> > >> > You may also have a bad slot on your motherboard, so moving the RAM >> > around to try and get it to work is a good way to troubleshoot your >> > given issue in compiling things. >> > If you do move the RAM chip, make sure to firmly place it in its >> > destination slot. If you don't your computer will report errors with >> > the RAM chip, which are erroneous to the problem that you currently >> > have. >> > >> > HTH, >> > -Garrett >> > >> > On Apr 23, 2006, at 7:58 AM, Marwan Sultan wrote: >> > >> > > Hello there, >> > > >> > > Sorry for disturb, >> > > >> > > I have changed the RAM to diffrent 256 1 chipset DDR. >> > > and now, whenever I compile any port the following error shows, >> > > >> > > cc: Internal error: Segmentation fault: 11 (program as) >> > > Please submit a full bug report. >> > > See <URL:http://gcc.gnu.org/bugs.html>; for instructions. >> > > *** Error code 1 >> > > >> > > For whatever port! >> > > Any Advise? is it a PC problem? not BSD? >> > > >> > > Marwan >> > > >> > >> Marwan Sultan wrote: >> > >>> >> > >>> Its 2 chipset RAM, each 256DDR total 512 >> > >>> Running on Dell Optiplex Gx260. P4 2.5 >> > >>> >> > >>> Do you think ram has something wrong! ? it should be like one ram >> > >>> chipset? has the problem? >> > >>> I'll try them one at a time, >> > >>> >> > >>> Thanks for the advise, >> > >>> >> > >>> Thanks kevin, thanks Garrett >> > >>> >> > >>>> Marwan Sultan wrote: >> > >>>> >> > >>>>> Hello Guys, >> > >>>>> >> > >>>>> I fresh installed FreeBSD 6.0R some wierd stuff going on! >> > >>>>> Firts: the box restarted from it self like 4 times, and >> > >>>>> /var/log/messages showing only one strange >> > >>>>> line (for me) which is >> > >>>>> Apr 22 01:10:46 box kernel: pid 5764 (cc1), >> > >>>>> uid 0: exited on signal 6 (core >> > >>>>> dumped) >> > >>>>> >> > >>>>> then i ran fsck, it cleared some files, now its not >> > >>>>> restarting but, i'm not sure it will or it will not. >> > >>>>> >> > >>>>> second problem: whenever i try to install any port, >> > >>>>> it gave an error msg during the make says: >> > >>>>> >> > >>>>> cc1 in free(): error: junk pointer, too high to make sense >> > >>>>> cc1 in malloc(): error: recursive call >> > >>>>> cc: Internal error: Abort trap: 6 (program cc1) >> > >>>>> Please submit a full bug report. >> > >>>>> See <URL:http://gcc.gnu.org/bugs.html>; for instructions. >> > >>>>> *** Error code 1 >> > >>>>> >> > >>>>> >> > >>>>> Anyone could Advise please? >> > >>>>> Marwan >> > >>>> >> > >>>> >> > >>>> How many RAM chips? Try them one at a time... >> > >>>> >> > >>>> KDK >> > >> >> > >> Another thing: Check the capacitors on your motherboard. If >> > >> they the tops are swelling (tops are not flat) or bursting >> > >> (emitting yellow/orange dialectric) on the capacitors around the >> > >> RAM/CPU, it's time to either call Dell or get a new machine. The >> > >> fault with bad capacitors is a well known quality control problem >> > >> and if you search google for those terms, maybe you can get some >> > >> more information as to what it is and why it occurs. >> > >> -Garrett >> > > >> > >> > _______________________________________________ >> > freebsd-questions@freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> > To unsubscribe, send any mail to >> "freebsd-questions-unsubscribe@freebsd.org" >> > >> > * >> > >> > >> > >> > >> > >> ************************************************************************************ >> >> > This footnote confirms that this email message has been scanned by >> > PineApp Mail-SeCure for the presence of malicious code, vandals & >> computer viruses. >> > >> ************************************************************************************ >> >> > >> > >> >> >> -- >> Bill Moran >> Potential Technologies >> http://www.potentialtech.com What I would do next is take a look in the system event log in your BIOS and see if there are any logs about bad RAM access. Next, I would grab your Dell Resource CD and run the memory tests to see if it may be the bus or the RAM itself failing. Finally, I would swap around the RAM if nothing is conclusive and rerun memtest86+ just to make sure that your problem isn't a bad DIMM slot. If the memory test shows the same sections (or similar sections), failing with a different RAM chip on the same slot, the slot is bad. If the problems migrate with the RAM, the RAM is bad. HTH, -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?444BC725.5050403>