Re: error installing world from R/O src and obj

2019-10-21 Thread Andriy Gapon
On 22/10/2019 08:46, Andriy Gapon wrote: > On 12/10/2019 15:23, Dimitry Andric wrote: >> By any chance, did you upgrade src from before r353358 (llvm 9.0.0 >> import) to a revision after it, and then did an incremental build? >> Maybe, for some reason the depend stage is then not run, which could >

Re: error installing world from R/O src and obj

2019-10-21 Thread Andriy Gapon
On 12/10/2019 15:23, Dimitry Andric wrote: > By any chance, did you upgrade src from before r353358 (llvm 9.0.0 > import) to a revision after it, and then did an incremental build? > Maybe, for some reason the depend stage is then not run, which could > lead to this scenario. I don't have a record

FreeBSD CI Weekly Report 2019-10-20

2019-10-21 Thread Li-Wen Hsu
(Please send the followup to freebsd-testing@ and note Reply-To is set.) FreeBSD CI Weekly Report 2019-10-20 === Here is a summary of the FreeBSD Continuous Integration results for the period from 2019-10-14 to 2019-10-20. During this period, we have: * 2475 buil

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

2019-10-21 Thread Niclas Zeising
On 2019-10-21 11:08, Yuri Pankov wrote: Niclas Zeising wrote: On 2019-10-20 08:45, Yuri Pankov wrote: 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_WAIT

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

2019-10-21 Thread Yuri Pankov
Niclas Zeising wrote: On 2019-10-20 08:45, Yuri Pankov wrote: 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

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

2019-10-21 Thread Niclas Zeising
On 2019-10-17 23:05, Mark Johnston wrote: On Thu, Oct 17, 2019 at 10:31:12PM +0200, Niclas Zeising wrote: On 2019-10-17 21:53, ma...@freebsd.org wrote: On Thu, Oct 17, 2019 at 03:03:51PM +0200, Niclas Zeising wrote: On 2019-10-16 18:57, Neel Chauhan wrote: While drm-current-kmod worked for a

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

2019-10-21 Thread Niclas Zeising
On 2019-10-21 09:01, Thomas Mueller wrote: from 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

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

2019-10-21 Thread Niclas Zeising
On 2019-10-20 08:45, Yuri Pankov wrote: 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

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

2019-10-21 Thread Thomas Mueller
from 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