From owner-freebsd-current Tue Nov 25 17:40:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA28478 for current-outgoing; Tue, 25 Nov 1997 17:40:56 -0800 (PST) (envelope-from owner-freebsd-current) Received: from nomis.Simon-Shapiro.ORG (nomis.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA28409 for ; Tue, 25 Nov 1997 17:40:41 -0800 (PST) (envelope-from shimon@nomis.Simon-Shapiro.ORG) Received: (qmail 538 invoked by uid 1000); 26 Nov 1997 01:40:49 -0000 Message-ID: X-Mailer: XFMail 1.2-beta-111797 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199711251516.IAA27098@mt.sri.com> Date: Tue, 25 Nov 1997 17:40:49 -0800 (PST) Reply-To: shimon@simon-shapiro.org Organization: Me, Just me... From: Simon Shapiro To: Nate Williams Subject: Re: Compiler Bug??? Cc: freebsd-current@FreeBSD.ORG, Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 25-Nov-97 Nate Williams wrote: >> > Guess what, you have bad memory! Seriously, this is not a >> > compiler bug, >> > but something in your hardware that is hosed up. Either the >> > memory is >> > bad, the timings are bad, the cache is bad, or some combination of >> > the >> > above is bad. Compiler bugs don't go away on reboots, but >> > corrupted >> > memory does. >> >> ... just to clarify here, as I am reading Simon slightly differently >> from you; >> >> - code built while running UP works. >> - code built while running SMP fails. > > Actually, code built while running SMP was failing, but causing a > boot > into UP caused it to work, and then going back to SMP caused it to > still > work. > >> I'm inclined to agree with Nate in that it's unlikely that you have >> found a compiler bug, more likely an environment (eg. kernel) bug >> that >> is causing you some serious grief. Seems that way. The sequence as not critical. Just putting moderate load on the SMP kernel would cause the system to go googoo. ONE of the symptoms was bad compiles. Another was a crashing gcc, etc. Simon