[Bug 954433] New: Xorg 100% cpu load, on recently updated (to Leap 42.1) x64 systems, idling at Xorg login page
http://bugzilla.opensuse.org/show_bug.cgi?id=954433 Bug ID: 954433 Summary: Xorg 100% cpu load, on recently updated (to Leap 42.1) x64 systems, idling at Xorg login page Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: abittner@opensuse.org QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- 981 root 20 0 285336 52216 34828 R 99.19 0.342 4393:45 Xorg I have just found a second system amongst my opensuse leap ones, that is now displaying 100% cpu load for the Xorg process. I ssh-d to the machine it it was taking a long time until the login finished and the shell displayed. Top shows the following. I had the same behavior on a different machine just yesterday. Was also a Leap one. That one was a brand new 13.2 x64 machine only originally installed November 2014 and then upgraded to leap. This machine here is an opensuse one with a longer upgrade history. I can just systemctl stop display-manager.service and the cpu hogging stops, but why is this happening? system is not being used directly physically for X, only for other purposes. Any way to see what is going on with that process exactly? My machines are amd/radeon based. Any more stuff to submit? systemctl status display-manager.service display-manager.service - X Display Manager Loaded: loaded (/usr/lib/systemd/system/display-manager.service; disabled) Active: active (running) since Wed 2015-11-04 23:02:32 CET; 5 days ago Main PID: 961 (kdm) CGroup: /system.slice/display-manager.service +- 961 /usr/bin/kdm +- 981 /usr/bin/Xorg -br :0 vt7 -nolisten tcp -seat seat0 -auth /var/lib/kdm/AuthFiles/A:0-Wtm7Bb +-1293 -:0 +-1295 /usr/lib64/kde4/libexec/kdm_greet Nov 04 23:02:32 tuxr01 kdm_config[962]: Multiple occurrences of section [Xdmcp] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. Nov 04 23:02:32 tuxr01 kdm_config[962]: Multiple occurrences of section [X-*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. Nov 04 23:02:32 tuxr01 kdm_config[962]: Multiple occurrences of section [X-*-Greeter] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. Nov 04 23:02:32 tuxr01 kdm_config[962]: Multiple occurrences of section [X-:*-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. Nov 04 23:02:32 tuxr01 kdm_config[962]: Multiple occurrences of section [X-:0-Core] in /usr/share/kde4/config/kdm/kdmrc. Consider merging them. Nov 04 23:02:32 tuxr01 kdm[961]: plymouth is running Nov 04 23:02:32 tuxr01 kdm[961]: plymouth is active on VT 7, reusing for :0 Nov 04 23:02:32 tuxr01 kdm[961]: plymouth should quit after server startup Nov 04 23:02:36 tuxr01 kdm[961]: Quitting Plymouth with transition Nov 04 23:02:36 tuxr01 kdm[961]: Is Plymouth still running? no Linux tuxr01 4.1.12-1-default #1 SMP PREEMPT Thu Oct 29 06:43:42 UTC 2015 (e24bad1) x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c1
--- Comment #1 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c2
--- Comment #2 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c3
--- Comment #3 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c4
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c5
--- Comment #5 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c6
--- Comment #6 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c7
--- Comment #7 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c8
--- Comment #8 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c9
andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c10
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c11
andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c13
andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c15
--- Comment #15 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c17
andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c18
--- Comment #18 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c21
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c22
andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c23
--- Comment #23 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c24
--- Comment #24 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c25
--- Comment #25 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c26
--- Comment #26 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c27
--- Comment #27 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c28
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c29
andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c30
Egbert Eich
the file it created is like 600kilobytes
I should have mentioned this.
it eventually stoppd logging or some process terminated
That's fine. What we need happens at startup.
do you need the whole file?
No.
or only some lines containing socket info?
It's there already: [..]
socket(PF_LOCAL, SOCK_STREAM|SOCK_CLOEXEC, 0) = 6 connect(6, {sa_family=AF_LOCAL, sun_path="/var/run/dbus/system_bus_socket"}, 33) = 0 socket(PF_NETLINK, SOCK_RAW|SOCK_CLOEXEC|SOCK_NONBLOCK, NETLINK_KOBJECT_UEVENT) = 14
This looks like on mine. This points to an issue in libdbus. The Xserver should handle it gracefully, however libdbus should not close the socket behind the Xserver. @Andreas, are you using a specific setup? Looks like you are using a KDE installation - do you still have kdm running on Leap 42.1 (maybe due to the update)? I'm just curious what condition could have triggered this. Anyway, adding the Dbus maintainer and bugowner. @Fridrich, do have an idea about this behavior? (If needed, i can give you the source file with the dbus interface). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c31
andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c32
--- Comment #32 from Egbert Eich
What do you mean by "still have kde". Isnt KDE a supported or normal scenario on OpenSuSE? I think my most OpenSuSE boxes are updated ones from long ago in the past. Mostly. But some were opensuse 13.2 to Leap 42.1 upgrade, and one of those machines did have this xorg cpu load bug.
I said "do you still have kdm running" ie. kd>m< not kde>e<. New installations of KDE use sddm - not kdm any more. It is possible that the 13.2 to Leap 42.1 upgrade led to the exact situation you are seeing. However this is very little to go by to reproduce this problem. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c33
--- Comment #33 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c34
andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c35
--- Comment #35 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c36
--- Comment #36 from Egbert Eich
side notes: I researched a bit into sddm and kdm, and there were some discussions that read that one need to simply switch the "kdm" to DISPLAYMANAGER="sddm" in sysconfig/displaymanager config-file
although the comments in that config file only speak about xdm and kdm and gdm, but no sddm is anywhere mentioned.
There are so many DMs now days and new ones get added that there is no chance keeping track. it should read "(kdm/xdm/gdm/...).
I even removed all the kdm rpm packages and even the sddm ones via rpm -e and reinstalled the sdm stuff via zypper in.
You should not have to uninstall kdm, I have several DMs installed in parallel on my test box.
the displaymanager config file never changed after these procedures, it had kdm as the setting.
Right, what you did is pretty much an update procedure. Here configuration settings of previous versions are changed very conservatively. Uninstalling packages is something that may require some user intervention at some other place. Since you can have several DMs installed we do not edit entries in this file.
So when i changed that to sddm it now gives errors and fails to load the sddm stuff.
I dont wana pollute this bugreport do I need to file another one or what is the or an official way to switch between these xdm kdm and sddm and all
Are you sure the sddm stuff got installed correctly? Moreover, for this bug you should not have to deinstall kdm and switch to sddm instead. There is a real issue here and I'm looking for a way to reproduce it. If we fix it we need some test bed to try out the fixes. Without this, all our efforts would be wasted. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c37
--- Comment #37 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c38
--- Comment #38 from Egbert Eich
I revistited this machine again today, and oddly enough there was again a kdm process as well as Xorg running on it. displaymanager=kdm was the setting.
I changed this variable to sddm now and restarted display-manager.service and ps now shows sddm processes
Do you see a login screen? I have no idea why sddm isn't starting an Xserver on your machine, usually it does...
But there is no running Xorg process now. Is this normal? Does Xorg not run with sddm during that user-login screen?
anyways, back to this bug, should I revert and set it back to kdm and keep it that way for this bug to continue helping you with this machine?
Yes, please. I cannot promise you when I will get to it. But once I have a fix it needs to be tested - ATM you are the only one who can do this. Since you don't need the system, you disable the display manager when you don't do tests so it doesn't run high all the time. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c39
--- Comment #39 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c40
--- Comment #40 from Egbert Eich
No problem, just reply back in this bugreport when you need me to do more stuff. Most or all of these machines I am using with opensuse are actually not being used for desktop activity, and mostly I can do remote work only. So I dont know what the machine or if it displays anything.
Ok, so you don't even have a monitor connected. In this case you should probably disable the display manager or boot into the multi-user.target (aka runlvl 3).
So just to sum it up, most likely as you found out, it is a kdm related (e.g. upgraded opensuse 13.2 default install to leap 42.1, the kdm stuff stays, and messes up the xorg and related stuff related to libdbus.
And you cannot repro this scenario? Clean 13.2/x64 to leap/42.1? Maybe it is
Don't know, haven't tried this update scenario. Will do maybe.
also related to connected or disconnected (turned off or no at all) monitors with these opensuse machines, as my machines are either connected to some keyboard/video/mouse via some kvm switch sharing input/display device with some other (e.g. windows) machine or they dont have a monitor connected at all (some of them).
Maybe this helps.
Ok, thanks for the info, will give it a try! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c41
--- Comment #41 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c42
--- Comment #42 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c43
--- Comment #43 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c44
--- Comment #44 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c45
--- Comment #45 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c46
--- Comment #46 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c47
--- Comment #47 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c48
--- Comment #48 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c49
--- Comment #49 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c50
--- Comment #50 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c51
--- Comment #51 from andreas bittner
http://bugzilla.opensuse.org/show_bug.cgi?id=954433
http://bugzilla.opensuse.org/show_bug.cgi?id=954433#c52
--- Comment #52 from Egbert Eich
just verified it again on some other system. you are right, as soon as one restarts the dbus
sudo systemctl restart dbus.service
the xorg starts to consume 100% cpu
then one needs to issue a
sudo systemctl restart display-manager.service
to make it calm down again.
Heh, you probably found a reproducer so that I can look into this more deeply :) -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com