If so, welcome to the club! In my case, the workaround mentioned that deals with the @HARDLOCKLIMIT = 1024 seems to make things much better, so it’s worth to try on your machine.
So even though you have the most recent 2.6.34.7 kernel loaded, I would wonder if the script file please_try_again wrote might help any. It was shown here:
Also, I wonder what might happen if you loaded the 2.6.35.7 kernel, just to see if that might be the problem, if the first trick did not help. I have a script that allows most anyone to compile/install the most recent kernel into their computer.
James - what’s your experience’s been with the .35 kernel? Would you recommend it on a “non-play” system? I’m hesitant to put it on my work laptop, since I can’t afford any major downtime there, but if your experience has been flawless, it may be worth a shot.
Unfortunately, I had to switch to Gnome on my main box (my wife uses it! so it needs to work) - Because kde just didn’t cut the mustard.
Otherwise, kde is good for me on my Intel Laptops (though I know some users have had trouble with Intel too)
Well what I am going to call desktop hitching is random.
This is not the every two to four second hitch/freeze that so many have had.
I am going to read the bugzilla page and see about this “hardlock” thing and applying it to the test box.
This happens on this machine so infrequently as to be a non issue. I though it was a Nivida/Kernel interaction thing but it may be a Nvidia/KDE 4.4thing.
It wasn’t a big issue for me and even in Gnome when I start a wine application, I get a hang for a couple of seconds, but only the first time I start the application during a session. Maybe that’s a clue…
This is just too random. Rebooting seems to have helped it a bunch. Disdabling the GPU temp in gkellm stopped the hitches there. I haven’t done anything else. :0