Date: Sun, 26 Apr 2020 07:11:44 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 236003] x11-drivers/xf86-video-intel: update to 2019-12-09 snapshot and refactor Message-ID: <bug-236003-7141-mnF0wC0WkS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-236003-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-236003-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D236003 Jan Beich <jbeich@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #211836|0 |1 is obsolete| | --- Comment #47 from Jan Beich <jbeich@FreeBSD.org> --- Created attachment 213793 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D213793&action= =3Dedit v8 - More upstream SNA bugfixes (In reply to Taku YAMAMOTO from comment #46) > It appears that Xorg begins either spinning inside drm ioctl or > hopping U-K back and forth after massive texture operations. Does it happen as soon as Xorg is started? If not which application causes = it. Can you attach ktrace(1) or truss(1) and try decode the ioctl Xorg invokes = in a busy loop? What's U-K? What do you mean by hopping? CPU usage spikes in top(1)? Did you see anything unusual in Xorg.log? Mainly look for (EE) lines. Does enablig DRI3 in xorg.conf help? xf86-video-intel defaults to DRI2 unli= ke modesetting. For me xf86-video-intel works fine as it did months ago. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-236003-7141-mnF0wC0WkS>