Date: Tue, 21 Feb 2023 19:15:24 +0000 From: bugzilla-noreply@freebsd.org To: x11@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-7141-eKtI9fE9pv@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-266315-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-266315-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=3D266315 --- Comment #31 from jakub_lach@mailplus.pl --- (In reply to Paul Dufresne from comment #30) Thanks, but this is hardly a solution.=20 Note, that I had working/stable accelerated intel driver for years prior to drm-510-kmod. I've already experienced old drm, newcons and drm2/kms2 introduction.=20 At that point, intel was more or less stable for me. Last crashes (and corruption) I had was related to forcing 'sna' acceleration method.=20 At some point, I've used drm-legacy-kmod, as I had believed at that time it= was last one supporting GM45. It was also stable iirc. I could live with some hang ups as long as they did not crash the system (p= rior to drm-510-kmod). --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-266315-7141-eKtI9fE9pv>