From nobody Thu Oct 3 13:27:40 2024 X-Original-To: x11@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 4XKCCp4xkHz5YKN9 for ; Thu, 03 Oct 2024 13:27:50 +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 "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XKCCm2vNJz4SW1 for ; Thu, 3 Oct 2024 13:27:48 +0000 (UTC) (envelope-from ml@netfence.it) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=netfence.it header.s=202407 header.b=oFddPHap; 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 [10.1.2.18] (alamar.local.netfence.it [10.1.2.18]) (authenticated bits=0) by soth.netfence.it (8.18.1/8.17.2) with ESMTPSA id 493DReX8015372 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NO) for ; Thu, 3 Oct 2024 15:27:40 +0200 (CEST) (envelope-from ml@netfence.it) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netfence.it; s=202407; t=1727962060; bh=hmvNo2GNdDGWwhh16n3i5fNSPMJUrwFOYmKPjGdm7k8=; h=Date:To:From:Subject; b=oFddPHapSXTLwPEZRZylWdnzxSyiUmSa1JRmjbJKlYCj9jLypOseYe171Ym//9rjl rND2h4DEuiVxnyexbz4uapZqsMQIlnD1rb8Gimo6Wv5g5lcAbiTAWmuMmggLaPxLOX r+HA08NL/d8tOGhCg15aWMtV1ipVyytoUdqreEPs= X-Authentication-Warning: soth.netfence.it: Host alamar.local.netfence.it [10.1.2.18] claimed to be [10.1.2.18] Message-ID: <418fbdc4-d794-4e79-bedc-8ef90a16f2cf@netfence.it> Date: Thu, 3 Oct 2024 15:27:40 +0200 List-Id: X11 List-Archive: https://lists.freebsd.org/archives/freebsd-x11 List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-x11@freebsd.org Sender: owner-freebsd-x11@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US To: x11@freebsd.org From: Andrea Venturoli Subject: GPU hanging after upgrade to 14.1 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[netfence.it,none]; R_SPF_ALLOW(-0.20)[+ip4:78.134.96.152]; R_DKIM_ALLOW(-0.20)[netfence.it:s=202407]; MIME_GOOD(-0.10)[text/plain]; XM_UA_NO_VERSION(0.01)[]; RCPT_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:35612, ipnet:78.134.0.0/17, country:IT]; RCVD_VIA_SMTP_AUTH(0.00)[]; MIME_TRACE(0.00)[0:+]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_ALL(0.00)[]; MLMMJ_DEST(0.00)[x11@freebsd.org]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; HAS_XAW(0.00)[]; MID_RHS_MATCH_FROM(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; TO_DN_NONE(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[x11@freebsd.org]; DKIM_TRACE(0.00)[netfence.it:+] X-Rspamd-Queue-Id: 4XKCCm2vNJz4SW1 X-Spamd-Bar: --- Hello. I've got a Starlite laptop which has always worked flawlessly (at least WRT graphics). > pciconf -lvb > vgapci0@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 > bar [10] = type Memory, range 64, base 0x90000000, size 16777216, enabled > bar [18] = type Prefetchable Memory, range 64, base 0x80000000, size 268435456, enabled > bar [20] = type I/O Port, range 32, base 0x1000, size 64, enabled However, a few days ago I upgraded it from 13.3 to 14.1 and it started giving troubles (usually 2-3 times a day, while performing normal desktop work). When in happens, the screen might get garbled in different ways, it might be unresponsive or not, but in the end I have to press Ctrl-Alt-Backspace and start over. What I see in the first console might be (please forgive any little mistake, as I need to rewrite it from a picture): > drmn0: [drm] GPU HANG: ecode 9:1:85dffdfb, in MainThread [100791] > drmn0: [drm] Resetting rcs0 for preemption time out > drmn0: [drm] Xorg[100791] context reset due to GPU hang or: > drmn0: [drm] Resetting rcs0 for CS error > drmn0: [drm] MainThread[100791] context reset due to GPU hang > drmn0: [drm] GPU HANG: ecode 9:1:00280001, in MainThread [100791] > drmn0: [drm] GPU HANG: ecode 9:1:85dfffff, in MainThread [100791] > drmn0: [drm] Resetting rcs0 for preemption time out > drmn0: [drm] Xorg[100791] context reset due to GPU hang I've seen a couple of bug reports, but those does not look the same to me. I'm using 2023Q3 port tree, so: > # pkg info|grep -E "(drm|xorg)" > drm-61-kmod-6.1.92 DRM drivers modules > drm-kmod-20220907_3 Metaport of DRM modules for the linuxkpi-based KMS components > gpu-firmware-kmod-20240401,1 Firmware modules for the drm-kmod drivers > libdrm-2.4.122,1 Direct Rendering Manager library and headers > xorg-fonts-truetype-7.7_1 X.Org TrueType fonts > xorg-server-21.1.13,1 X.Org X server and related programs > xorgproto-2024.1 X Window System unified protocol definitions Is this something known? Something obvious to look into? Are the instructions for reporting this still relevant, here? > https://wiki.freebsd.org/Intel_GPU bye & Thanks av.