Desktop slows to a crawl after a few days

After some time, usually in the morning after a few days, the machine will run rather slowly. It’s like the machine is ‘ticking’ only once every few seconds (The clock actually losses the time and i have to resynchronize the clock). A reboot quickly fixes the problem, and top shows nothing consuming the cpu (top actually being at the top of the list).

Any suggestions on how to go about debugging this???

System information:

OS: Linux x86_64
System: openSUSE 11.1 (x86_64)
KDE: 4.1.3 (KDE 4.1.3) “release 4.10.4”

Processor (CPU): Intel(R) Core™ i7 CPU 920 @ 2.67GHz
Speed: 2,673.32 MHz
Cores: 4

Total memory (RAM): 11.7 GB
Free memory: 10.5 GB (+ 676.5 MB Caches)
Free swap: 2.0 GB

Vendor: NVIDIA Corporation
Model: GeForce GTX 275/PCI/SSE2
Driver: 3.2.0 NVIDIA 190.42

any hints in any logs?
top show any zombies on that third morning?

are you running screen saver on random? pick one, or “blank screen”
and see if the problem goes away…

check back here in a few days if it goes away, or not…

and, consider the possibility of doing something so that top is not
the most useful thing running over night–personally, i suggest
folding@home <> which hold the possibility
of someday producing something good for all mankind (such as
Alzheimer’s, Mad Cow (BSE), CJD, ALS, Huntington’s, Parkinson’s
disease, and many Cancers and cancer-related syndromes.)

if the screen saver trick doesn’t work for you, maybe keeping the box
busy will…

Have a lot of fun…

I don’t think its a screensaver. Sometimes it will start acting up while I am actually on the machine. I am running the virtual machine screensaver, though. Folding@home does look like an interesting way to put the cpu to use at night.

I looked at /var/log/messages and found these items (repeats omitted)

Nov 5 08:45:23 Coanda pulseaudio[9598]: module-alsa-sink.c: ALSA woke us up to write new data t
o the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. P
lease report this issue to the PulseAudio developers.
Nov 5 08:51:37 Coanda avahi-daemon[3912]: Invalid query packet.

There are 200,300 lines of mostly the first item for the last two days… These seems rather bad, could it be the cause? How would I go about addressing this?

crcook wrote:

> Please report this issue to the PulseAudio developers.

i guess you should find and chat with the PulseAudio developers to see
if they can trouble shoot your problems…or, at least help you fix
that part…

if you use the forum search function and look around you will find
that many people have solved all their sound problems by uninstalling
pluseaudio…now, i’ve never heard of it causing your problem, but it
is easy to uninstall (with YaST) and usually all sound keeps working
fine (usually better)…and, if this problem goes away then you know
not to reinstall it…

if the original prob remains you might wanna reinstall it and then
get with the developers to help them fix their bug…

check back because there could EASILY have someone (many ones) smarter
than me drop by and give the answer…

and, let us know if removing pulseaudio fixes your problem…

Have a lot of fun…

I have moved to 11.2, and have not seen the issue since. I was not able to figure out what was causing the problem in the first place.

> I have moved to 11.2, and have not seen the issue since. I was not able
> to figure out what was causing the problem in the first place.

it is not your responsibility to figure out what caused the problem…
that is the job of the developers…

which is why the error in the log asked you to “Please report this
issue to the PulseAudio developers” rather than saying “Figure out
what is causing the PulseAudio problem and fix it yourself or ask on
the forum for help.”

see/understand the difference??