Bug#232466: arts: Sound server fatal error: cpu overload, aborting (workaround)

2004-02-13 Thread Ross Boylan
On Fri, 2004-02-13 at 03:35, Adeodato Simó wrote:
> * Ross Boylan [Thu, 12 Feb 2004 15:11:25 -0800]:
> 
> > A few seconds after KDE starts up I get a pop up window with "Error
> > "Sound server fatal error:
> > cpu overload, aborting"
> 
> I got one of these about two weeks ago.
> 
> > Some clues:
> 
> > The problem started coincident with upgrading to a new kernel (2.4.24,
> > Debianized) with a new alsa-source (1.0.1-1).  I also patches for
> > evms, device-mapper, i2c, and lm-sensors.
> 
> Yep, the culprit seems to be alsa 1.0.1. I did the very same
> upgrade.
> 
> > I recall reading on debian-kde there were some issues with alsa
> > support, but I can't find that now.  In the past it's worked fine,
> > though it may have been using the OSS compatibility layer.
> 
> I found that the problem, actually, was the OSS compatibility layer.
> If you select in Control Panel -> ... -> Sound system -> Audio
> device OSS or Autodetect, you get the error. If you select ALSA
> there, if just works fine.
> 
> Seems like if there are some glitches with ALSA 1.0.1 OSS emulation,
> or at least when mixed with arts.
> 
> Really can't say anything about the causes but just that ALSA as the
> audio device solved the problem for me.
> 
> Cheers.
Thanks.

I can confirm this fix works for me too.
Setting Sound I/O to "Autodetect" or "OSS" produces the error (and does
really use a lot of CPU til it's killed).




Bug#232466: arts: Sound server fatal error: cpu overload, aborting

2004-02-13 Thread Adeodato Simó
* Ross Boylan [Thu, 12 Feb 2004 15:11:25 -0800]:

> A few seconds after KDE starts up I get a pop up window with "Error
> "Sound server fatal error:
> cpu overload, aborting"

I got one of these about two weeks ago.

> Some clues:

> The problem started coincident with upgrading to a new kernel (2.4.24,
> Debianized) with a new alsa-source (1.0.1-1).  I also patches for
> evms, device-mapper, i2c, and lm-sensors.

Yep, the culprit seems to be alsa 1.0.1. I did the very same
upgrade.

> I recall reading on debian-kde there were some issues with alsa
> support, but I can't find that now.  In the past it's worked fine,
> though it may have been using the OSS compatibility layer.

I found that the problem, actually, was the OSS compatibility layer.
If you select in Control Panel -> ... -> Sound system -> Audio
device OSS or Autodetect, you get the error. If you select ALSA
there, if just works fine.

Seems like if there are some glitches with ALSA 1.0.1 OSS emulation,
or at least when mixed with arts.

Really can't say anything about the causes but just that ALSA as the
audio device solved the problem for me.

Cheers.

-- 
Adeodato Simó (a.k.a. thibaut)
EM: asp16 [ykwim] alu.ua.es | IM: my_dato [jabber.org] | PK: DA6AE621
 
# nobody is perfect
$ su - nobody


signature.asc
Description: Digital signature


Bug#232466: arts: Sound server fatal error: cpu overload, aborting

2004-02-12 Thread Ross Boylan
Package: arts
Version: 1.1.5-2
Severity: normal

A few seconds after KDE starts up I get a pop up window with "Error
-artsmess" visible on the title bar (I assume it's artsmessage, but I
can't resize it to see).

The error is 
"Sound server fatal error:
cpu overload, aborting"

Despite this warning, I still have at least some sound: I hear sounds
when I open and close windows, for example.  However, the "Test Sound"
button on the KDE Control Center/Sound System/aRTS tab is greyed out.

If I set the Sound I/O method to non and then restart it with
autodetect, I get the CPU overload popup again.

This problem could well be with another package (e.g., alsa), but I'm
filing this here because that's where I see the symptoms.  I posted a
question about this to debian-user
(http://lists.debian.org/debian-user/2004/debian-user-200401/msg07177.html)
a couple of weeks ago.  My only response has been from someone saying
they have the same problem.

Some clues:

The problem started coincident with upgrading to a new kernel (2.4.24,
Debianized) with a new alsa-source (1.0.1-1).  I also patches for
evms, device-mapper, i2c, and lm-sensors.

I'm not sure exactly which version I had before, but here are some
*excerpts* of recent changelog entries in alsa-driver that seem notable:

alsa-lib (1.0.1-1) unstable; urgency=medium

  * New upstream release (closes: #228102).
+ NOTE! This version includes source incompatibility with previous
  versions. We tested a great many packages and filed bugs, but you may
  want to check your own package too if it Build-Depends: on
  libasound2-dev. The change is briefly documented at
  /usr/share/doc/libasound2-dev/NOTES.
  * David B Harris:
+ Bump libasound2.shlibs to this release (>> 1.0.0) as a new
  symbol (snd_seq_port_subscribe_set_voices)
+ Install "NOTES" file as documentation in libasound2-dev, which documents
  the recent source-incompatible change

 -- Jordi Mallach <[EMAIL PROTECTED]>  Mon, 26 Jan 2004 14:18:06 +0100
[note this was from libasound2]

alsa-driver (0.9.8-2) unstable; urgency=low

  * Steve Kowalik:
- Drop debconf question about loading OSS compatibility modules. We now
  perform auto-detection during boot-up. (Closes: #222350)

alsa-driver (0.9.8-1) unstable; urgency=low

  * Steve Kowalik:
- Patch #16: New; compile core/oss/snd-pcm-oss.c with
  -fno-omit-frame-pointer. (Closes: #195837, #11, #201700)




I recall reading on debian-kde there were some issues with alsa
support, but I can't find that now.  In the past it's worked fine,
though it may have been using the OSS compatibility layer.

I have a dual-processor Athlon system.  Using devfs.

The problem has persisted as I've upgraded from the Debianized
(testing/unstable) KDE packages from 3.1.4 to 3.1.5.  I just rebooted
to be sure I was using the new stuff.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux iron 2.4.24advncd #1 SMP Fri Jan 30 14:30:34 PST 2004 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages arts depends on:
ii  libarts1  1.1.5-2aRts Sound system
ii  libartsc0 1.1.5-2aRts Sound system C support librar

-- no debconf information


Here are my current KDE versions:
# dpkg -l '*kde*' | grep ii
ii  kde-core   3.1.1  The K Desktop Environment (Core)
ii  kdeaddons  3.1.3-1add-on plugins and applets provided with KDE
ii  kdeaddons-kfil 3.1.3-1KDE file dialog plugins for text files and f
ii  kdeadmin   3.1.5-1KDE Administration tools metapackage
ii  kdeadmin-kfile 3.1.5-1KDE File dialog plugins for deb and rpm file
ii  kdeartwork 3.1.5-2themes, styles and more from the official KD
ii  kdeartwork-mis 3.1.5-2various multimedia goodies released with KDE
ii  kdeartwork-sty 3.1.5-2widget styles released with KDE
ii  kdeartwork-the 3.1.5-2icon themes released with KDE
ii  kdeartwork-the 3.1.5-2window decoration themes released with KDE
ii  kdebase3.1.3-1KDE Base metapackage
ii  kdebase-bin3.1.3-1KDE Base (binaries)
ii  kdebase-data   3.1.3-1KDE Base (shared data)
ii  kdebase-kio-pl 3.1.3-1KDE I/O Slaves
ii  kdegames   3.1.4-1KDE Games metapackage
ii  kdegames-card- 3.1.4-1Card decks for KDE games
ii  kdegraphics3.1.4-1KDE Graphics metapackage
ii  kdegraphics-kf 3.1.4-1provide meta information for graphic files
ii  kdelibs3.1.5-1KDE core libraries metapackage
ii  kdelibs-bin3.1.5-1KDE core binaries
ii  kdelibs-data   3.1.5-1KDE core shared data
ii  kdelibs4   3.1.5-1KDE core libraries
ii  kdemultimedia  3.1.2-1KDE Multimedia metapackage
ii  kdemultimedia- 3.1.2-1au/avi/m3u/mp3/ogg/wav plugins for kfile
ii  kdemultimedia- 3.1.2-1Support for browsing audio CDs under Konquer
ii  kdenetwork 3.1.4-1KDE Net