Date: Sun, 20 Oct 2019 09:45:53 +0300 From: Yuri Pankov <yuripv@yuripv.net> To: freebsd-current@freebsd.org Subject: Re: DRM-current-kmod is still a problem at r353339 Message-ID: <7cb6ecd6-2dcd-92e4-75a3-5e5d34377ed6@yuripv.net> In-Reply-To: <25593555-6452-0933-d0fe-0459425cde55@delphij.net> 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> <25593555-6452-0933-d0fe-0459425cde55@delphij.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/18/2019 8:01 AM, Xin Li wrote: > 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. Confirmed that it worked for me too on P51. Sorry for offtopic, but do you see the console getting "stuck" after loading i915kms, i.e. for input to show you need to switch to another console and back?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7cb6ecd6-2dcd-92e4-75a3-5e5d34377ed6>