From owner-freebsd-amd64@freebsd.org  Wed Mar 29 13:08:58 2017
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 2084CD23469
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 29 Mar 2017 13:08:58 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from gw.catspoiler.org (unknown [IPv6:2602:304:b010:ef20::f2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "gw.catspoiler.org", Issuer "gw.catspoiler.org" (not verified))
 by mx1.freebsd.org (Postfix) with ESMTPS id 0121E6CEEB
 for <freebsd-amd64@FreeBSD.org>; Wed, 29 Mar 2017 13:08:57 +0000 (UTC)
 (envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (mousie.catspoiler.org [192.168.101.2])
 by gw.catspoiler.org (8.15.2/8.15.2) with ESMTP id v2TD8nOX030817;
 Wed, 29 Mar 2017 06:08:53 -0700 (PDT)
 (envelope-from truckman@FreeBSD.org)
Message-Id: <201703291308.v2TD8nOX030817@gw.catspoiler.org>
Date: Wed, 29 Mar 2017 06:08:49 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
Subject: Re: FreeBSD on Ryzen
To: nbe@renzel.net
cc: freebsd-amd64@FreeBSD.org
In-Reply-To: <201703291259.v2TCxQmO030622@gw.catspoiler.org>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Mar 2017 13:08:58 -0000

On 29 Mar, Nils Beyer wrote:
> Hi Don,
> 
> Don Lewis wrote:
>> I put together a Ryzen 1700X machine over the weekend and installed the
>> 12.0-CURRENT r315413 snapshot on it a couple of days ago.  The RAM is
>> DDR4 2400.
>> 
>> First impression is that it's pretty zippy.
> 
> I also have a Ryzen 1700 (OCed to 3.4GHz) now and can confirm that nearly
> everything is running fine; even "bhyve".
> 
> Could you do me a favour and execute "sysctl dev.cpu.0". It seems that the
> frequency levels are not handled correctly yet. Here's my output:
> ==============================================================================
> #sysctl dev.cpu.0
> dev.cpu.0.cx_method: C1/hlt C2/io
> dev.cpu.0.cx_usage_counters: 16616204 0
> dev.cpu.0.cx_usage: 100.00% 0.00% last 375us
> dev.cpu.0.cx_lowest: C1
> dev.cpu.0.cx_supported: C1/1/0 C2/2/400
> dev.cpu.0.freq_levels: 3400/3562 2700/2835 1550/1312
> dev.cpu.0.freq: 2700
> dev.cpu.0.%parent: acpi0
> dev.cpu.0.%pnpinfo: _HID=none _UID=0
> dev.cpu.0.%location: handle=\_PR_.P000
> dev.cpu.0.%driver: cpu
> dev.cpu.0.%desc: ACPI CPU
> 
> #sysctl dev.cpu.0.freq=3400
> dev.cpu.0.freq: 2700
> sysctl: dev.cpu.0.freq=3400: Device not configured
> 
> #dmesg -a | grep hwpstate
> hwpstate0: <Cool`n'Quiet 2.0> on cpu0
> hwpstate0: set freq failed, err 6
> ==============================================================================


% sysctl dev.cpu.0
dev.cpu.0.cx_method: C1/hlt C2/io
dev.cpu.0.cx_usage_counters: 16502716 0
dev.cpu.0.cx_usage: 100.00% 0.00% last 211us
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_supported: C1/1/0 C2/2/400
dev.cpu.0.freq_levels: 3400/4590 3000/3825 2200/1980
dev.cpu.0.freq: 3400
dev.cpu.0.%parent: acpi0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%location: handle=\_PR_.P000
dev.cpu.0.%driver: cpu
dev.cpu.0.%desc: ACPI CPU

# dmesg -a | grep hwpstate
hwpstate0: <Cool`n'Quiet 2.0> on cpu0