artsd is eating my CPU on 2.6.1-mm4

Featherfoot

I have kernel 2.6.1-mm4 installed running on a Gigabyte 7VT600 mobo which has a VIA 8235 sound chip. I use the dxs-=2 option and have sound working but whenver sound plays with KDE, cpu utitlization goes up over 50% and stays there after the sound goes away. Killing artsd cures the problem. The problem doesn't exist with kernel 2.4.22-ac4.

Any ideas on how to cure the problem?

Angrybob · Guru Joined: 19 Apr 2003 Posts: 575

are you using the kde 3.2 beta? I was using that for a while and everything was fine... then I upgraded alsa and my kernel and that problem started happening, high cpu usage and some "cpu overload" message box pops up every once in a while... just have to wait for the kde guys to fix it I guess.

Featherfoot · Posted: Sun Jan 18, 2004 3:08 pm Post subject:

No, I found that the 3.2 beta shut down my sound so I took it off. This is with 3.1.5. Same problem with 3.1.4, though.

pilla · Posted: Sun Jan 18, 2004 3:31 pm Post subject:

Are you using ALSA?
_________________
"I'm just very selective about the reality I choose to accept." -- Calvin

Featherfoot · Posted: Sun Jan 18, 2004 3:39 pm Post subject:

I am using the ALSA that is in kernel 2.6.1-mm4.

kuba · n00b Joined: 01 Apr 2003 Posts: 19

maybe this can help

i had to select ALSA in Sound I/O method under Sound I/O (Sound and multimedia -> Sound System in KDE control center).
The previous selection "Autodetect" didn't work with the new alsa version.

Featherfoot · Posted: Sun Jan 18, 2004 4:04 pm Post subject:

I can hear everything just fine. It's just that my system get sluggish when I run it. Killing artsd cures the problem until I need sound again.

javascript:emoticon('

')

Are you suggesting that turning off autodetect might make that better?

jcc · Posted: Sun Jan 18, 2004 4:21 pm Post subject:

when running artsd with the autodetect method on -mm4 (just like you do), I would get a message about CPU Overload just in a matter of minutes.... Also the system would start feeling slow after a while. I set it to ALSA, and bam... Perfect. Just Do It :)

hotwok · n00b Joined: 13 Jan 2004 Posts: 48 Location: Sweden

i had the same problem with artsd using ~50% CPU on my 2400+
it seems artsd is default set to autodetect sound I/O. but somehow it dosn't detect alsa in my 2.6.1 kernel so i manually set artsd sound I/O to alsa and now its back to normal. hope this helps

Featherfoot · Posted: Sun Jan 18, 2004 7:08 pm Post subject:

Thanks. I will try it!

Drewgrange · Guru Joined: 29 Mar 2003 Posts: 483 Location: Ohio, US

I was having the same problem with mm3. Changing autodetect to ALSA fixed it.

Rimmer · n00b Joined: 04 Jan 2004 Posts: 14

I just went from gentoo-dev-sources (2.6.something) to 2.6.2_rc1-love1. I compliled everything the same (ie anything compiled as a module before remained a module).

I wonder if alsa is running... how do I tell? Though I guess the fact that juk plays songs means alsa is working. Any suggestions?

Pythonhead · Posted: Thu Jan 29, 2004 8:08 pm Post subject:

I was having this problem when I was in XFCE4 and started a kde application. I solved it by starting arts manually before any kde app like this: