From owner-freebsd-amd64@freebsd.org Sun Mar 26 22:02:26 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 A258CD1D8E1 for ; Sun, 26 Mar 2017 22:02:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 92AA01551 for ; Sun, 26 Mar 2017 22:02:26 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2QM2QbQ050848 for ; Sun, 26 Mar 2017 22:02:26 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 215898] Usb Acting weird Date: Sun, 26 Mar 2017 22:02:26 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: cy@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution bug_status cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Sun, 26 Mar 2017 22:02:26 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215898 Cy Schubert changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |--- Status|Closed |Open CC| |cy@FreeBSD.org --- Comment #22 from Cy Schubert --- Seeing the same problem again post r315914. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-amd64@freebsd.org Mon Mar 27 06:29:04 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 8D567D1F55C for ; Mon, 27 Mar 2017 06:29:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 76C0C18EE for ; Mon, 27 Mar 2017 06:29:04 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2R6T3Jx007326 for ; Mon, 27 Mar 2017 06:29:04 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 215898] Usb Acting weird Date: Mon, 27 Mar 2017 06:29:04 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Mon, 27 Mar 2017 06:29:04 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215898 --- Comment #23 from Hans Petter Selasky --- What are the errors you see in dmesg? --HPS --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-amd64@freebsd.org Mon Mar 27 06:29:46 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 3B7BED1F5C3 for ; Mon, 27 Mar 2017 06:29:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 2BD371982 for ; Mon, 27 Mar 2017 06:29:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2R6Tjh6008234 for ; Mon, 27 Mar 2017 06:29:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 215898] Usb Acting weird Date: Mon, 27 Mar 2017 06:29:45 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: usb X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: hselasky@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-usb@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Mon, 27 Mar 2017 06:29:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D215898 --- Comment #24 from Hans Petter Selasky --- There hasn't been any USB patches recently, so this is likely not related to USB. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-amd64@freebsd.org Tue Mar 28 03:43:41 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 B0908D211A1 for ; Tue, 28 Mar 2017 03:43:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 9F028DC8 for ; Tue, 28 Mar 2017 03:43:41 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v2S3hfZ2066838 for ; Tue, 28 Mar 2017 03:43:41 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-amd64@FreeBSD.org Subject: [Bug 217138] head (e.g.) -r315870 for arm64: sh vs. jemalloc asserts: include/jemalloc/internal/tsd.h:687: Failed assertion: "tsd_booted" once swapped in after being swapped out (comment 10) Date: Tue, 28 Mar 2017 03:43:41 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: markmi@dsl-only.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: attachments.created Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 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: Tue, 28 Mar 2017 03:43:41 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217138 --- Comment #33 from Mark Millard --- Created attachment 181258 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D181258&action= =3Dedit Test program with thousands of 14 KiByte allocations The test program that has thousands of 14 KiByte allocations usually ends up with them all being zeroed in the parent and child of the fork. But I've had a couple of runs where a much smaller prefix was messed up and then there were normal, expected values. #define region_size (14u*1024u) . . . #define num_regions (256u*1024u*1024u/region_size) So num_regions=3D=3D18724, using up most of 256 MiBytes. Note: each region has its own 14 KiByte allocation. But dyn_regions[1296].array[0] in one example was the first normal value. In another example dyn_regions[2180].array[4096] was the first normal value. The last is interesting for being part way through an allocation's space. That but aligning with a 4 KiByte page size would seem odd for a pure-jemalloc issue. --=20 You are receiving this mail because: You are on the CC list for the bug.= From owner-freebsd-amd64@freebsd.org Wed Mar 29 07:55:19 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 42A82D23A08 for ; Wed, 29 Mar 2017 07:55:19 +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 09EB8670B4 for ; Wed, 29 Mar 2017 07:55:18 +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.5 required=7.0 tests=ALL_TRUSTED,BAYES_00, MISSING_MID autolearn=no 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 632B3141480F for ; Wed, 29 Mar 2017 09:54:18 +0200 (CEST) Received: from asbach.renzel.net (unknown [172.18.96.1]) by dublin.vkf.isb.de.renzel.net (Postfix) with ESMTP id 5D66F81178 for ; Wed, 29 Mar 2017 09:54:18 +0200 (CEST) Content-Type: text/plain; charset="ISO-8859-1" From: Nils Beyer Organization: VKF Renzel GmbH Date: Wed, 29 Mar 2017 09:54:18 +0200 User-Agent: KNode/4.14.10 Content-Transfer-Encoding: 7Bit Subject: Re: FreeBSD on Ryzen To: freebsd-amd64@FreeBSD.org References: <201703222030.v2MKUJJs026400@gw.catspoiler.org> Lines: 41 MIME-Version: 1.0 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on nijmegen.renzel.net X-Mailman-Approved-At: Wed, 29 Mar 2017 11:24:00 +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 07:55:19 -0000 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: on cpu0 hwpstate0: set freq failed, err 6 ============================================================================== TIA and regards, Nils From owner-freebsd-amd64@freebsd.org Wed Mar 29 13:08:58 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 2084CD23469 for ; 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 ; 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 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-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: 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: on cpu0 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