From owner-freebsd-i386@FreeBSD.ORG Wed Jun 14 09:36:15 2006 Return-Path: X-Original-To: freebsd-i386@hub.freebsd.org Delivered-To: freebsd-i386@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCBA416A41B; Wed, 14 Jun 2006 09:36:15 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 716B743D49; Wed, 14 Jun 2006 09:36:15 +0000 (GMT) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (linimon@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k5E9aFPN099428; Wed, 14 Jun 2006 09:36:15 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k5E9aEcx099423; Wed, 14 Jun 2006 09:36:15 GMT (envelope-from linimon) Date: Wed, 14 Jun 2006 09:36:15 GMT From: Mark Linimon Message-Id: <200606140936.k5E9aEcx099423@freefall.freebsd.org> To: drixter@e-utp.net, linimon@FreeBSD.org, freebsd-i386@FreeBSD.org Cc: Subject: Re: i386/97772: World - compile error on cgram.y - segmentation fault X-BeenThere: freebsd-i386@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: I386-specific issues for FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jun 2006 09:36:15 -0000 Synopsis: World - compile error on cgram.y - segmentation fault State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Wed Jun 14 09:34:51 UTC 2006 State-Changed-Why: Please report kernel compile failures on the appropriate mailing list, in this case, freebsd-stable. Build failures tend to get fixed very quickly due to the high number of developers who track the latest code, and the automated tinderboxes that continually run builds. In particular, since the tinderbox is not reporting any similar errors, I think it is likely that you have failing RAM or an overheating processor, which have time and time again been the source of errors like this. http://www.freebsd.org/cgi/query-pr.cgi?pr=97772