DRM-current-kmod is still a problem at r353339

[Neel Chauhan]

However, the patch to drm-kmod doesn't work for me. I tried both 
drm-devel-kmod and drm-current-kmod.

https://i.imgur.com/81JvaOO.jpg

-Neel

===

https://www.neelc.org/

On 2019-10-17 17:35, Eirik Øverby wrote:
> On 10/17/19 11:29 PM, Eirik Øverby wrote:
>> On 10/17/19 10:31 PM, Niclas Zeising wrote:
>>> On 2019-10-17 21:53, markj at freebsd.org wrote:
>>>> On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote:
> ......
>>>> I believe it was the recent work on the vm page busy state, r353539
>>>> specifically.  This patch should fix it; we don't yet have a
>>>> __FreeBSD_version number bump on which to gate the patch.
> .......>>
>>> Hi!
>>> Hopefully someone can confirm that this patch to drm-current-kmod or 
>>> drm-devel-kmod fixes the issue.  I won't be able to work on this 
>>> before the weekend at the earliest, I'm afraid.
>>> Mark, is it possible to get a belated version bump for this fix, and 
>>> what changed to require it?
>> 
>> Built, rebooting ... Will hopefully check back in soon.
> 
> And tada, I'm back. That seemed to do the trick. Thanks!
> 
> /Eirik
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to 
> "freebsd-current-unsubscribe at freebsd.org"