Date: Tue, 19 Dec 1995 06:24:40 -0800 From: David Greenman <davidg@Root.COM> To: "Jordan K. Hubbard" <jkh@time.cdrom.com> Cc: asami@cs.berkeley.edu (Satoshi Asami), stable@freebsd.org Subject: Re: program cc1 got fatal signal 11 Message-ID: <199512191424.GAA00214@corbin.Root.COM> In-Reply-To: Your message of "Tue, 19 Dec 95 05:49:00 PST." <17790.819380940@time.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>> I've seen cc1 occasionally die with signals (usually 11, but I've seen >> 6 and 10 before too) on a 2.1R machine recently. Although I suspected >> hardware problems, as it disappeared when I disabled the internal > >I have this happen too, though nowhere near as often as you seem to! > >It stops about one in three `make worlds' in their tracks, and always >during a large C compile - typically one in libg++ or groff someplace. >It's cc1 that, furthermore, is always the one croaking! When run a >second time, it always makes it through. Go figure! > >Also FYI: This did *not* happen until I went from a 90Mhz part to a >133Mhz part in my ASUS P55TP4-XE MB. Yes, my memory is 60ns. Using >256K pipeline burst module. I thought you told me that the problem went away once you figured out the correct voltage setting for the CPU?? -DG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512191424.GAA00214>