From: Benny Sjostrand <gorm@cucumelo.org>
To: Jaroslav Kysela <perex@suse.cz>
Cc: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: [BUG ?] Crash in the cs46xx driver when using alsaplayer
Date: Mon, 12 Aug 2002 21:42:16 +0200 [thread overview]
Message-ID: <3D580F98.60902@cucumelo.org> (raw)
In-Reply-To: Pine.LNX.4.33.0208122106500.1463-100000@pnote.perex-int.cz
>
>
>>Where is BUG ?, or in cs46xx driver or in the ALSA PCM core somewhere ?,
>>well, it's easy fixed in snd_cs46xx_playback_copy(...) doing a check.
>>Then why it only happen with the alsaplayer, just no idea ....
>>
>>suggestions ... ?? comments .... ??
>>
>
>playback_copy shouldn't be called after hw_free. I don't see any error in
>PCM core. The additional check would be dead code. It would be better to
>determine the real problem. Do you know the order of syscalls?
>
That's exactly my thought.
Adding a check in snd_cs46xx_playback_copy(...) works fine however
it may not be the right solution to the problem.
It only happens to me with the "alsaplayer", so probably the alsaplayer
is doing something special.
The alsaplayer seems to have various threads:
10826 pts/1 S 0:00 alsaplayer -f 2048
10827 pts/1 S 0:00 alsaplayer -f 2048
10828 pts/1 S 0:00 alsaplayer -f 2048
10830 pts/1 S 0:00 alsaplayer -f 2048
10831 pts/1 S 0:02 alsaplayer -f 2048
10832 pts/1 S 0:00 alsaplayer -f 2048
10834 pts/1 RN 0:00 alsaplayer -f 2048
10835 pts/1 RN 0:00 alsaplayer -f 2048
Maybe the problem is some race condition, just a theory ....
Is there way to debug the PCM core finding out what happens ??
/Benny
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
prev parent reply other threads:[~2002-08-12 19:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 18:59 [BUG ?] Crash in the cs46xx driver when using alsaplayer Benny Sjostrand
2002-08-12 19:22 ` Jaroslav Kysela
2002-08-12 19:42 ` Benny Sjostrand [this message]
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=3D580F98.60902@cucumelo.org \
--to=gorm@cucumelo.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.