buildworld failures on STABLE

2007-10-07 Thread Per olof Ljungmark
On a remote machine currently with RELENG-6 from 20th. June, with STABLE 
sources from this morning I get build failures in contrib/ similar to:


cc -O2 -fno-strict-aliasing -pipe -DIN_GCC -DHAVE_CONFIG_H 
-DPREFIX=\/usr/obj/usr/src/tmp/usr\ 
-I/usr/obj/usr/src/tmp/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cc_int/../cc_tools 
-I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc 
-I/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/config 
-DHAVE_CONFIG_H -DTARGET_NAME=\i386-undermydesk-freebsd\ -DIN_GCC 
-I/usr/obj/usr/src/tmp/legacy/usr/include -c 
/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c
/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c: In 
function `pre_edge_rev_lcm':
/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c:801: 
internal compiler error: Segmentation fault: 11

Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://gcc.gnu.org/bugs.html for instructions.
*** Error code 1

Would this indicate a hardware (memory) problem? Any way to test remotely?

Thanks.

Per olof
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: buildworld failures on STABLE

2007-10-07 Thread Roland Smith
On Sun, Oct 07, 2007 at 11:01:16AM +0200, Per olof Ljungmark wrote:
 On a remote machine currently with RELENG-6 from 20th. June, with STABLE 
 sources from this morning I get build failures in contrib/ similar to:
snip
 /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c:801: internal 
 compiler error: Segmentation fault: 11
snip
 Would this indicate a hardware (memory) problem? 

Yes. The compiler dying with signal 11 is a typical memory problem.

 Any way to test remotely?

There are memory test applications like memtest86+ (http://www.memtest.org/).
You have to boot from it, but it does support a console on a serial port.

Roland
-- 
R.F.Smith   http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914  B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)


pgpuSDa3WCars.pgp
Description: PGP signature


Re: buildworld failures on STABLE

2007-10-07 Thread Eugene Grosbein
On Sun, Oct 07, 2007 at 11:40:11AM +0200, Roland Smith wrote:

  On a remote machine currently with RELENG-6 from 20th. June, with STABLE 
  sources from this morning I get build failures in contrib/ similar to:
 snip
  /usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c:801: internal 
  compiler error: Segmentation fault: 11
 snip
  Would this indicate a hardware (memory) problem? 
 
 Yes. The compiler dying with signal 11 is a typical memory problem.
 
  Any way to test remotely?
 
 There are memory test applications like memtest86+ (http://www.memtest.org/).
 You have to boot from it, but it does support a console on a serial port.

There is also ports/sysutils/memtest that may be run from multiuser
if one manages to build it with broken memory :-)
Or it's possible to install a package.

One problem with running such application with OS loaded is that
kernel places strict limit to amount of memory that user-level application
may lock. There is a PR with a patch that allows to raise the limit
so memtest could test most part of free memory:

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/114654

Eugene Grosbein
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: buildworld failures on STABLE

2007-10-07 Thread Per olof Ljungmark

Eugene Grosbein wrote:

On Sun, Oct 07, 2007 at 11:40:11AM +0200, Roland Smith wrote:

On a remote machine currently with RELENG-6 from 20th. June, with STABLE 
sources from this morning I get build failures in contrib/ similar to:

snip
/usr/src/gnu/usr.bin/cc/cc_int/../../../../contrib/gcc/lcm.c:801: internal 
compiler error: Segmentation fault: 11

snip
Would this indicate a hardware (memory) problem? 

Yes. The compiler dying with signal 11 is a typical memory problem.


Any way to test remotely?

There are memory test applications like memtest86+ (http://www.memtest.org/).
You have to boot from it, but it does support a console on a serial port.


There is also ports/sysutils/memtest that may be run from multiuser
if one manages to build it with broken memory :-)
Or it's possible to install a package.

One problem with running such application with OS loaded is that
kernel places strict limit to amount of memory that user-level application
may lock. There is a PR with a patch that allows to raise the limit
so memtest could test most part of free memory:

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=kern/114654


Thanks for the memtest advice, I ran it and memory is definitely hosed.
Sigh, that means 400 kilometers of travel...

Per olof
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]