Date: Wed, 30 Sep 2020 17:48:25 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 229995] [panic, regression] radeonkms "timed sleep before timers are working" Message-ID: <bug-229995-227-M6VTedI3Vf@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-229995-227@https.bugs.freebsd.org/bugzilla/> References: <bug-229995-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=3D229995 --- Comment #3 from Andrew Daugherity <andrew.daugherity@gmail.com> --- (In reply to Alexey Dokuchaev from comment #2) I'm running 12.1 on a similar server (also an embedded Radeon R100) and usi= ng the drm-kmod package. It was installed as 12.0, which had the same issue w= ith the included drivers as 11.x, as noted in comment 1. However, prompted by = the deprecation notice I installed drm-legacy-kmod. I don't recall if I ever t= ried loading that via /boot/loader.conf, but as the package message suggests usi= ng the kld_list setting in rc.conf, I'm following that method. (Although it neglects to mention that you must also load drm2.ko that way [1], or else it will use the kernel's [deprecated] drm2.ko with the radeonkms from the pack= age, and still generate deprecation warnings.) I've since switched to the non-legacy drm-kmod package, which also works fi= ne, at least in 16 bpp modes. Other depths had issues with both the legacy/ker= nel drivers (they defaulted to 8 bpp, which was grayscale for some reason; 24 b= pp had an incorrect console palette) and the new ones (display corruption in s= ome depths; sorry, I forget which, but at least the new drivers default to 16 b= pp, which works). [ Aside: the vt(4) man page only mentions kern.vt.fb.default_mode=3D"<X>x<Y= >" and nothing about setting depth, which is apparently done by appending it to the resolution, e.g. "1280x1024-16". I found that in a mailing list; seems lik= e an oversight to not include it in the man page... ] So... while it _is_ a bug that it panics if you load the drivers on boot, loading the drivers later is an easy workaround (and maybe even the preferr= ed method?), so it's not that big of a problem. I was unaware of the kld_list rc.conf setting until the package told me to use it -- that's a cleaner met= hod, for sure.=20 [1] https://github.com/FreeBSDDesktop/drm-legacy/issues/7#issuecomment-658407985 --=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-229995-227-M6VTedI3Vf>