On 2017-Feb-20, at 11:10 AM, Mateusz Guzik <mjguzik at gmail.com> wrote:
> On Sat, Feb 18, 2017 at 04:18:05AM -0800, Mark Millard wrote:
>> [Note: I experiment with clang based powerpc64 builds,
>> reporting problems that I find. Justin is familiar
>> with this, as is Nathan.]
>> I tried to update the PowerMac G5 (a so-called "Quad Core")
>> that I have access to from head -r312761 to -r313864 and
>> ended up with random panics and hang ups in fairly short
>> order after booting.
>> Some approximate bisecting for the kernel lead to:
>> (sometimes getting part way into a buildkernel attempt
>> for a different version before a failure happens)
>> -r313266: works (just before use of atomic_fcmpset)
>> -r313271: fails (last of the "use atomic_fcmpset" check-ins)
>> (I did not try -r313268 through -r313270 as the use was
>> gradually added.)
>> So I'm currently running a -r313864 world with a -r313266
>> No kernel that I tried that was from before -r313266 had the
>> Any kernel that I tried that was from after -r313271 had the
>> Of course I did not try them all in other direction. :)
> I found that spin mutexes were not properly handling this, fixed in
> Locally I added a if (cpu_tick() % 2) return (0); snipped to amd64
> fcmpset to simulate failures. Everything works, while it would easily
> fail without the patch.
> That said, I hope this concludes the 'missing check for not-reread value
> of failed fcmpset' saga.
> Mateusz Guzik <mjguzik gmail.com>
I tried to update from -r313864 to -r313999 in my amd64 context
(a VirtualBox machine under macOS) but it now crashes late in
the boot sequence (after it processes a dump if I make one but
before I can log in).
This update was via my usual explicit svnlite update; buildworld
buildkernel; etc. production style build of world and kernel,
including use of MALLOC_PRODUCTION.
The window shows:
markmi at dsl-only.net
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"