Hey all, Recently artsd has been shutting off with the error "CPU overload". It doesn't seem to matter what I'm running. It'll do this at random times even if no sound is being processed. I've even tried logging into KDE3 and not starting up any extra programs, just KDE with a few applets (none sound related). The CPU Overload error/shutdown of artsd occurs very randomly... sometimes within a minute of starting KDE, sometimes up to two hours before it occurs. I also have KDE set up so no sounds play except when KDE starts up or is shut down. Even shut off the system bell for the Konsole. I can see when it's going to happen because the CPU monitor applet suddenly shows heavy CPU usage. I've used kpm to see what's running and I see nothing that would be making Arts do this. But artsd itself will show heavy system usage when this occurs just before it shuts down. I'm using the latest KDE3 RPMs taken from the SuSE server, which includes arts-1.0.1-13.rpm . (Using SuSE 7.3 Pro) To make matters worse, if I "artsd start" after this happens, it'll start fine, but all sounds are choppy when I do this so it's useless. And eventually at some random point it will do a CPU overload again. But leaving KDE and logging in again will restart arts without the choppy-sound problem. 1) Is this an arts issue, an issue with this particular RPM, or what? Where do I start to look in determining the problem? I'm almost certain this didn't start happening until I installed the latest build of that particular RPM, but I can't say that for certain. 2) Seems odd that starting KDE (and thus it starts artsd) doesn't cause choppy sounds, but if I do "artsd start" it gets choppy. This happens even if I "artsd stop" then start it again, not just after a CPU overload issue. Does KDE set some specific options for artsd when it starts arts itself that I should be doing as well? Later, Joe "Flame" Sullivan -------------------------------------------------------------------------------------- Firechild Web Design and CGI Scripting Services http://firechild.net Secretary, World Association of Internet Marketing http://waim.org Webmaster, Amerikanska - For Americans In Sweden http://amerikanska.com Meta-editor, Open Directory Project http://dmoz.org ---------------------------------------------------------------------------------------
On Sunday 30 June 2002 17.45, Joe Sullivan wrote:
Recently artsd has been shutting off with the error "CPU overload". It doesn't seem to matter what I'm running. It'll do this at random times even if no sound is being processed.
Hmmm... After digging around in random places on the web for what seems like hours, I think I found the solution myself. Posting it here in case anyone else has issues, and so noone wastes their time responding since it seems resolved: The problem seems to have been "full duplex mode". In the KDE Control Center, under Sound > Sound Server > Sound I/O , I had marked "full duplex mode", though I don't recall doing this. Unmarking it and restarting the server seems to be working okay now. Apparently full duplex mode causes problems with some sound cards. Later, Joe "Flame" Sullivan -------------------------------------------------------------------------------------- Firechild Web Design and CGI Scripting Services http://firechild.net Secretary, World Association of Internet Marketing http://waim.org Webmaster, Amerikanska - For Americans In Sweden http://amerikanska.com Meta-editor, Open Directory Project http://dmoz.org ---------------------------------------------------------------------------------------
Yes, full duplex seems to cause lots of problems in linux, even when the card supports it. you could also try grabbing this updated arts rpm (its suse 8 but i cant imagine why it wouldn't work on 7.3 in this case). http://www.mirror.ac.uk/sites/ftp.suse.com/pub/suse/i386/update/8.0/kde7/art... Ewan On Sun, 2002-06-30 at 19:43, Joe Sullivan wrote:
On Sunday 30 June 2002 17.45, Joe Sullivan wrote:
Recently artsd has been shutting off with the error "CPU overload". It doesn't seem to matter what I'm running. It'll do this at random times even if no sound is being processed.
Hmmm... After digging around in random places on the web for what seems like hours, I think I found the solution myself.
Posting it here in case anyone else has issues, and so noone wastes their time responding since it seems resolved:
The problem seems to have been "full duplex mode". In the KDE Control Center, under Sound > Sound Server > Sound I/O , I had marked "full duplex mode", though I don't recall doing this.
Unmarking it and restarting the server seems to be working okay now. Apparently full duplex mode causes problems with some sound cards.
Later, Joe "Flame" Sullivan
participants (2)
-
Ewan Leith
-
Joe Sullivan