From owner-freebsd-stable@freebsd.org Tue Jan 23 20:34:23 2018 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3AD64EC59B4 for ; Tue, 23 Jan 2018 20:34:23 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5E6476DA38; Tue, 23 Jan 2018 20:34:22 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from [82.47.237.48] (helo=foula.drayhouse.twisted.org.uk) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1ee5Fm-000D1N-7V; Tue, 23 Jan 2018 20:33:10 +0000 Subject: Re: Ryzen issues on FreeBSD ? To: Mike Tancsa , Don Lewis Cc: Peter Moody , freebsd-stable@freebsd.org References: <8e842dec-ade7-37d1-6bd8-856ea1a827ca@sentex.net> <9b769e4e-b098-b294-0bce-8bb1c42e8a59@rootautomation.com> <730eb882-1c6a-afb7-0ada-396db44fb34b@ingresso.co.uk> <8b882970-4d5d-2a96-4dac-779cab07b9ae@sentex.net> <343acf99-3e9e-093a-7390-c142396c2985@sentex.net> From: Pete French Message-ID: <0bb2b241-6e79-0cc6-2046-9960609aedc2@ingresso.co.uk> Date: Tue, 23 Jan 2018 20:32:48 +0000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Jan 2018 20:34:23 -0000 On 23/01/2018 19:08, Mike Tancsa wrote: > It looks like this thread got mention on phorix :) In the comments > section (comment #9) a post makes reference to > > http://blog.programster.org/ubuntu-16-04-compile-custom-kernel-for-ryzen > > I guess Linux is still working through similar lockups too :( Interesting - do we have anything like RCU implemented in the kernel which might be worth looking at ? From a quick glance it looks like its just a software technique, so I cant see which bits of the CPU it's tickling that might cause issues though.