Do we have a CPUTYPE=native and/or generic stability problem?

Scot Hetzel swhetzel at
Sun Nov 4 09:43:21 UTC 2012

On Sat, Nov 3, 2012 at 5:24 PM, Alexander Leidinger
<Alexander at> wrote:
> Hi,
> while trying to update from r239708 to r242511 (amd64 arch) I tried to
> compile the world with "make -j8". After a short while I got an
> internal error in the clang compile (this is a gcc-compiled system, I
> don't use clang). The CFLAGS/COPTFLAGS are -O2 -pipe.
> Without the -j8 it compiles just fine.
> Without the CPUTYPE?=native it compiles even with -j8.
> The CPU is an Intel(R) Xeon(R) CPU (L5630) with ECC ram.
> The r239708 world runs stable since I installed it (build with
> CPUTYPE=native). The r242511 world (no CPUTYPE set) doesn't run stable
> (not only the watchdogd segfault I reported in another mail some minutes
> ago, but also some other kind of reboot every X minutes I haven't
> investigated yet).
> Does someone run -current on a similar system on a similar revision and
> can comment about the stability?

Not sure if your hitting the same bug, that was found in PR 112997.

When you set CPUTYPE?=native, doesn't set MACHINE_CPU to
the correct values for your CPUTYPE.

See for a patch

Does your system compile correctly, if you specify the CPUTYPE?


More information about the freebsd-current mailing list