From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001823]: surround40 memory leak
Date: Tue, 25 Jul 2006 20:29:28 +0200 [thread overview]
Message-ID: <8faf4d962acbdcd5edc9366c8c3026c6@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1823>
======================================================================
Reported By: darkbrain
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 1823
Category: PCI - cs46xx
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution:
Kernel Version:
======================================================================
Date Submitted: 02-05-2006 22:59 CET
Last Modified: 07-25-2006 20:29 CEST
======================================================================
Summary: surround40 memory leak
Description:
It seems that surround40 has a memory leak or somthing similar, playing a
game in surround40 mode the game result unplayable after some minutes.
And there is a problem in CS46xx.conf file, i need to remove the hook on
the rear pcm to permit multiple surround40 subdevices to be opened.
======================================================================
----------------------------------------------------------------------
Raymond - 07-25-06 16:03
----------------------------------------------------------------------
Do the "out of sync" problem occur even 2 or 3 instances of surround40 ?
If yes, there is no way to fix unless you know how to patch the firmware.
The available resource DSP_MAX_PCM_CHANNELS are not enough for 31
subdevices(instances) of surround40 or surround51
If there are only 2 pcm_channels left and pcm_multi try to open surround40
or surround51, it is possible that pcm_multi and cs46xx driver is not
capable to recover from this kind of error.
The au88x0 driver also have this kind of problem
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2228
The driver of the hardware mixing sound card need special handling in
snd_xxx_hw_params() and snd_xxx_hw_free() for OSS emulation too.
----------------------------------------------------------------------
bitmage2 - 07-25-06 20:29
----------------------------------------------------------------------
About Raymond's question: I can run 10 instances of "speaker-test -c 6
-Dsurround51 -t wav" without removing the "lock" in the CS46xx.pcm.rear.0
section (I am using no .asoundrc). Instances 1-5 run correct, instances
6-10 produce wrong noises, and instance 11 tells me:
-----
Unable to set hw params for playback: No such device or address
Setting of hwparams failed: No such device or address
-----
If I remove the "lock" (by copying the CS46xx.pcm.rear.0 section to a new
.asoundrc file), the behaviour does *not* change - it is exactly like
described above.
By the way: The CS64xx soundcard I am using is a "Hercules Game Theater
XP7.1".
Issue History
Date Modified Username Field Change
======================================================================
02-05-06 22:59 darkbrain New Issue
02-06-06 06:32 Raymond Note Added: 0007943
02-06-06 07:10 Raymond Note Edited: 0007943
02-06-06 07:31 Raymond Note Edited: 0007943
02-06-06 07:32 Raymond Note Edited: 0007943
02-06-06 10:46 darkbrain Note Added: 0007945
02-06-06 10:46 darkbrain Note Added: 0007946
02-06-06 10:47 darkbrain Note Deleted: 0007946
02-06-06 18:37 darkbrain Note Added: 0007950
02-11-06 15:01 darkbrain Note Added: 0008018
02-12-06 05:09 Raymond Note Added: 0008025
02-15-06 06:21 Raymond Note Added: 0008076
02-21-06 07:56 Raymond Note Added: 0008152
03-27-06 04:42 Raymond Note Added: 0008987
06-02-06 09:33 Raymond Note Deleted: 0008152
06-02-06 09:33 Raymond Note Deleted: 0008987
06-02-06 09:34 Raymond Note Deleted: 0008076
07-11-06 13:28 Raymond Note Added: 0010970
07-24-06 21:21 bitmage2 Note Added: 0011215
07-24-06 21:25 bitmage2 Note Added: 0011216
07-25-06 02:41 Raymond Note Added: 0011222
07-25-06 05:47 Raymond Note Edited: 0011222
07-25-06 10:18 darkbrain Note Added: 0011224
07-25-06 16:03 Raymond Note Added: 0011228
07-25-06 20:29 bitmage2 Note Added: 0011231
======================================================================
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next reply other threads:[~2006-07-25 18:29 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 18:29 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-03 2:26 [ALSA - driver 0001823]: surround40 memory leak bugtrack
2006-08-01 4:39 bugtrack
2006-08-01 1:52 bugtrack
2006-08-01 0:48 bugtrack
2006-07-31 20:52 bugtrack
2006-07-31 20:42 bugtrack
2006-07-31 3:39 bugtrack
2006-07-30 9:53 bugtrack
2006-07-30 1:33 bugtrack
2006-07-30 1:26 bugtrack
2006-07-29 20:44 bugtrack
2006-07-29 15:23 bugtrack
2006-07-29 13:01 bugtrack
2006-07-29 12:50 bugtrack
2006-07-29 12:12 bugtrack
2006-07-29 12:02 bugtrack
2006-07-29 10:23 bugtrack
2006-07-29 10:20 bugtrack
2006-07-29 3:13 bugtrack
2006-07-28 3:03 bugtrack
2006-07-26 14:26 bugtrack
2006-07-26 7:45 bugtrack
2006-07-26 6:34 bugtrack
2006-07-26 0:21 bugtrack
2006-07-25 14:03 bugtrack
2006-07-25 8:18 bugtrack
2006-07-25 0:41 bugtrack
2006-07-24 19:25 bugtrack
2006-07-24 19:21 bugtrack
2006-07-11 11:28 bugtrack
2006-03-27 2:42 bugtrack
2006-02-21 6:56 bugtrack
2006-02-15 5:21 bugtrack
2006-02-12 4:09 bugtrack
2006-02-11 14:01 bugtrack
2006-02-06 17:37 bugtrack
2006-02-06 9:46 bugtrack
2006-02-06 9:46 bugtrack
2006-02-06 5:32 bugtrack
2006-02-05 21:59 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=8faf4d962acbdcd5edc9366c8c3026c6@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