Bug 485056

Summary:	radeon: Xorg at 100%CPU whenever using multiple logins (ES1000)
Product:	[openSUSE] openSUSE 11.1	Reporter:	Joachim Reichelt <Joachim.Reichelt>
Component:	X.Org	Assignee:	E-mail List <xorg-maintainer-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <xorg-maintainer-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	markgray+to-suse, sndirsch, wstephenson
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	tar to define X11 installation X11 info of radeon machine

Description Joachim Reichelt 2009-03-13 08:33:58 UTC

User-Agent:       Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.1b4pre) Gecko/20090311 Shiretoko/3.1b4pre

There are three users loged in at :0 :1 :2
# who
the08    :0           Feb 18 10:12 (console)
bkl07    :1           Feb 20 14:03 (localhost)
jgr08    :2           Mar 12 15:12 (localhost)
The not visible displays eat all cpu:
19766 root      20   0 92484 4984 1116 S   89  0.5  20434:19 /usr/bin/Xorg -br -nolisten tcp :1 vt8 -auth /var/lib/xdm/authdir/authfiles/A:1-qgBPxw
 3770 root      39  19 53080 7948 1252 R   67  0.8  31154:54 /usr/bin/Xorg -br :0 vt7 -auth /var/lib/xdm/authdir/authfiles/A:0-CD6pOr


Reproducible: Always

Steps to Reproduce:
1.login on 0:
2.login on 1:
3.login on 2:
Actual Results:  
see Details

Expected Results:  
no Xorg activiti at all on unused idle desktops

Comment 1 Mark Gray 2009-03-13 10:24:05 UTC

Please attach the information requested on the webpage:

http://en.opensuse.org/Bugs:X

Comment 2 Joachim Reichelt 2009-03-13 11:21:47 UTC

Created attachment 279383 [details]
tar to define X11 installation


Xorg.0.log  Xorg.0.log.old  Xorg.1.log  Xorg.1.log.old  Xorg.2.log  Xorg.2.log.old  hwinfo-gfx.txt  xorg.conf


Sorry, I didn't see, that this is needet.

And this is, what is installed:
# rpm -qa | grep x11
xorg-x11-libXau-7.4-1.23            
xorg-x11-libXt-devel-7.4-1.26       
xorg-x11-libxkbfile-devel-7.4-1.25  
xorg-x11-driver-video-7.4-19.4
xorg-x11-proto-devel-7.4-1.27
x11-tools-0.1-167.7
xorg-x11-libXt-7.4-1.26
xorg-x11-libxkbfile-7.4-1.25
xorg-x11-libXmu-7.4-1.26
xorg-x11-libXrender-7.4-1.24
xorg-x11-libXprintUtil-devel-7.4-1.26
xorg-x11-libSM-7.4-1.26
ConsoleKit-x11-0.2.10-60.16
xorg-x11-libXfixes-devel-7.4-1.24
xorg-x11-libXv-devel-7.4-1.25
xorg-x11-libXmu-devel-7.4-1.26
ghostscript-x11-8.62-31.39
xorg-x11-libICE-7.4-1.24
xorg-x11-util-devel-7.4-1.22
xorg-x11-libXau-devel-7.4-1.23
x11-input-synaptics-0.15.2-5.24
xorg-x11-libXext-7.4-1.25
xorg-x11-libXprintUtil-7.4-1.26
xorg-x11-driver-video-radeonhd-1.2.3_081202_ed532a7-1.1
pulseaudio-module-x11-0.9.12-9.6
xorg-x11-libXp-7.4-1.25
xorg-x11-libfontenc-7.4-1.23
xorg-x11-libXdmcp-devel-7.4-1.23
xorg-x11-libxcb-devel-7.4-1.24
xorg-x11-server-7.4-17.3
libqt4-x11-4.4.3-4.8.2
xorg-x11-xtrans-devel-7.4-4.12
xorg-x11-Xvnc-7.4-17.3
x11-input-wacom-0.8.1-36.16
xorg-x11-libXdmcp-7.4-1.23
xorg-x11-driver-video-unichrome-20080807-12.44
xorg-x11-libICE-devel-7.4-1.24
xorg-x11-fonts-7.4-1.32
xorg-x11-libXext-devel-7.4-1.25
xorg-x11-libxcb-7.4-1.24
xorg-x11-libXpm-7.4-1.27
emacs-x11-22.3-4.6
xorg-x11-libX11-ccache-7.4-1.36
xorg-x11-driver-input-7.4-11.5
xorg-x11-libfontenc-devel-7.4-1.23
xorg-x11-libX11-7.4-1.25
xorg-x11-libXrender-devel-7.4-1.24
xorg-x11-7.4-8.13
xorg-x11-fonts-core-7.4-1.32
xorg-x11-libXv-7.4-1.25
xorg-x11-libX11-devel-7.4-1.25
xorg-x11-libs-7.4-8.1
xorg-x11-libXp-devel-7.4-1.25
xorg-x11-server-extra-7.4-17.3
yast2-x11-2.17.10-1.9
xorg-x11-libSM-devel-7.4-1.26
xorg-x11-libXfixes-7.4-1.24
xorg-x11-xauth-7.4-8.13
xorg-x11-libXpm-devel-7.4-1.27
xorg-x11-fonts-devel-7.4-1.23
dbus-1-x11-1.2.4-5.1
xorg-x11-devel-7.4-8.1

Comment 3 Stefan Dirsch 2009-03-13 11:29:06 UTC

Unfortunately we don't track any NVIDIA driver bugs filed against 
openSUSE in Novell's bugzilla. Please complain directly to NVIDIA.
Thanks.

(in case you can reproduce this issue with nv driver, feel free to reopen)

Comment 4 Joachim Reichelt 2009-03-13 11:52:14 UTC

Did a test on a system with pure OS graphics:


Section "Device"
  BoardName    "ES1000 515E"
  Driver       "radeon"
  Identifier   "Device[0]"
  Option       "monitor-VGA-0" "Monitor[0]"
  VendorName   "ATI"
EndSection


And :
if a screensaver pops up on the hidden  session, Xorg goes to 100%.

So:
start session 1
start session 2 (login as another user)
activate the screensaver, e.g. just test it.
switch back to session 1.
Now Xorg got 100%

Comment 5 Joachim Reichelt 2009-03-13 12:16:14 UTC

Created attachment 279412 [details]
X11 info of radeon machine

Comment 6 Joachim Reichelt 2009-03-16 22:02:16 UTC

It seems to be fixed in 11.2b1, as I cannot reproduce it on this version.
I did not check for the bug on this special machine running 11.1

BUT: why is the screensaver in KDE4 not running in a nice level?
No I got:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
3214 jre       20   0 81640  30m  14m R   79  1.2   3:16.30 kwave.kss -root
12036 jre       20   0 85268  33m  18m S    2  1.3   0:08.99 kwave.kss -window-id 25234566

Comment 7 Stefan Dirsch 2009-03-20 18:08:40 UTC

> BUT: why is the screensaver in KDE4 not running in a nice level?
> No I got:
>
>   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
> 3214 jre       20   0 81640  30m  14m R   79  1.2   3:16.30 kwave.kss -root
> 12036 jre       20   0 85268  33m  18m S    2  1.3   0:08.99 kwave.kss
> -window-id 25234566

Isn't this a question for the KDE guys?

Comment 8 Lubos Lunak 2009-03-20 20:30:13 UTC

(In reply to comment #7)
> > BUT: why is the screensaver in KDE4 not running in a nice level?
> Isn't this a question for the KDE guys?
Because somebody managed to dump a configure check while porting to KDE4. I will fix it.

Comment 9 Stefan Dirsch 2009-03-20 21:02:02 UTC

Thanks, Lubos!

Comment 10 Stefan Dirsch 2009-03-22 04:52:02 UTC

(In reply to comment #6)
> It seems to be fixed in 11.2b1, as I cannot reproduce it on this version.
> I did not check for the bug on this special machine running 11.1

In this case I'm rather sure it's a duplicated.

*** This bug has been marked as a duplicate of bug 472046 ***