Date: Mon, 20 Feb 2023 13:06:37 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 266315] linuxkpi panic after recent updates (13.1-STABLE #0 stable/13-9cbba5950: Wed Sep 7 23:42:41 CEST 2022) Message-ID: <bug-266315-227-7dqum70TUP@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266315-227@https.bugs.freebsd.org/bugzilla/> References: <bug-266315-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266315 --- Comment #15 from Oleh Vinichenko <moonlapse81@gmail.com> --- now, that i updated to FreeBSD-CURRENT for testing purposes, i had less frequents hangs with master branch of drm-kmod ( which was linux-5.12.x ). Now, after, drm-kmod update to linux-5.15.x hangs and GPU resets returned. System freezes and only hard reset required to bring system back. Only thing i seeing is: drmn0: [drm] GPU HANG: ecode 6:1:0ffe0000, in Renderer [101196] drmn0: [drm] Resetting chip for stopped heartbeat on rcs0 drmn0: [drm] Renderer[101196] context reset due to GPU hang Notice, that i already reported this in: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D259670 To me this looks like a grave issue, which is not fully addressed and simple updates to newer linux graphic stack would not help. Since, it is really ha= rd to get meaningful information and ability to debug by regular users, i prop= ose this issues, which are quite common, to be reported to FreeBSD foundation/c= ore developers as it looks like subtle bug within FreeBSD linuxkpi layer. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266315-227-7dqum70TUP>