From owner-freebsd-amd64@freebsd.org Wed Mar 29 19:01:36 2017 Return-Path: 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 B0260D23A0F for ; Wed, 29 Mar 2017 19:01:36 +0000 (UTC) (envelope-from nbe@renzel.net) Received: from nijmegen.renzel.net (mx1.renzel.net [195.243.213.130]) by mx1.freebsd.org (Postfix) with ESMTP id 420D8C8E for ; Wed, 29 Mar 2017 19:01:35 +0000 (UTC) (envelope-from nbe@renzel.net) X-Virus-Scanned: GDATA Antivirus at gdata-milter.renzel.de.isb X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=-7.0 required=7.0 tests=BAYES_00,UNPARSEABLE_RELAY autolearn=ham version=3.3.2 Received: from dublin.vkf.isb.de.renzel.net (unknown [10.0.0.80]) by nijmegen.renzel.net (smtpd) with ESMTP id 205C0141481C for ; Wed, 29 Mar 2017 21:01:32 +0200 (CEST) Received: from navigator.renzel.net (unknown [10.0.0.254]) by dublin.vkf.isb.de.renzel.net (Postfix) with ESMTPS id 043E181C56 for ; Wed, 29 Mar 2017 21:01:32 +0200 (CEST) Received: from navigator.renzel.net (localhost [127.0.0.1]) by navigator.renzel.net (8.14.9/8.14.5) with ESMTP id v2TJ1V6q087060 for ; Wed, 29 Mar 2017 21:01:31 +0200 (CEST) (envelope-from nbe@renzel.net) Received: (from www@localhost) by navigator.renzel.net (8.14.9/8.14.5/Submit) id v2TJ1VXm087059; Wed, 29 Mar 2017 21:01:31 +0200 (CEST) (envelope-from nbe@renzel.net) To: freebsd-amd64@freebsd.org Subject: Re: FreeBSD on Ryzen X-PHP-Originating-Script: 501:rcube.php Received: from WcEtJ88eLD68jssnfN47d0z6Oxjztvqz828JBHK6FaNs+P6hvw/44A== (OfXFruJEcxlanBGFkhMPhlJ7k0xH2/RS) by webmail.renzel.net with HTTP (HTTP/1.1 POST); Wed, 29 Mar 2017 21:01:31 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Date: Wed, 29 Mar 2017 21:01:31 +0200 From: Nils Beyer Organization: VKF Renzel GmbH In-Reply-To: <201703291308.v2TD8nOX030817@gw.catspoiler.org> References: <201703291308.v2TD8nOX030817@gw.catspoiler.org> Message-ID: <030fb07230af09e172cec7cc63209043@renzel.net> X-Sender: nbe@renzel.net User-Agent: Roundcube Webmail/1.2.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on nijmegen.renzel.net X-Mailman-Approved-At: Wed, 29 Mar 2017 19:36:12 +0000 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Mar 2017 19:01:36 -0000 On 2017-03-29 15:08, Don Lewis wrote: > dev.cpu.0.freq_levels: 3400/4590 3000/3825 2200/1980 > dev.cpu.0.freq: 3400 Thanks - so I assume that sth. doesn't work correctly inside "hwpstate" when the CPU is overclocked. I've enabled "debug.hwpstate_debug" an got: ======================================================================================= hwpstate0: setting P0-state on cpu0 hwpstate0: setting P0-state on cpu1 hwpstate0: setting P0-state on cpu2 hwpstate0: setting P0-state on cpu3 hwpstate0: setting P0-state on cpu4 hwpstate0: setting P0-state on cpu5 hwpstate0: setting P0-state on cpu6 hwpstate0: setting P0-state on cpu7 hwpstate0: setting P0-state on cpu8 hwpstate0: setting P0-state on cpu9 hwpstate0: setting P0-state on cpu10 hwpstate0: setting P0-state on cpu11 hwpstate0: setting P0-state on cpu12 hwpstate0: setting P0-state on cpu13 hwpstate0: setting P0-state on cpu14 hwpstate0: setting P0-state on cpu15 hwpstate0: result: P1-state on cpu0 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu1 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu2 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu3 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu4 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu5 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu6 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu7 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu8 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu9 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu10 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu11 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu12 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu13 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu14 hwpstate0: error: loop is not enough. hwpstate0: result: P1-state on cpu15 hwpstate0: error: loop is not enough. ======================================================================================= So the CPU cannot switch to P0-state for some reason. Does anyone have an idea besides disabling overclocking? TIA and regards, Nils