From owner-freebsd-stable@FreeBSD.ORG Thu May 10 07:57:55 2012 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7B29106564A; Thu, 10 May 2012 07:57:55 +0000 (UTC) (envelope-from bartsch@dssgmbh.de) Received: from dss.incore.de (dss.incore.de [195.145.1.138]) by mx1.freebsd.org (Postfix) with ESMTP id A1D3B8FC14; Thu, 10 May 2012 07:57:55 +0000 (UTC) Received: from inetmail.dmz (inetmail.dmz [10.3.0.3]) by dss.incore.de (Postfix) with ESMTP id EA5675C9BA; Thu, 10 May 2012 09:57:54 +0200 (CEST) X-Virus-Scanned: amavisd-new at incore.de Received: from dss.incore.de ([10.3.0.3]) by inetmail.dmz (inetmail.dmz [10.3.0.3]) (amavisd-new, port 10024) with LMTP id HMsq8qd3r_S3; Thu, 10 May 2012 09:57:53 +0200 (CEST) Received: from mail.incore (fwintern.dmz [10.0.0.253]) by dss.incore.de (Postfix) with ESMTP id CA45B5C9B8; Thu, 10 May 2012 09:57:53 +0200 (CEST) Received: from pcadmin.incore (pcadmin.incore [192.168.0.140]) by mail.incore (Postfix) with ESMTPSA id C1AD245084; Thu, 10 May 2012 09:57:53 +0200 (CEST) Message-ID: <4FAB7500.7020204@dssgmbh.de> Date: Thu, 10 May 2012 09:57:52 +0200 From: Alfred Bartsch User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:7.0.1) Gecko/20111007 Thunderbird/7.0.1 MIME-Version: 1.0 To: Andriy Gapon 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> In-Reply-To: <4FAB6BE7.9060500@FreeBSD.org> X-Enigmail-Version: undefined 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: Thu, 10 May 2012 07:57:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 10.05.2012 09:19, schrieb Andriy Gapon: > on 10/05/2012 10:12 Alfred Bartsch said the following: >> I got this stupid idea of a "16k limit" during testing. It was >> unobvious to me that the build process in a standard environment >> (i386) simply produces invalid code. In i386 (32-bit) hardware, >> we don't use zfs at all, so I can't tell anything about >> gptzfsboot. For now, modifying /sys/boot/i386/gptboot/Makefile >> completely solves this actual build problem. >> >> IMHO the compiler should always know perfectly well in which >> hardware environment it runs and for which target environment it >> produces code. So the build environment should be modified to fix >> this. I would certainly give it a try, but unfortunately this is >> far beyond my knowledge. :-( > > That's an interesting theory. What kind of hardware do you have? > Is it something non-mainstream or sufficiently old? As far as I can > tell, our base GCC uses i686 target arch if none is explicitly > requested. > 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: FreeBSD 8.3-STABLE #0: Tue May 8 16:15:10 CEST 2012 root@pcadmin.incore:/usr/obj/usr/src/sys/PCADMIN i386 Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz (2141.96-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x6f6 Family = 6 Model = f Stepping = 6 Features=0xbfebfbff Features2=0xe3bd AMD Features=0x20100000 AMD Features2=0x1 TSC: P-state invariant If you do need more information, let me know. - -- Alfred Bartsch Data-Service GmbH mailto:bartsch@dssgmbh.de -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+rdQAACgkQ5QGe2JdVf3iHZACcDnC5FOx+xGCpbal0Bt9LKFSz HO0An028jZdQGxnzkUpOHlKKoV+WPmUN =4tGu -----END PGP SIGNATURE-----