From nobody Mon Jun 5 09:02:35 2023 X-Original-To: stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4QZSL25l56z4Yxtv for ; Mon, 5 Jun 2023 09:02:34 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.netfence.it (mailserver.netfence.it [78.134.96.152]) (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 (2048 bits) client-digest SHA256) (Client CN "mailserver.netfence.it", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4QZSL11g4Mz45xW for ; Mon, 5 Jun 2023 09:02:33 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=netfence.it header.s=202304 header.b=T0HCEeMQ; spf=pass (mx1.freebsd.org: domain of ml@netfence.it designates 78.134.96.152 as permitted sender) smtp.mailfrom=ml@netfence.it; dmarc=pass (policy=none) header.from=netfence.it Received: from [192.168.144.18] (46-44-233-122.ip.welcomeitalia.it [46.44.233.122] (may be forged)) (authenticated bits=0) by soth.netfence.it (8.17.1/8.17.1) with ESMTPSA id 35592LjA089330 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO); Mon, 5 Jun 2023 11:02:22 +0200 (CEST) (envelope-from ml@netfence.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netfence.it; s=202304; t=1685955744; bh=xxSWFQ38Y+GZe/CtS7Xxl5XqmFJrPFbU3NExozjUEj4=; h=Date:Subject:To:References:Cc:From:In-Reply-To; b=T0HCEeMQ2orRY+iAg3pTurrsSMNAZbICyfaJtJ3DqtGKH5YX9oOtXPXfQS3eDwoH6 7nl3riUXKb8dVEy/a826QSF4mutWsQvQQ2TiIUa6HyvkEAit2UysCI5QSdzhilUF5A xbrByIYTuyH+O9irt1wVzkjBs60kDrp1+R61r4bk= X-Authentication-Warning: soth.netfence.it: Host 46-44-233-122.ip.welcomeitalia.it [46.44.233.122] (may be forged) claimed to be [192.168.144.18] Message-ID: <28e13090-c943-1bad-6200-cf322bd74c50@netfence.it> Date: Mon, 5 Jun 2023 11:02:35 +0200 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: Periodic lag spike on FreeBSD 13.2-RELEASE (intel graphics / wayland) Content-Language: en-US To: Jonathan Vasquez References: Cc: "stable@freebsd.org" From: Andrea Venturoli In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.86 X-Spamd-Result: default: False [-3.99 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.988]; DMARC_POLICY_ALLOW(-0.50)[netfence.it,none]; R_DKIM_ALLOW(-0.20)[netfence.it:s=202304]; R_SPF_ALLOW(-0.20)[+ip4:78.134.96.152]; MIME_GOOD(-0.10)[text/plain]; BLOCKLISTDE_FAIL(0.00)[78.134.96.152:server fail,46.44.233.122:server fail]; MLMMJ_DEST(0.00)[stable@freebsd.org]; TO_DN_EQ_ADDR_SOME(0.00)[]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT]; RCPT_COUNT_TWO(0.00)[2]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DKIM_TRACE(0.00)[netfence.it:+]; FROM_HAS_DN(0.00)[]; HAS_XAW(0.00)[]; TO_DN_SOME(0.00)[]; ARC_NA(0.00)[]; RCVD_TLS_ALL(0.00)[] X-Rspamd-Queue-Id: 4QZSL11g4Mz45xW X-Spamd-Bar: --- X-ThisMailContainsUnwantedMimeParts: N On 5/29/23 17:23, Jonathan Vasquez wrote: > Hello all, Hello. > I'm not sure if anyone is experiencing this, but on my framework laptop > running this graphic card... > I get periodic lag spikes. The lag spikes last about 2-3 seconds, almost Me too, on a Starlite laptop. vgapci0@pci0:0:2:0: class=0x030vgapci0@pci0:0:2:0: class=0x030000 rev=0x06 hdr=0x00 vendor=0x8086 device=0x3184 subvendor=0x0000 subdevice=0x0000 vendor = 'Intel Corporation' device = 'GeminiLake [UHD Graphics 605]' class = display subclass = VGA > I do notice these > messages in my dmesg and I think they may be related: > > drmn0: [drm] *ERROR* Atomic update failure on pipe D (start=20288 > end=20289) time 0 us, min 1073, max 1079, scanline start 1050, end 1081 I've got similar messages: drmn0: [drm] *ERROR* Atomic update failure on pipe A (start=293599 end=293600) time 0 us, min 1073, max 1079, scanline start 1070, end 1081 drmn0: [drm] *ERROR* Atomic update failure on pipe A (start=352658 end=352659) time 0 us, min 1073, max 1079, scanline start 1057, end 1058 drmn0: [drm] *ERROR* Atomic update failure on pipe A (start=401363 end=401364) time 1625 us, min 1073, max 1079, scanline start 1040, end 1147 drmn0: [drm] *ERROR* Atomic update failure on pipe A (start=875524 end=875525) time 1566 us, min 1073, max 1079, scanline start 997, end 997 So far I've been unable to correlate them with those lags. (Waiting for them to happen with an open windows with tail running, but, of course, it won't happen today :) > jon@leslie:~ $ pkg info drm-510-kmod > drm-510-kmod-5.10.163_7 > Name           : drm-510-kmod Same here. Further details differ, as I compile it myself. > I can't remember at the moment if it also happened with X11, but it may > have. I'not 100% sure, but I believe this started when I upgraded from 13.1 to 13.2 (with no other relevant change). > Please let me know if there is anything else I can provide to narrow > down the root cause. Thank you! No idea, really. If you want me to try something, collect other data, etc... I'll gladly comply. Perhaps a bug report should be opened? bye & Thanks av.