From owner-freebsd-stable@FreeBSD.ORG Fri May 11 06:42:06 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9D997106566C for ; Fri, 11 May 2012 06:42:06 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id E03848FC0A for ; Fri, 11 May 2012 06:42:05 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id JAA13490; Fri, 11 May 2012 09:42:04 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1SSjYB-0004A0-QF; Fri, 11 May 2012 09:42:03 +0300 Message-ID: <4FACB4BB.1000008@FreeBSD.org> Date: Fri, 11 May 2012 09:42:03 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120503 Thunderbird/12.0.1 MIME-Version: 1.0 To: Alfred Bartsch References: <4FAA3912.3030801@dssgmbh.de> <4FAA4A11.808@FreeBSD.org> <4FAA5E70.7030508@dssgmbh.de> <4FAA83BD.2030204@FreeBSD.org> <4FAB6A7B.9050500@dssgmbh.de> <4FAB6BE7.9060500@FreeBSD.org> <4FAB7500.7020204@dssgmbh.de> In-Reply-To: <4FAB7500.7020204@dssgmbh.de> X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: freebsd-stable@FreeBSD.org Subject: Re: FreeBSD 8 i386 gptboot corrupt - SOLVED X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 May 2012 06:42:06 -0000 on 10/05/2012 10:57 Alfred Bartsch said the following: > Our i386 hardware is sufficiently old, and IMHO mainstream, e.g.: Intel > SR1325 with Pentium-4 CPU, 2GB RAM Intel SR2200 with Pentium-III CPU(s), > 2/4 GB RAM, Intel SR2300 with dual XEON, 4 GB RAM > > Even on my desktop (Intel MB DQ965CO, Intel Core2 CPU), this (wrong) > behavior can be reproduced. dmesg output: There is also an interest in what board models and BIOS versions you have there. -- Andriy Gapon