From owner-freebsd-current@FreeBSD.ORG Wed Nov 4 15:24:02 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A17F01065672 for ; Wed, 4 Nov 2009 15:24:02 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 64B8E8FC0A for ; Wed, 4 Nov 2009 15:24:02 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 8885F6D41B; Wed, 4 Nov 2009 15:24:01 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 59752844E9; Wed, 4 Nov 2009 16:24:01 +0100 (CET) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Kai Gallasch References: <20091031231545.493cee89@boiler.free.de> Date: Wed, 04 Nov 2009 16:24:01 +0100 In-Reply-To: <20091031231545.493cee89@boiler.free.de> (Kai Gallasch's message of "Sat, 31 Oct 2009 23:15:45 +0100") Message-ID: <867hu6gvou.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Wed, 04 Nov 2009 15:24:02 -0000 Kai Gallasch writes: > I installed 8.0RC2-amd64 on an 8-core opteron server a few days ago. > > When I try to do a make buildworld or make buildkernel the server > reboots without any message left in the logs. The same happens > when building bigger ports (for example ruby18 or perl58) Could it be related to this? What's your CPUID? Author: attilio Date: Wed Nov 4 01:32:59 2009 New Revision: 198868 URL: http://svn.freebsd.org/changeset/base/198868 Log: Opteron rev E family of processor expose a bug where, in very rare ocassions, memory barriers semantic is not honoured by the hardware itself. As a result, some random breakage can happen in uninvestigable ways (for further explanation see at the content of the commit itself). =20=20 As long as just a specific familly is bugged of an entire architecture is broken, a complete fix-up is impratical without harming to some extents the other correct cases. Considering that (and considering the frequency of the bug exposure) just print out a warning message if the affected machine is identified. =20=20 Pointed out by: Samy Al Bahra Help on wordings by: jeff MFC: 3 days Modified: head/sys/amd64/amd64/identcpu.c head/sys/i386/i386/identcpu.c DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no