Date: Thu, 11 Jun 2020 15:31:36 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 247166] graphics/drm-devel-kmod: panic with i915kms on -current Message-ID: <bug-247166-7141-ZOXteDdCbo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-247166-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-247166-7141@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=3D247166 Vladimir Kondratyev <wulf@freebsd.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wulf@freebsd.org --- Comment #5 from Vladimir Kondratyev <wulf@freebsd.org> --- The panic is easy reproducible on KabyLake. All you need is to run guc firm= ware or vp8enc from multimedia/libva-utils. Both of them trigger it instantly. I workarounded it with updating linux_reservation.c to up to date version (really to 5.3) and moving critical section start in reservation_object_add_shared_fence() routine down to RCU_INIT_POINTER macr= o. There were lot of dma_fence changes in 5.0-5.4 timeframe, so it may have se= nse to start fixing the bug after drm-kmod reaches v5.4 --=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-247166-7141-ZOXteDdCbo>