From owner-freebsd-current Thu May 2 8:40:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from msgbas1.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by hub.freebsd.org (Postfix) with ESMTP id 5DAD337B41A for ; Thu, 2 May 2002 08:40:43 -0700 (PDT) Received: from msgrel1.cos.agilent.com (msgrel1.cos.agilent.com [130.29.152.77]) by msgbas1.cos.agilent.com (Postfix) with ESMTP id EA516BD9B; Thu, 2 May 2002 09:40:42 -0600 (MDT) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by msgrel1.cos.agilent.com (Postfix) with ESMTP id 42F5511B; Thu, 2 May 2002 09:40:42 -0600 (MDT) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_22672)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id IAA18640; Thu, 2 May 2002 08:40:41 -0700 (PDT) Message-Id: <200205021540.IAA18640@mina.soco.agilent.com> To: sreese@codysbooks.com Cc: freebsd-current Subject: Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 Reply-To: Darryl Okahata In-Reply-To: Your message of "01 May 2002 12:52:51 PDT." <1020282771.29023.17.camel@borges.codysbooks.com> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Thu, 02 May 2002 08:40:40 -0700 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Fluid 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 darrylo@soco.agilent.com 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message