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

Have you patched with mjg_at_'s pmap-fict-invl.diff?  The panic seems to be
similar...

Cheers,

On Fri, Oct 18, 2019 at 2:01 AM Neel Chauhan <neel_at_neelc.org> wrote:

> This still panicks for me, but with a different error.
>
> https://i.postimg.cc/K8nxF57G/IMG-20191018-045338.jpg
>
> I really should be sleeping but can't because I have to use an older
> kernel to have working graphics. Thanks, Netflix for making my life
> harder.
>
> -Neel
>
> On 2019-10-18 01:01, 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_at_'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_at_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_at_freebsd.org mailing list
> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >>> To unsubscribe, send any mail to
> >>> "freebsd-current-unsubscribe_at_freebsd.org"
> >> _______________________________________________
> >> freebsd-current_at_freebsd.org mailing list
> >> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> >> To unsubscribe, send any mail to
> >> "freebsd-current-unsubscribe_at_freebsd.org"
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > https://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to
> > "freebsd-current-unsubscribe_at_freebsd.org"
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>