Date: Sat, 17 Oct 2020 09:11:58 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 250193] Kernel panic loading DRM kmods Message-ID: <bug-250193-7141-XKI4zTqHBd@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-250193-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-250193-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=3D250193 Hans Ottevanger <hans@beastielabs.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hans@beastielabs.net --- Comment #5 from Hans Ottevanger <hans@beastielabs.net> --- (In reply to Jason W. Bacon from comment #4) I can confirm that this also happens on my Core-2 Quad system, with a Radeon HD-6450 based graphics card. When using the drm-fbsd12.0-kmod-4.16.g20200221 package on 12.1-RELEASE-p10 everything works as usual. After upgrading to 12.2-RC3 the system panics immediately on loading radeonkms.ko. I still get a stacktrace, but it is followed by a hard hangup, so no core dump is made. It does not matter whether I put kld_list=3D"/boot/modules/radeonkms.ko" in /etc/rc.conf or run kldload /boot/modules/radeonkms.ko directly from the shell. When I build drm-fbsd12.0-kmod-4.16.g20200221 locally from ports, the probl= em does not occur and the systems functions normally. I wonder what an end user gets to see when installing 12.2-RELEASE once it = is available and then attempts to use the package. --=20 You are receiving this mail because: You are on the CC list for the bug. 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-250193-7141-XKI4zTqHBd>