From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001149]: CPU overload error and arts exits
Date: Thu, 2 Jun 2005 15:29:37 +0200 [thread overview]
Message-ID: <aaf1bab24336a93359650755d040fcc3@bugtrack.alsa-project.org> (raw)
The following issue has been RESOLVED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1149>
======================================================================
Reported By: anandrajan
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1149
Category: PCI - emu10k1
Reproducibility: always
Severity: major
Priority: normal
Status: resolved
Distribution: SuSE 9.3 Pro x86-64 version
Kernel Version: 2.6.11
Resolution: won't fix
Fixed in Version:
======================================================================
Date Submitted: 06-01-2005 16:35 CEST
Last Modified: 06-02-2005 15:29 CEST
======================================================================
Summary: CPU overload error and arts exits
Description:
Hardware: A7V Deluxe with onboard Realtek ALC 850 sound and Marvel gigabit
ethernet, AMD Athlon 64 3000+, 1GB DDR 400, two IDE disks, NEC DVD RW,
Plextor CD-RW, ELSA GLoria III nVidia Quadro2 Pro videocard, Soundblaster
Live PCI soundcard
Software: SuSE 9.3 Pro x86-64 version, KDE 3.4, alsa 1.0.8 drivers
Originally I had configured both the onboard Realtek and the Soundblaster
cards. Then I removed the Realtek from the configuration. Unfortunately
and even when full duplex is not checked in KDE 3.4, I get a CPU overload
error and then arts exits. If I monitor what's happening, I see the CPU
usage in arts increasing until it maxes out the CPU after which I get this
error. The arts page claims that this is a driver issue.
======================================================================
----------------------------------------------------------------------
anandrajan - 06-02-05 15:26
----------------------------------------------------------------------
I upgraded to 1.0.9 and the results are mixed - sorry couldn't resist :-).
While arts doesn't crash after KDE starts up, I can make arts crash by
enabling system sounds and resizing a window several times in succession.
Don't know if this is a emu10k1 (alsa) or arts problem. When the window is
resized several times and arts has to emit a sound each time, it draws
more and more of the CPU and then crashes. Also, I've seen arts crash by
itself a couple of times. Regardless, it works better now but not
perfectly.
Duplex is enabled right now. Also, I've attached my /dev/sndstat file
since it still claims that I'm running alsa 1.0.8 in emulation.
Output of /dev/sndstat
Sound Driver:3.8.1a-980706 (ALSA v1.0.8 emulation code)
Kernel: Linux agape-server 2.6.11.4-20a-default
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1 Wed Mar 23 21:52:37 UTC
2005 x86_64
Config options: 0
Installed drivers:
Type 10: ALSA emulation
Card config:
Sound Blaster Live! (rev.8, serial:0x80271102) at 0xd800, irq 185
Audio devices:
0: EMU10K1 (DUPLEX)
Synth devices:
0: Emu10k1
Midi devices:
0: EMU10K1 MPU-401 (UART)
Timers:
7: system timer
Mixers:
0: Cirrus Logic CS4297A rev 4
RPMS related to alsa that are installed on my machine:
alsa-32bit-9.3-7
alsa-tools-1.0.9-0.pm.1
kalsatools-1.5.0-349
alsa-1.0.9-5.1
alsaplayer-0.99.76-72.1
alsa-firmware-1.0.9-0.pm.0
alsamodular-1.8.7-5
kalsatools-debuginfo-1.5.0-348
alsa-devel-1.0.9-5.1
alsamixergui-0.9.0rc1-544
alsa-tools-gui-1.0.9-0.pm.1
----------------------------------------------------------------------
tiwai - 06-02-05 15:29
----------------------------------------------------------------------
It's a known bug of arts, I believe. Nothing can be done from alsa
driver/lib side...
Issue History
Date Modified Username Field Change
======================================================================
06-01-05 16:35 anandrajan New Issue
06-01-05 16:35 anandrajan Distribution => SuSE 9.3 Pro x86-64
version
06-01-05 16:35 anandrajan Kernel Version => 2.6.11
06-01-05 16:45 tiwai Note Added: 0004859
06-02-05 15:26 anandrajan Note Added: 0004877
06-02-05 15:29 tiwai Status new => resolved
06-02-05 15:29 tiwai Resolution open => won't fix
06-02-05 15:29 tiwai Assigned To => tiwai
06-02-05 15:29 tiwai Note Added: 0004878
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
next reply other threads:[~2005-06-02 13:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 13:29 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 13:26 [ALSA - driver 0001149]: CPU overload error and arts exits bugtrack
2005-06-01 14:45 bugtrack
2005-06-01 14:35 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aaf1bab24336a93359650755d040fcc3@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox