Date: Thu, 26 Mar 2015 22:00:30 +0100 (CET) From: "Jakob Alvermark" <jakob@alvermark.net> To: "freebsd-x11" <freebsd-x11@freebsd.org>, "FreeBSD Current" <freebsd-current@freebsd.org> Subject: Re: [Call for testers] DRM device-independent code update to Linux 3.8 (take #2) Message-ID: <18597.85.229.93.187.1427403630.squirrel@webmail.alvermark.net> In-Reply-To: <5510A1E3.9040603@selasky.org> References: <54F636B3.90701@FreeBSD.org> <20150307111305.10d7678d@kan> <CAOFF%2BZ3ZDjt4nTcyV%2B9_GZvexsbFBYz84q-J79tcUue9jx6NEQ@mail.gmail.com> <5510A1E3.9040603@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, March 24, 2015 00:29, Hans Petter Selasky wrote: > Hi, > > > Without the attached kernel patch(es), Xorg starts consuming alot of CPU > and becomes very unresponsive and unusable. > > Using ktrace reveals that X-org is issuing DRM_IOCTL_MODE_GETCONNECTOR > over and over again with no apparent reason. It doesn't happen when using a > simple window manager like blackbox. I was not able to use XFCE4 (9-stable > userland) with 11-current kernel at all, after the latest DRM2 kernel > updates. It worked fine before the update. > > I'm not sure what is causing it. Going through the new DRM2 code > revealed that a mode sorting function did not take all parameters like > interlaced or not into account, causing the mode list to be reshuffelled > every time a new mode scan was done. Not sure if Xorg cares about this > though. I got the same problem with XFCE4, Xorg at 100% CPU. Applied the patch and it works again. Jakob
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?18597.85.229.93.187.1427403630.squirrel>