Date: Mon, 21 Oct 2019 11:38:32 +0200 From: Niclas Zeising <zeising+freebsd@daemonic.se> To: Yuri Pankov <yuripv@yuripv.net>, freebsd-current@freebsd.org Subject: Re: DRM-current-kmod is still a problem at r353339 Message-ID: <1452ada7-53e7-dc44-de3e-a508110a5ff5@daemonic.se> In-Reply-To: <38b1cc56-8d39-b1ab-30fe-b2568af6d304@yuripv.net> References: <CAGudoHG_aAcqOfSi0GCW5-yw=6RcEXB0dz72mkgdJoz0guJMHA@mail.gmail.com> <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> <7cb6ecd6-2dcd-92e4-75a3-5e5d34377ed6@yuripv.net> <81907442-b17d-c975-75a7-84704e440568@daemonic.se> <38b1cc56-8d39-b1ab-30fe-b2568af6d304@yuripv.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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")) >>>> =C2=A0 -> 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=20 >>>> 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=20 >>> loading i915kms, i.e. for input to show you need to switch to another= =20 >>> console and back? >> >> This is a known regression with drm-devel-kmod, and one of the reasons= =20 >> it hasn't made it past devel yet. >=20 > Got it, thanks.=C2=A0 I'm only seeing it on the lenovo laptop with hd63= 0 and=20 > not on the intel nuc with iris plus 650 graphics, so I thought it's tha= t=20 > laptop specific. It is a strange error. I'm seeing it on my laptop (an x270) but only on=20 the internal screen. If I connect an external screen using HDMI that=20 screen works, but still not the internal screen. Others aren't having=20 this issue at all. https://github.com/FreeBSDDesktop/kms-drm/issues/151 has some more (not=20 very much more) info. Regards --=20 Niclas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1452ada7-53e7-dc44-de3e-a508110a5ff5>