From owner-freebsd-bugs@freebsd.org Mon Feb 8 10:42:01 2021 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id AE41A52D36A for ; Mon, 8 Feb 2021 10:42:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DZ2dj4P7Kz3GV8 for ; Mon, 8 Feb 2021 10:42:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id 96E0B52D80E; Mon, 8 Feb 2021 10:42:01 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 96A4652D61D for ; Mon, 8 Feb 2021 10:42:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4DZ2dj3jNcz3H0r for ; Mon, 8 Feb 2021 10:42:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 67BB615C6B for ; Mon, 8 Feb 2021 10:42:01 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 118Ag1Ua098167 for ; Mon, 8 Feb 2021 10:42:01 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 118Ag15K098166 for bugs@FreeBSD.org; Mon, 8 Feb 2021 10:42:01 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 253344] System hard resets when setting CPU frequency with Ryzen 2600 Date: Mon, 08 Feb 2021 10:42:01 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: blaircwyatt@gmail.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Feb 2021 10:42:01 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D253344 Bug ID: 253344 Summary: System hard resets when setting CPU frequency with Ryzen 2600 Product: Base System Version: 12.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: blaircwyatt@gmail.com I started having an issue when I enabled powerd on FreeBSD 12.2. With the default adaptive settings, the system would hard reset shortly after starti= ng the daemon. After some digging it seems that it this reset occurs when the frequency is= set and is instantly reproduceable with sysctl: nas: ~# sysctl dev.cpu.0.freq dev.cpu.0.freq: 3400 nas: ~# sysctl -n dev.cpu.0.freq_levels 3400/3867 2975/3383 2800/2537 2450/2219 2100/1902 1750/1585 1550/1237 1356/= 1082 1162/927 968/773 775/618 581/463 387/309 193/154 nas: ~# sysctl dev.cpu.0.freq=3D2100 dev.cpu.0.freq: 3400 -> 2100 nas: ~# *reset* I am running the following configuration: ASUS PRIME A320I-K Ryzen 2600 Corsair 2x8GB 2666MHz SilverStone 650W SFX Power Supply 4x8TB WD Red Asus BIOS update latest version 2203 - 2020/08/11 (AGESA at 1006). I have updated to FreeBSD 12.2-RELEASE-p3 (from a fresh install of RELEASE)= as well. After some searching, I also tried the following BIOS tricks and they don't change the symptom: Global C-State Control - Disabled Power Supply Idle Control - Typical SMT - Disabled I did run up an Ubuntu instance and frequency scaling is working and report= ing correctly on there (under /proc/cpuinfo). Interestingly the FreeBSD system reports 22.5W at idle with just CPU/RAM/Motherboard/Fans/USB/No Graphics Card (but the CPU still reporting 2400MHz) and the same could be seen under Ubuntu. Something else of interest is that with this config, temp monitoring reports incorrect temperatures (same as board temp in BIOS, CPU temp is about 10 degrees more): dev.cpu.11.temperature: 32.1C dev.cpu.10.temperature: 32.1C dev.cpu.9.temperature: 32.1C dev.cpu.8.temperature: 32.1C dev.cpu.7.temperature: 32.1C dev.cpu.6.temperature: 32.1C dev.cpu.5.temperature: 32.1C dev.cpu.4.temperature: 32.1C dev.cpu.3.temperature: 32.1C dev.cpu.2.temperature: 32.1C dev.cpu.1.temperature: 32.1C dev.cpu.0.temperature: 32.1C Could it be that the CPU is actually scaling correctly without powerd and j= ust not reporting? Anyway, that's a bit of an aside, the hard reboot is the main problem. --=20 You are receiving this mail because: You are the assignee for the bug.=