Date: Sat, 19 Oct 2019 10:16:15 +0900 (JST) From: Masachika ISHIZUKA <ish@amail.plala.or.jp> To: freebsd-current@freebsd.org Subject: Re: DRM-current-kmod is still a problem at r353339 Message-ID: <20191019.101615.1133718013110043927.ish@amail.plala.or.jp> In-Reply-To: <20191018.214449.616506450481592816.ish@amail.plala.or.jp> References: <689d53378dcca22adb29aa23f03e8e1b@neelc.org> <25593555-6452-0933-d0fe-0459425cde55@delphij.net> <20191018.214449.616506450481592816.ish@amail.plala.or.jp>
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. Thank you very much. Now, it is good working r353722M(1300053) on 3 machines. (1) DELL Vostro 3267 desktop (core i5-7500) Both patches are required. (2) DELL Vostro 3568 notebook (Celeron 3865U) Both patches are required. (3) DELL XPS 12 9Q33 notebook (core i7-4500U) At least mjg@'s pmap-fict-invl patch is required. -- Masachika ISHIZUKA
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191019.101615.1133718013110043927.ish>