Re: r353072 > r353427 > r353709

2019-10-20 Thread Clay Daniels
On 10/20/19 3:42 AM, Gary Jennejohn wrote: This is a patch to a file used in the port itself, not to the kernel sources under /usr/src/sys. This should be pretty clear from this line in the referenced link to the posting in freebsd-current: # cat files/patch-linuxkpi_gplv2_src_linux__page.c

Re: DRM-current-kmod is still a problem at r353339

2019-10-20 Thread Yuri Pankov
On 10/21/2019 4:14 AM, Neel Chauhan wrote: For me, the following code is still necessary for me (HP Spectre x360 2018), which is the remaining parts of the patches not committed if you are using a recent kernel. I don't know about you all ThinkPad users, it should still apply as it's Intel in

Re: DRM-current-kmod is still a problem at r353339

2019-10-20 Thread Neel Chauhan
For me, the following code is still necessary for me (HP Spectre x360 2018), which is the remaining parts of the patches not committed if you are using a recent kernel. I don't know about you all ThinkPad users, it should still apply as it's Intel in general not just HP or Lenovo. Without

Re: r353072 > r353427 > r353709

2019-10-20 Thread Gary Jennejohn
On Sat, 19 Oct 2019 22:07:52 -0500 Clay Daniels wrote: > On 10/19/19 4:54 AM, Evilham wrote: > > Have you seen the recent threads about this? > > Particularly this with some steps that worked-for-me (tm): > > https://lists.freebsd.org/pipermail/freebsd-current/2019-October074660.html > > > > --

Re: DRM-current-kmod is still a problem at r353339

2019-10-20 Thread Yuri Pankov
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