From owner-freebsd-current Sat Feb 22 11:18:47 2003 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 90ECF37B401 for ; Sat, 22 Feb 2003 11:18:46 -0800 (PST) Received: from MX3.estpak.ee (mta2.mail.neti.ee [194.126.101.111]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1AE5943F75 for ; Sat, 22 Feb 2003 11:18:45 -0800 (PST) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-44-69-dsl.mus.estpak.ee [80.235.44.69]) by MX3.estpak.ee (Postfix) with ESMTP id C614E88005; Sat, 22 Feb 2003 21:18:42 +0200 (EET) Received: (from vallo@localhost) by kevad.internal (8.12.6/8.12.6/Submit) id h1MJIceC003902; Sat, 22 Feb 2003 21:18:39 +0200 (EET) (envelope-from vallo) Date: Sat, 22 Feb 2003 21:18:38 +0200 From: Vallo Kallaste To: "Paul A. Howes" Cc: freebsd-current@FreeBSD.org Subject: [Re: cc: Internal error: Illegal instruction (program as) Message-ID: <20030222191838.GA3818@kevad.internal> Reply-To: kalts@estpak.ee References: <001c01c2da91$782551e0$0200a8c0@howesnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001c01c2da91$782551e0$0200a8c0@howesnet> User-Agent: Mutt/1.5.1i-ja.1 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 On Sat, Feb 22, 2003 at 11:43:01AM -0500, "Paul A. Howes" wrote: > I am receiving some strange errors during a buildworld of 5.0-RELEASE-p2 > from 5.0-RELEASE-p1. The location of where the failure varies, but the > program that causes the failure is the same every time: "as". > > The errors are a variety of signal 10 and signal 4. I do find an > "as.core" file under /usr/obj, but as is stripped, so there are no > debugging symbols or listing that I can provide. > > The strange thing is that I have been able to successfully build > XFree86, KDE, and many other ports on this system. I followed the > 4.x-to-5.0 upgrade directions to the letter about a month ago, and have > had no major problems before this. > > Any help would be greatly appreciated! As John Hay suggested, add DISABLE_PSE and DISABLE_PG_G to your kernel configuration and rebuild/install kernel. I was having _exactly_ same behaviour; at the beginning of test runs to narrow the problem a bit I did _large_ ports builds, which ran for 1,5 days.. flawlessly, as you had seen. Then changed test method to parallel (make -j4) buildworld and the problem occasionally appeared from nowhere again. The flags mentioned before will work, as I haven't had any problems after enabling them (months of time now). -- Vallo Kallaste To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message