From owner-freebsd-current@FreeBSD.ORG Fri Sep 12 12:56:01 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 599B716A4BF for ; Fri, 12 Sep 2003 12:56:01 -0700 (PDT) Received: from mailhub.yumyumyum.org (dsl092-171-091.wdc2.dsl.speakeasy.net [66.92.171.91]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACA6C43FEA for ; Fri, 12 Sep 2003 12:55:59 -0700 (PDT) (envelope-from culverk@yumyumyum.org) Received: by mailhub.yumyumyum.org (Postfix, from userid 80) id 190DC466; Fri, 12 Sep 2003 15:56:03 -0400 (EDT) Received: from 141.156.69.109 ([141.156.69.109]) by mailhub.yumyumyum.org (Horde) with HTTP for ; Fri, 12 Sep 2003 15:56:02 -0400 Message-ID: <1063396562.945f4dc2da041@mailhub.yumyumyum.org> Date: Fri, 12 Sep 2003 15:56:02 -0400 From: culverk@yumyumyum.org To: Scott Reese References: <1063396282.9261.18.camel@borges> In-Reply-To: <1063396282.9261.18.camel@borges> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) 4.0-cvs X-Originating-IP: 141.156.69.109 cc: freebsd-current@freebsd.org Subject: Re: GCC tickling obscure hardware bug or...? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Sep 2003 19:56:01 -0000 Quoting Scott Reese : > Hello all, I'm rephrasing my previous question to reflect new findings > in my situation in the hopes that someone may have an idea of what's > going on here (see thread "Internal compiler error in > reload_cse_simplify_operands" from earlier this week). > > In a nutshell, I have upgraded my machine to a PIV 2.4 GHz processor on > a VIA P4B 400 motherboard with 512 MB Samsung 2700 DDRAM. I have a 300 > Watt power supply with a ball-bearing fan and a Seagate 40 GB HD. The > problem I'm having that I did not see with my PIII is that I'm getting > intermittent internal compiler errors when attempting to compile > anything (again, see previous thread for an example). I even did a > fresh install of the system yesterday in order to rule out something > random getting hosed causing problems with my compiler. Through > experimentation, I've found that toggling the CFLAGS from -O to -O2 or > vice-versa works around the problem (actually, I've had greater success > leaving my CFLAGS set to -O2 -pipe and occasionally bringing them back > to -O -pipe when I run into an ICE and then setting them back again). > My hunch is that some hardware bug is being tickled by gcc somehow. I > don't think it's the standard "broken hardware" thing because I've not > received any signal 11/7/4 errors at all and the system runs > wonderfully. So far it's been up for over 24 hours, compiling ports and > running without a hitch. The only strangeness is the compiler's > behavior. Also, I should mention that I added > > options DISABLE_PSE > options DISABLE_PG_G > > to my kernel config but the ICE's still persist, though they seem to be > less frequent now. > > Attached is my dmesg, please let me know if anyone would like any more > information about this or if you have any idea what might be going on > here. > > Thank you, > Scott > Whenever I've had problems like this, it's been either bad memory, or bad memory settings in bios. I'd check both of those things. Ken