Date: Wed, 04 Nov 2009 16:24:01 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: Kai Gallasch <gallasch@free.de> Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC2 amd64 - kernel panic running make buildworld Message-ID: <867hu6gvou.fsf@ds4.des.no> In-Reply-To: <20091031231545.493cee89@boiler.free.de> (Kai Gallasch's message of "Sat, 31 Oct 2009 23:15:45 %2B0100") References: <20091031231545.493cee89@boiler.free.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Kai Gallasch <gallasch@free.de> 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 <sbahra at repnop dot org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?867hu6gvou.fsf>