From owner-freebsd-current Tue Nov 25 15:36:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA17202 for current-outgoing; Tue, 25 Nov 1997 15:36:31 -0800 (PST) (envelope-from owner-freebsd-current) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA17194 for ; Tue, 25 Nov 1997 15:36:26 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id KAA00560; Wed, 26 Nov 1997 10:01:33 +1030 (CST) Message-Id: <199711252331.KAA00560@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Nate Williams cc: Mike Smith , shimon@simon-shapiro.org, freebsd-current@FreeBSD.ORG Subject: Re: Compiler Bug??? In-reply-to: Your message of "Tue, 25 Nov 1997 08:16:09 PDT." <199711251516.IAA27098@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Nov 1997 10:01:33 +1030 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > 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. Not exactly. I quote: ] Scenario 1: ] ] Xfmail of 17-Nov-97 with xforms 0.88: Compiles fine, then produces ] dozens of ``Bad Attribute'' and `Bad Coordinates''. These come from ] libX11. Tearing my hair out did not help, so I boot UP (was on SMP). ] The problem is... GONE! ] ] Recompile on UP, reboot SMP... Problem is... Yup, GONE! This is actually: - code built while running SMP fails while running SMP. - code built while running SMP works UP. - code built while running UP works everywere. Either of our interpretations could be right. More data, Simon? mike