Date: Wed, 19 Nov 2014 13:49:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 195165] New: Kernel with drm panics, when xorg tries to load new drm-modules Message-ID: <bug-195165-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195165 Bug ID: 195165 Summary: Kernel with drm panics, when xorg tries to load new drm-modules Product: Base System Version: 10.1-RELEASE Hardware: amd64 OS: Any Status: Needs Triage Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: mi@ALDAN.algebra.com Created attachment 149586 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149586&action=edit core.txt file from the panic I had a fairly solid system running 9.x and decided to upgrade to 10.1. The rebuild went smoothly, the same kernel-config was built cleanly. I rebuilt all of the X11-ports and tried starting xdm as usual. The machine rebooted after a panic (see attachment for more details): panic: make_dev_credv: bad si_name (error=17, si_name=dri/card0) Apparently, this is problem has been known to the x11@ folks for a while -- when the new X11-drivers try to load DRM2, the kernels with the "old" DRM in them will panic: http://lists.freebsd.org/pipermail/freebsd-stable/2014-September/079868.html While the recommended work-around -- remove "device drm" and "device radeondrm" from kernel config -- helped me get going, it should not be necessary: 1. There must be no panic 2. If DRM2 can not coexist with DRM, it must check for the condition and report an error. 3. If DRM2 is a replacement for DRM, why not remove the old "device" altogether? No doubt, the x11@ group is aware of the problem. This ticket is intended to help them track it. -- 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-195165-8>