Consistant buildworld Segmentation fault at '===> gnu/usr.bin/cc/cpp' after latest RELENG_5 cvsup

[Doug White]

On Mar 9, 2005, at 6:36 AM, Aaron Daubman wrote:

> Hi all,
>
> I'm an oldtime FreeBSD user but am new to the amd64 world.  I'm trying
> to put one of my Sunfire V20z single proc Opteron w/2G RAM servers to
> better use (previously ran Win2k3) and am having some difficulty
> updating it.

[...]
> makeinfo -I /usr/src/gnu/usr.bin/cc/doc/../../../../contrib/gcc/doc -I
> /usr/src/gnu/usr.bin/cc/doc/../../../../contrib/gcc/doc/include
> --no-split -I /usr/src/gnu/usr.bin/cc/doc -I
> /usr/src/gnu/usr.bin/cc/doc
> /usr/src/gnu/usr.bin/cc/doc/../../../../contrib/gcc/doc/ 
> cppinternals.texi
>  -o cppinternals.info
> gzip -cn cppinternals.info > cppinternals.info.gz
> ===> gnu/usr.bin/cc/cpp
> Segmentation fault (core dumped)
> *** Error code 139
[...]

The typical reason for segfaults is bad hardware.  A v20z is a pretty  
decent server class machine, though, so unless its suffering from an  
undetected condition it should scream bloody murder if something goes  
bad. This is assuming it has ECC memory and you aren't ignoring that  
big yellow "maintenance" light that comes on when something bad  
happens, like a fan going down.

Can you get into the LOM and check the environmentals?

--
Doug White                    |  FreeBSD: The Power to Serve
dwhite at gumbysoft.com          |  www.FreeBSD.org