Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
Fluid [EMAIL PROTECTED] wrote: How about signal 4? I was rebuilding my -current the other day and I kept getting mostly signal 4 errors (in different places) with a couple of signal 10's and 11's. I tried finding a run-down of what the various errors meant, but I couldn't find a thing. The signal number mapping is in /usr/include/sys/signal.h. [ Um, if you don't know what the signals mean, you might not want to be running -current. ] SIGILL (signal 4) is usually not good (e.g., bad RAM, IDE data corruption, etc.). The weird thing is that when I switched terminals in KDE (i.e. opened a new Konsole window), my build problems ceased. Possible bad RAM: the new window allocated enough memory such that a bad spot in memory was allocated to the new Konsole's process, and not randomly to the build processes. Windows XP runs on the same box with no problems (i.e. will run for weeks without a reboot) so I'm a little hesitant to blame my hardware. This doesn't necessarily mean much. Windows will either not stress the hardware as much, or will use RAM in different ways. I seem to recall hearing rumors that Windows allocates memory from the top down. If so, and if FreeBSD allocates memory from the bottom up (I don't know), that could explain why you do not appear to be seeing the problem under xp. However, as other people are having mysterious problems with -current, it could be a software problem. -- Darryl Okahata [EMAIL PROTECTED] DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
On Tue, Apr 30, 2002 at 06:24:14PM -0400, Forrest Aldrich wrote: I've experienced this same problem today; but only after installing 5.0-current on the system in question. It compiled fine with FreeBSD_4.5. This is a 1.2ghz Pentium with 1gb of RAM. No problems with other things (large compile projects with 4.5 before). I have been building XFree86 without problems, until I updated my -CURRENT system (I did the previous update three months ago). I don't think that this is a hardware related problem. My -CURRENT system is running on an 800 MHz Duron (KT133 chipset), and performs flawlessly otherwise, including large builds such as make worlds. The kernel has all debugging options removed, and the malloc.conf options are aj. -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
On Wed, 1 May 2002 13:32:35 +0200, Jose M. Alcaide [EMAIL PROTECTED] said: I have been building XFree86 without problems, I just rebuilt both -current (Friday or Saturday timeframe) and all of X (last night) without a problem. (Well, other than all of the old binaries I need to recompile now...) -GAWollman To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
On Tue, 2002-04-30 at 10:35, Ian wrote: cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 I have seen cc1 die like this many many times, and have only ever seen 2 root causes for the death: 1) bad ram 2) you overclocked the cpu or bus just a bit too much How about signal 4? I was rebuilding my -current the other day and I kept getting mostly signal 4 errors (in different places) with a couple of signal 10's and 11's. I tried finding a run-down of what the various errors meant, but I couldn't find a thing. The weird thing is that when I switched terminals in KDE (i.e. opened a new Konsole window), my build problems ceased. Windows XP runs on the same box with no problems (i.e. will run for weeks without a reboot) so I'm a little hesitant to blame my hardware. -Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
On Tue, Apr 30, 2002 at 11:28:48AM +0200, Jose M. Alcaide wrote: cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 This cc1 SIGBUS is triggered by different source files at different times. But it happens while building XFree86-Server sooner or later, and always with SIGBUS. I did not have problems building the rest of the XFree86-4 ports, or making the world, neither. I commented out CFLAGS (and also CPUTYPE) from /etc/make.conf, but it seems that the XFree86 build system uses -O -pipe anyway. More info: removing -O and/or -pipe from CFLAGS does not improve the situation: cc1 keeps crashing at random places with SIGBUS while building XFree86-Server-4.2.0_2. I found a message from Kris Kennaway telling that this is a widely experienced problem: http://www.freebsd.org/cgi/getmsg.cgi?fetch=1049089+1051787+/usr/local/www/db/text/2002/freebsd-current/20020310.freebsd-current However, disabling optimizations does not work for me. -- ** Jose M. Alcaide // [EMAIL PROTECTED] // [EMAIL PROTECTED] ** ** Beware of Programmers who carry screwdrivers -- Leonard Brandwein ** To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
From: Jose M. Alcaide [EMAIL PROTECTED] Date: Tue, 30 Apr 2002 11:28:48 +0200 To: [EMAIL PROTECTED] Subject: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 I am getting this error while building XFree86-Server-4.2.0_2 on a recently updated -CURRENT (Mon Apr 29 10:55:43 GMT): [snip] cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 I have seen cc1 die like this many many times, and have only ever seen 2 root causes for the death: 1) bad ram 2) you overclocked the cpu or bus just a bit too much cc1 dying on a long complex source module when you've overclocked beyond what your silicon can handle is so reliable a test that it's the first thing I use when trying to find the true speed a new system will run at. If you're not overclocking, then bad ram would make a good second suspect, I had a failing DIMM a couple years ago first manifest as signal 10 and 11 errors in cc1. -- Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
I've experienced this same problem today; but only after installing 5.0-current on the system in question. It compiled fine with FreeBSD_4.5. This is a 1.2ghz Pentium with 1gb of RAM. No problems with other things (large compile projects with 4.5 before). _F From: Jose M. Alcaide [EMAIL PROTECTED] Date: Tue, 30 Apr 2002 11:28:48 +0200 To: [EMAIL PROTECTED] Subject: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 I am getting this error while building XFree86-Server-4.2.0_2 on a recently updated -CURRENT (Mon Apr 29 10:55:43 GMT): [snip] cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got fatal signal 10 I have seen cc1 die like this many many times, and have only ever seen 2 root causes for the death: 1) bad ram 2) you overclocked the cpu or bus just a bit too much cc1 dying on a long complex source module when you've overclocked beyond what your silicon can handle is so reliable a test that it's the first thing I use when trying to find the true speed a new system will run at. If you're not overclocking, then bad ram would make a good second suspect, I had a failing DIMM a couple years ago first manifest as signal 10 and 11 errors in cc1. -- Ian To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
Found that cc1 also has a problem with this on a buildworld for FreeBSD-5.0-CURRENT. FYI. I can reinstall 4.5 and attempt the same, but I recall no problems with 4.5. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2
To follow up on my previous post: I did reinstall FreeBSD-4.5 (updated with cvsup), did a buildworld etc., then build XFree86-4 with no troubles at all. So looks like the problem may be with FreeBSD-5.0-CURRENT. _F To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
