high cpu use after x11 updates

[Niclas Zeising]

On 2019-06-20 00:32, AN wrote:
> 
> 
> On Tue, 18 Jun 2019, Niclas Zeising wrote:
> 
>> Date: Tue, 18 Jun 2019 20:08:33 +0200
>> From: Niclas Zeising <zeising+freebsd at daemonic.se>
>> To: AN <andy at neu.net>, freebsd-x11 at freebsd.org
>> Subject: Re: high cpu use after x11 updates
>>
>> On 2019-06-17 01:17, AN wrote:
>>> Hi:
>>>
>>> FreeBSD FBSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #93 r349104: Sun 
>>> Jun 16 08:41:26 EDT 2019 
>>> root at FBSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL amd64 1300031
>>>
>>> After recent updates to several x11 ports, the process 
>>> /usr/local/bin/X seems to be using a lot of cpu resources.  
>>> Historically I seem to remember X using something less than 1% cpu on 
>>> this machine.  Here are the related ports that were updated recently:
>>>
>>>      + x11/libxshmfence (libxshmfence-1.2_4 -> libxshmfence-1.3)
>>>      + x11/libXext (libXext-1.3.3_3,1 -> libXext-1.3.4,1)
>>>      + x11/libXdamage (libXdamage-1.1.4_5 -> libXdamage-1.1.5)
>>>      + x11/libXcursor (libXcursor-1.1.15_2 -> libXcursor-1.2.0)
>>>      + x11-toolkits/libXmu (libXmu-1.1.2_5,1 -> libXmu-1.1.3,1)
>>>      + x11/libXrandr (libXrandr-1.5.1_2 -> libXrandr-1.5.2)
>>>      + x11/libXvMC (libXvMC-1.0.10_2 -> libXvMC-1.0.11)
>>>      + x11/sessreg (sessreg-1.1.1 -> sessreg-1.1.2)
>>>      + x11/libxkbfile (libxkbfile-1.0.9_2 -> libxkbfile-1.1.0)
>>>      + x11/xkeyboard-config (xkeyboard-config-2.24_1 ->
>>>          xkeyboard-config-2.27)
>>>      + x11/libxkbcommon (libxkbcommon-0.8.0_1 -> libxkbcommon-0.8.4)
>>>      + x11/libXxf86dga (libXxf86dga-1.1.4_5 -> libXxf86dga-1.1.5)
>>>      + x11/libXcomposite (libXcomposite-0.4.4_5,1 ->
>>>          libXcomposite-0.4.5,1)
>>>
>>> I rebuilt the xserver and am still seeing the same behavior.  Are 
>>> there any other ports I need to rebuild?  What other info can I 
>>> provide?  Any suggestions would be appreciated.
>>>
>>> Also, I am using:
>>> nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX 
>>> platforms  390.87  Tue Aug 21 15:53:31 PDT 2018
>>> nvidia0: <GeForce GT 710> on vgapci0
>>> and running compiz.
>>>
>>>
>>>  From top:
>>> 21865 root         21   -1  6528M   300M select   4  28:35   6.55% 
>>> /usr/local/bin/X :0 -auth /root/.serverauth.199
>>>
>>> Thanks in advance for any advice.
>>
>> Hi!
>> is you update just the ports, or also the base system at the same time?
>> Any chance you can try to undo either the ports update or the base 
>> system update, and see if the problem persists?
>> Regards
>>
> 
> Niclas:
> 
> Unfortunately, after a full update I see the same behavior.
> 
> Buildworld/buildkernel/installworld to:
> FreeBSD FBSD_13 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r349192: Wed Jun 19 
> 10:18:31 EDT 2019 
> root at FBSD_13:/usr/obj/usr/src/amd64.amd64/sys/MYKERNEL  amd64 1300032
> 
> also rebuilt:
> xorg-server
> xwayland
> nvidia-driver
> 
> 43235 root         21   -1  6239M    40M select   0   0:04   8.51% 
> /usr/local/bin/X :0
>     12 root        -96    -      0   752K WAIT     2   0:01   1.18% 
> [intr{irq62: vgapci0}]
> 57791 root         20    0   110M    52M select  10   0:01   0.69% 
> mate-terminal --sm-client-id 104f4
> 59442 root         20    0    98M    60M select   9   0:11   0.65% 
> compiz --replace --sm-disable --ig
> 69803 root         20    0    14M  4224K CPU3     3   0:00   0.16% top 
> -i -P -H -S -s 1 -a
> 
> # svnlite info
> Path: .
> Working Copy Root Path: /usr/ports
> URL: svn://svn.freebsd.org/ports/head
> Relative URL: ^/head
> Repository Root: svn://svn.freebsd.org/ports
> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
> Revision: 504486
> Node Kind: directory
> Schedule: normal
> Last Changed Author: linimon
> Last Changed Rev: 504486
> Last Changed Date: 2019-06-18 10:34:06 -0400 (Tue, 18 Jun 2019)
> 
> 
> Any suggestions are appreciated.

The next step is to figure out which change caused the issue.  If 
possible, roll back to the FreeBSD version you had before the issue 
started, or roll back the updated packages one by one until the issue is 
gone, to see which update is causing the issue.
Regards
-- 
Niclas