From owner-freebsd-current@freebsd.org Tue Mar 23 09:34:45 2021 Return-Path: Delivered-To: freebsd-current@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 443BE57FC37 for ; Tue, 23 Mar 2021 09:34:45 +0000 (UTC) (envelope-from greg@unrelenting.technology) Received: from out0.migadu.com (out0.migadu.com [IPv6:2001:41d0:2:267::]) (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 4F4R6C4g6Mz4ZK4 for ; Tue, 23 Mar 2021 09:34:43 +0000 (UTC) (envelope-from greg@unrelenting.technology) Date: Tue, 23 Mar 2021 09:34:33 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=unrelenting.technology; s=key1; t=1616492075; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=qzD69NOefU1nW1fLWtKW6PmTMByLlUISVYL9Il2lP5E=; b=vv2tGbnYZxRYvx4FsaVLrHAvBH7gNcyOafkI7O7oF3qYQY6raNyEUyfTT2R5Yg9RiCsGVQ H80jbYEqqPLIGPKzJanrp3rk1H5oLwq0DxnBcg9hL2ovkNVBpubra3ebStmZx/fSd5a2lz tCO2XwnTiLvV/PzOyh0VIn8ZMWe0p3bWbLIaF1VVm+VbH+5OhwTNAl2mPFRJafLANlmxiJ HCagU8rqgVy0X/uSRLpfjDlalpCBpKJupMHe5yMU1T6vEfTyLW3PiynQkQUZRoQmasfpVf UyL7PCQ5GGk1UXoKuubwVq7IoidnbZrDwPv7IQleV6k9MSvdtNXYdME8KkvCNA== X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: myfreeweb To: freebsd-current@freebsd.org, Michael Gmelin , monochrome Subject: Re: freebsd 13 ryzen micro stutter In-Reply-To: <20210323101146.18c9a969@bsd64.grem.de> References: <20210323101146.18c9a969@bsd64.grem.de> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: greg@unrelenting.technology X-Rspamd-Queue-Id: 4F4R6C4g6Mz4ZK4 X-Spamd-Bar: --- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=unrelenting.technology header.s=key1 header.b=vv2tGbnY; dmarc=pass (policy=none) header.from=unrelenting.technology; spf=pass (mx1.freebsd.org: domain of greg@unrelenting.technology designates 2001:41d0:2:267:: as permitted sender) smtp.mailfrom=greg@unrelenting.technology X-Spamd-Result: default: False [-4.00 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; R_DKIM_ALLOW(-0.20)[unrelenting.technology:s=key1]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip6:2001:41d0:2:267::]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_LONG(-1.00)[-1.000]; SPAMHAUS_ZRD(0.00)[2001:41d0:2:267:::from:127.0.2.255]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[unrelenting.technology:+]; DMARC_POLICY_ALLOW(-0.50)[unrelenting.technology,none]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[2001:41d0:2:267:::from]; ASN(0.00)[asn:16276, ipnet:2001:41d0::/32, country:FR]; MID_RHS_MATCH_FROM(0.00)[]; MAILMAN_DEST(0.00)[freebsd-current] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2021 09:34:45 -0000 On March 23, 2021 9:11:46 AM UTC, Michael Gmelin wrote= : > > >On Mon, 22 Mar 2021 23:50:52 -0400 >monochrome wrote: > >> After about 8 months of struggling to narrow this down I did another=20 >> search and saw this: >>=20 >> https://www=2Ereddit=2Ecom/r/freebsd/comments/lc8fwo/freebsd_13_vega_64= _micro_stutter_in_x/ >>=20 >> I haven't seen this come up here so I thought I would bring it up=2E >>=20 >> My story started sometime before around August last year when synergy= =20 >> started getting really annoying with stuttering=2E Pretty sure it >> wasn't like that when I first started tracking 13-current in around >> May 2020 (I was on 12 with scfb for a long time before that with no >> issues), but since then I have tried to eliminate as many variables >> as possible=2E First I switched to barrier instead of synergy=2E Shortl= y >> after that I realized it was happening all the time and not just a >> network problem, I started using foobillard to verify during tests=2E I >> tried different RAM combinations, different network cards, a variety >> of RAM timings, stripping rc=2Econf etc, powerd settings, also scfb, >> with no effect=2E It is observable with ping -f, a dot or two appears >> every time it glitches=2E It seemed much better with RC2, but now with >> RC3 it seems to be back with a vengeance, and since its my main >> workstation and barrier/synergy server host for several machines, it >> is unbearable to use=2E Both Win10 and devuan3 on the same machine are >> smooth with no issues=2E Any feedback or info would be appreciated=2E >>=20 >> Hardware: >> ASRock B450M Pro4 >> Ryzen 2400G, no OC >> 32M DDR4-2933 >> Onboard Vega GPU, drm-fbsd13-kmod >> _______________________________________________ > >Without knowing much about the issue at hand, just a few ideas: > >Sysctls I would look at: >- raising *=2Ecx_lowest >- different kern=2Eeventtimer=2Etimer None of these should be an issue, but: sysctl kern=2Esched=2Esteal_thresh=3D1 For some reason with the default value of 2, I'm seeing weird stuttering i= n youtube videos, games, etc=2E on a 5950X system=2E 1 (or 0, IIRC) works f= ine=2E >Try running with powerd disabled=2E well, if you do that, don't forget to manually set the freq sysctl to the = maximum