From owner-freebsd-stable@freebsd.org Mon Mar 27 11:33:39 2017 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 30606CA2CC6 for ; Mon, 27 Mar 2017 11:33:39 +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 F0A3CF4A for ; Mon, 27 Mar 2017 11:33:38 +0000 (UTC) (envelope-from petefrench@ingresso.co.uk) Received: from dilbert.london-internal.ingresso.co.uk ([10.64.50.6]) by constantine.ingresso.co.uk with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.88 (FreeBSD)) (envelope-from ) id 1csSu0-000DuN-Bn for freebsd-stable@freebsd.org; Mon, 27 Mar 2017 11:33:36 +0000 Subject: Re: Opteron 6100-series "Magny-Cours" To: freebsd-stable@freebsd.org References: From: Pete French Message-ID: Date: Mon, 27 Mar 2017 12:33:36 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Mar 2017 11:33:39 -0000 On 03/27/17 11:09, Andrea Venturoli wrote: > On 03/25/17 19:02, Andriy Gapon wrote: >> >> Does anyone [still] use Opteron 6100-series / "Magny-Cours" processors >> with FreeBSD? > > Will an equivalent Athlon do or is this Opteron specific? > > What would that Athlon be? Opteron 6100 was a K10 core, like the Phenom II, but they were 8 core, so I would hazzard a guess that the FX-8350 or similar is the same. But its usually a good idea to test on the exact CPU exhibiting the issue. -pete. (FWIW, this is being types on a K10 machine and it works fine.)