Date: Wed, 14 Feb 2018 09:06:18 +0000 From: Steven Hartland <killing@multiplay.co.uk> To: freebsd-hackers@freebsd.org Subject: Re: Stale memory during post fork cow pmap update Message-ID: <16f4ce10-70d3-12f4-2246-e8ab44ba511f@multiplay.co.uk> In-Reply-To: <aadcb842-fb07-e856-e525-2e562d5a9e2d@sentex.net> References: <5A7E7F2B.80900@dell.com> <20180210111848.GL33564@kib.kiev.ua> <5A7F6A7C.80607@dell.com> <20180210225608.GM33564@kib.kiev.ua> <5A82AB7C.6090404@dell.com> <20180213133010.GD94212@kib.kiev.ua> <aadcb842-fb07-e856-e525-2e562d5a9e2d@sentex.net>
next in thread | previous in thread | raw e-mail | index | archive | help
@kib do you think this issue could be the cause of the golang crashes during fork that we spoke about a while back https://github.com/golang/go/issues/15658 If its possible is there anything specific I could do to force a regular occurrence in order to confirm or deny it? On 13/02/2018 21:49, Mike Tancsa wrote: > On 2/13/2018 8:30 AM, Konstantin Belousov wrote: >> Apparently Ryzen CPUs are able to demonstrate it quite reliably with the >> python driver for the samba build. It was very surprising to me, esp. >> because I tried to understand the Ryzen bug for the whole last week and >> thought that it is more likely CPU store/load inconsistency than a software >> thing. See https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225584. > Just tested on an AMD EPYC 7281 (16/32 cores), and it runs into this bug > every time on the samba build. Applying the referenced patch fixes the > problem, at least I was able to test 4 builds in a row without issue. > > ---Mike > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16f4ce10-70d3-12f4-2246-e8ab44ba511f>