[Bug 221029] AMD Ryzen: strange compilation failures using poudriere or plain buildkernel/buildworld

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Aug 20 08:55:08 UTC 2017


--- Comment #81 from Mark Millard <markmi at dsl-only.net> ---
(In reply to Don Lewis from comment #80)

FYI for my tests:

So far with kern.sched.steal_idle=0 I've never had
lang/ghc fail to build.

So far with kern.sched.steal_idle=1 I've always had
lang/ghc fail to build --before it even started using
ghc-stage1. (I monitored via top.) These failures do
seem random for at what point of the lang/ghc build
hat the failure happens. (Builds that work take
vastly longer to complete as well.)

I've done a half dozen build attempts or so each way
over those two alternatives (so far).

lang/ghc builds failed for kern.sched.steal_idle=1
every time that I've tried it, even when poudriere
was configured to avoid parallel builds (including
and avoiding ALLOW_MAKE_JOBS) and lang/ghc was the
only thing being built, prerequisites already in

System-wide memory bandwidth usage being high does
not seem to be important to having the lang/ghc builds

Most of the failure examples are for CPU temperatures
under 40 DegC. Only for hot days in contexts without
air conditioning have I seen as high as 44 DegC for
the Ryzen PC. (Liquid cooled, two 360 mm radiators,
ten 120 mm fans, low end graphics card, and so on:
all biased to keeping temperatures down.)

Die temperature does not seem to be important to having
the lang/ghc builds fail.

(It is too preliminary to depend on yet but so far the
kern.sched.steal_idle=0 "poudriere bulk -a" has had no
SIGSEGV or SIGBUS like failures for any ports, unlike
when I'd tried with kern.sched.steal_idle=1 .)

I do not expect the kern.sched.steal_idle=0 results to be
luck at this point (up to any kern.sched.balance=1
contribution if involved).

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list