On Tue, 19 Feb 2019 11:18:07 -0800 Steve Kargl <sgk_at_troutmask.apl.washington.edu> wrote: > On Tue, Feb 19, 2019 at 06:59:26PM +0000, Johannes Lundberg wrote: >> On 2/19/19 5:35 PM, Steve Kargl wrote: >>> My Dell Latitude D530 running i386 freebsd, which used the >>> i915kms.ko now locks up solid with drm-legacy-kmod. The PAE vs >>> non-PAE i386/conf/pmap.h merger in r342567 broke drm-legacy-kmod. >>> It seems that Niclas has provided a patch that fixes the building >>> of drm-legacy-kmod. >>> >>> Doing a bisection on /usr/src commits is fairly slow as it >>> takes a day to build world/kernel and the minimum set of ports >>> need to fire up Xorg. r343543 and earlier appear to work fine >>> with drm-legacy-kmod. >> >> So it's not only a build error, it's also a runtime bug that would have >> happened even with drm2 in base? Hmm.. > > It appears that that's the case. The likely candidates > are r343564(+65 for missing header), r343566, and r343567. That last commit added hw.above4g_allow tunable. Does it help if you set this to 0 in /boot/loader.conf? Also, it's worth trying drm-current-kmod if you haven't done so recently. If you did try already what were the problems?Received on Wed Feb 20 2019 - 15:07:43 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:20 UTC