i386 -march=xxx behavior [Was: FreeBSD 8 i386 gptboot corrupt - SOLVED]

2012-05-11 Thread Andriy Gapon
on 09/05/2012 15:09 Alfred Bartsch said the following: Am 09.05.2012 12:42, schrieb Andriy Gapon: on 09/05/2012 12:29 Alfred Bartsch said the following: This behavior is restricted to 32-bit servers (i386), all 64-bit servers (amd64) work without any problem, as expected. After some

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-11 Thread Andriy Gapon
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,

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-11 Thread Alfred Bartsch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 11.05.2012 08:42, schrieb Andriy Gapon: 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

Re: i386 -march=xxx behavior [Was: FreeBSD 8 i386 gptboot corrupt - SOLVED]

2012-05-11 Thread Konstantin Belousov
On Fri, May 11, 2012 at 09:37:10AM +0300, Andriy Gapon wrote: on 09/05/2012 15:09 Alfred Bartsch said the following: Am 09.05.2012 12:42, schrieb Andriy Gapon: on 09/05/2012 12:29 Alfred Bartsch said the following: This behavior is restricted to 32-bit servers (i386), all 64-bit servers

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-10 Thread Alfred Bartsch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.05.2012 16:48, schrieb Andriy Gapon: on 09/05/2012 15:09 Alfred Bartsch said the following: Am 09.05.2012 12:42, schrieb Andriy Gapon: on 09/05/2012 12:29 Alfred Bartsch said the following: Hello, after migrating some of our older servers to

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-10 Thread 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

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-10 Thread Alfred Bartsch
-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

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-10 Thread Andriy Gapon
on 10/05/2012 10:57 Alfred Bartsch said the following: 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

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-10 Thread Alfred Bartsch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 10.05.2012 10:20, schrieb Andriy Gapon: on 10/05/2012 10:57 Alfred Bartsch said the following: 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

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-09 Thread Alfred Bartsch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 09.05.2012 12:42, schrieb Andriy Gapon: on 09/05/2012 12:29 Alfred Bartsch said the following: Hello, after migrating some of our older servers to FeeBSD 8.3-stable (cvsupped May 4th), they don't boot anymore after installing the new boot

Re: FreeBSD 8 i386 gptboot corrupt - SOLVED

2012-05-09 Thread Andriy Gapon
on 09/05/2012 15:09 Alfred Bartsch said the following: Am 09.05.2012 12:42, schrieb Andriy Gapon: on 09/05/2012 12:29 Alfred Bartsch said the following: Hello, after migrating some of our older servers to FeeBSD 8.3-stable (cvsupped May 4th), they don't boot anymore after installing the new