You are not logged in.

Dear visitor, welcome to KDE-Forum.org. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

jturning

Beginner

  • "jturning" started this thread

Posts: 4

Location: Rancho Cordova, CA, USA

  • Send private message

1

Friday, December 29th 2006, 11:57pm

KDE Xorg CPU usage increases until locks X

When running the latest KDE 3.5.5, latest ATI driver, openSUSE 10.2, Xorg 7.2, when I lock the computer and the screensaver activates Xorg usage slowly climbs until it consumes one CPU and locks X windows. Only through SSH can I kill Xorg. This takes a few hours to happen. Otherwise, KDE runs great.

Also, I had the same problem with openSUSE 10.1 and Xorg 6.9 with KDE 3.5.5. No problems with previous version of KDE. And running Gnome locking the screen with the same Xscreensaver I have no issues. This is a KDE only problem on this box anyway.

Any ideas?

Bugz
Bugz

kriko

Trainee

Posts: 127

Location: Slovenia

  • Send private message

2

Sunday, January 7th 2007, 11:38am

I don't think this is a KDE problem at all. Please update to recent version of xorg from suse Xorg repo:
http://software.opensuse.org/download/xorg72/openSUSE_10.2/

Are you using fglrx or opensource driver?
I had such problem on nvidia once, because of composite extension, try to disable it (if enabled).

jturning

Beginner

  • "jturning" started this thread

Posts: 4

Location: Rancho Cordova, CA, USA

  • Send private message

3

Sunday, January 7th 2007, 8:03pm

Thanks

Thanks for responding. I added the repo to SMART and updated Xorg. I also disabled the composite extension. But the problem remains. CPU usage increases when the desktop is locked. In about an hour or so it went from 3/4 % to 12/13%. It slowly just keeps increasing.

It's odd that I don't have an issue with Gnome though. This is why it makes me think it's a KDE issue. Actually, I don't have this problem with Compiz/XGL when running KDE. So perhaps this points to the part of KDE that has the issue?

I'm still relatively new to Linux and Unix, so you might have to coach me a little on what I could do to iron down the issue.

Thanks.
jturning
Bugz

kriko

Trainee

Posts: 127

Location: Slovenia

  • Send private message

4

Sunday, January 7th 2007, 8:10pm

What screensaver are you running when your lock your screen?
Try using blank.

jturning

Beginner

  • "jturning" started this thread

Posts: 4

Location: Rancho Cordova, CA, USA

  • Send private message

5

Sunday, January 7th 2007, 8:21pm

I'm using blank to keep it simple until resolved.

jturning
Bugz

kriko

Trainee

Posts: 127

Location: Slovenia

  • Send private message

6

Sunday, January 7th 2007, 11:47pm

Works fine now? If so, I guess it's a ati driver problem.

jturning

Beginner

  • "jturning" started this thread

Posts: 4

Location: Rancho Cordova, CA, USA

  • Send private message

7

Monday, January 8th 2007, 3:35am

Negative, the bug with KDE is still there. I'd say ATI problem except with the same Xorg, xscreensaver...... the Gnome desktop works perfectly without this bug. Eventually here I'm gong to upgrade to an Nvidia card, so perhaps that will solve it.

Bugz
Bugz

kriko

Trainee

Posts: 127

Location: Slovenia

  • Send private message

8

Monday, January 8th 2007, 10:06am

Hmmm.. I don't know what it could be. What if you launch screensaver in test mode (without locking session - via test button)?

9

Friday, May 18th 2007, 12:46am

Same issue with Nvidia

I just wanted to state I'm having the same issue with an Nvidia card. So, I doubt this is ATI specific.

I'm using OpenSUSE 10.2. The problem happens even if the screensaver is set to blank.

2.6.18.8-0.3-default
Nvidia driver 9755
KDE 3.5.5 "release 45.4"

I have all of the updates available from OpenSUSE's stable repository.

kriko

Trainee

Posts: 127

Location: Slovenia

  • Send private message

10

Friday, May 18th 2007, 4:03pm

@flindet: do you have latest updates? If not, you're using old prerelease xorg version, which contains this bug (I had it too). Upgrade Xorg (set-up repos).

11

Saturday, July 7th 2007, 12:30pm

RE: KDE Xorg CPU usage increases until locks X

Hi, I am having the same problem with kde, ati driver from plf (mandriva) and xorg 7.1 with mandriva 2007.1
Yesterday I turned off xscreensaver before I left worked (at least I think I did) and just turned off my monitor but a few hours later cpu usage was at 100%.
Any ideas?

R Haynes

kriko

Trainee

Posts: 127

Location: Slovenia

  • Send private message

12

Saturday, July 7th 2007, 12:54pm

Do you have xorg updated? Current stable version is 7.2. Repo is located:
http://software.opensuse.org/download/xorg72/openSUSE_10.2/

13

Saturday, July 7th 2007, 1:39pm

no..

Hi, no I have still have xorg 7.1 installed - I am not terribly courageous to install xorg unless it is provided by mandriva (I am using mandriva 2007.1). Do you think this will solve the problem?

R Haynes

kriko

Trainee

Posts: 127

Location: Slovenia

  • Send private message

14

Saturday, July 7th 2007, 2:13pm

Well, I don't know. Suse had a terrible problem, because it shipped with broken Xorg (RC version).

15

Monday, July 9th 2007, 8:26pm

Try turning off DRI in your Xorg conf. I've had this problem over and over with the open source ATI drivers, and this is the only thing that seemed to work.

16

Tuesday, July 10th 2007, 1:44am

Hi, I will experiment with the DRI settings - for now I have turned off the
power management feature in KDE and the problem has not reappeared.
Not sure if this helps anyone diagnose.

R Haynes

17

Monday, July 16th 2007, 12:56pm

Hello,

I have exactly the same problem. My first suspicion fell on the Nvidia driver (since I use a Nvidia card) and/or the screen saver / DPMS system.

1) I have never seen or reproduced the problem while keeping my hands on the keyboard.

2) Sometimes, it take just few minutes of inactivity to crash the X server. When it happens, both my LCD screens are black, but on. LEDs are green, no DPMS off there. Even if they were in DPMS off state before the crash.

3) I am in suspicion that the problem happens more often when I have a TV application on, but I am not sure. I use tvtime, not tested with e.g. xawtv.

4) I have tested simple text banner and plain black screen savers. From now, I have the screen saver switched off (DPMS power off kept) and I am waiting if it will crash.

Some background info:
Distribution is Mandriva 2007.1 (KDE 3.5.6) with all the updates applied. This version has introduced the problem for me. Not present in 2007.0, configuration of the X server is the same. Kernel 2.6.22.1, tested with many prior versions. Multi CPU setup, the kernel is SMP. Dual head Nvidia card, so I have two screens configured in KDE. 4GB RAM, if it does matter.

I hope this will help a bit.

18

Tuesday, July 17th 2007, 10:26am

Well, with a screen saver turned off, the freeze is probably less frequent, but not solved.
Therefore my assume is - the problem is not caused by screen saver.

I am running Mandriva 2007.1 and I am wondering if the problem is related only to this distribution and version.

Does anyone have any news, findings, ... maybe solution?
I have never had my box that unstable ...

19

Wednesday, July 18th 2007, 6:03pm

Hello,

I am not sure if this is related exactly to the problem discussed here.
Anyway, when I have come to my box today, it was at 100% CPU load again and I have straced the X server a bit.
An example output follows. The sequence repeated over and over again in the strace log. Maybe it will be helpful to someone.

Source code

1
2
3
4
5
writev(33, [{"\1\1&W\0\0\0\0\355\0\0\1\n\0a\3\0\0\0\0\0\0\0\0\357VU\0\0\0\0\0", 32}], 1) = 32
select(256, [1 3 4 19 23 24 25 26 27 28 29 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 62 64 66], NULL, NULL, {0, 0}) = 13 (in [28 29 33 36 41 45 50 51 52 56 60 62 64], left {0, 0})
clock_gettime(CLOCK_MONOTONIC, {254344, 656257322}) = 0
read(33, "\24\0\6\0\245\1\0\0\31\1\0\0!\0\0\0\0\0\0\0\240\206\1\0", 4096) = 24
read(33, 0x25d51c0, 4096)               = -1 EAGAIN (Resource temporarily unavailable)

20

Saturday, August 25th 2007, 1:39pm

Just a question for people affected by the problem.
Do you run Super Karamba?