Date: Thu, 17 Oct 2019 22:01:09 -0700 From: Xin Li <delphij@delphij.net> To: Neel Chauhan <neel@neelc.org>, =?UTF-8?Q?Eirik_=c3=98verby?= <ltning@anduin.net> Cc: freebsd-current@freebsd.org, mjg@freebsd.org Subject: Re: DRM-current-kmod is still a problem at r353339 Message-ID: <25593555-6452-0933-d0fe-0459425cde55@delphij.net> In-Reply-To: <689d53378dcca22adb29aa23f03e8e1b@neelc.org> References: <CAGudoHG_aAcqOfSi0GCW5-yw=6RcEXB0dz72mkgdJoz0guJMHA@mail.gmail.com> <7ca3b30a-81f6-f79d-1486-7fd29765646f@acm.org> <CAGudoHE755ig7KGuzq8uNY01K2Jcf-MKBjCp8kbpJAoiHdbQMA@mail.gmail.com> <99c89ca0-462c-f4c7-fa07-6f61e9d39d66@acm.org> <f2e7c4b4c236ee694f277d78479cb6ee@neelc.org> <CAGudoHGwmp=vNwOy2W22rjx_mQj1nkbdYzuLfayM7O0vn4keeA@mail.gmail.com> <bb951f83-6a50-48ce-8efa-b8fa92a9840e@yggdrasil.evilham.com> <CAGudoHGoikyZudFSxYjypF8EL24BPxBTPQjAnCKTe%2Bvg3DJiWQ@mail.gmail.com> <bb4f31fcb7f06059f1d9fe391b119661@neelc.org> <3bb2e410-51dd-bc3f-7660-41a4683551b3@daemonic.se> <20191017195347.GB6447@raichu> <53ff1ac5-c7e8-1b6c-bd43-481eaef61120@daemonic.se> <f0f64057-2d8a-9ec2-9d01-91e2265f8a91@anduin.net> <72d67f0a-aeef-1c06-2b12-9351a1f52060@anduin.net> <689d53378dcca22adb29aa23f03e8e1b@neelc.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Another (semi-fixed!) data point -- I can confirm that with if (vm_page_sleep_if_busy(page, "linuxkpi")) -> if (!vm_page_busy_acquire(page, VM_ALLOC_WAITFAIL)) change and mjg@'s earlier patch at https://people.freebsd.org/~mjg/pmap-fict-invl.diff (please commit it) , the latest drm-v5.0 branch of drm-current-kmod worked just fine with Intel HD Graphics P630 on Lenovo P51. On 2019-10-17 18:37, Neel Chauhan wrote: > 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@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@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to >> "freebsd-current-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25593555-6452-0933-d0fe-0459425cde55>