Date: Tue, 27 May 2008 03:45:55 -0700 From: Jeremy Chadwick <koitsu@FreeBSD.org> To: cy@htlwrn.ac.at Cc: freebsd-ports@FreeBSD.org Subject: Re: Compiler segfault under fbsd7? Message-ID: <20080527104555.GA38717@eos.sc1.parodius.com> In-Reply-To: <20080527123805.ywfk7hs9yiog04ww@webmail.htlwrn.ac.at> References: <20080527105703.yi5jjfb64kow8k8s@webmail.htlwrn.ac.at> <20080527090825.GA35576@eos.sc1.parodius.com> <20080527123805.ywfk7hs9yiog04ww@webmail.htlwrn.ac.at>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, May 27, 2008 at 12:38:05PM +0200, cy@htlwrn.ac.at wrote: > You are right: make buildworld exits with > > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/genattrtab.c: In > function 'make_internal_attr': > /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/genattrtab.c:4240: > internal compiler error: Segmentation fault: 11 You have CPU, motherboard, or memory problems. My vote is on memory. You can download memtest86 or memtest86+ (burn either to a CD via ISO, or put them on a floppy and boot them) and let it run for a while. You will probably see errors there within a few minutes. > So it's some hardware than (could it be an old BIOS). Possible, but doubtful. > Or could it be the HD, fdisk gives: > > ******* Working on device /dev/ad0 ******* > parameters extracted from in-core disklabel are: > cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=155061 heads=16 sectors/track=63 (1008 blks/cyl) > > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) > start 63, size 156296322 (76316 Meg), flag 80 (active) > beg: cyl 0/ head 1/ sector 1; > end: cyl 1023/ head 254/ sector 63 > > I tried to fix this with fdisk to the correct 1024/255/63 but the upper > part of the output stays always the same ... I don't see anything wrong with the fdisk output. gcc is segfaulting. This is very likely going to happen as a result of bad memory, not as a result of a bad disk. You'd be having many other problems (not sig11; I'm talking random I/O errors or the system locking up hard) if you had a bad disk. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080527104555.GA38717>