From: Takashi Iwai <tiwai@suse.de>
To: Andy Lo-A-Foe <andy@alsaplayer.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Kernel OOP with alsaplayer driver
Date: Tue, 20 Aug 2002 14:27:23 +0200 [thread overview]
Message-ID: <s5hk7mlsok4.wl@alsa2.suse.de> (raw)
In-Reply-To: <20020820110644.GA380@orbital.xs4all.nl>
Hi,
At Tue, 20 Aug 2002 13:06:44 +0200,
Andy Lo-A-Foe wrote:
>
> Hi,
>
> We've been experiencing kernel OOPSes with the alsaplayer alsa-final
> output plugin. The problems appeared in the 0.9.0rc3 release and
> forward. The same code works fine on 0.9.0rc1. The OOP is triggered at
> close time (snd_pcm_close()) and only then. This behaviour was
> duplicated on at least 2 systems with different soundcards, each time
> with alsaplayer 0.99.71 and alsa 0.9.0rc3 ...
>
> I just noticed that the OOPS doesn't happen if I call snd_pcm_drain() just
> before snd_pcm_close(). It makes sense, but the OOPS should never happen
> right?
could you check via strace which ioctl triggers this?
strangely i cannot reproduce this on my machine.
i guess it's the same problem reported by Benny, the data is
transferred even after hw_free call (in snd_pcm_close).
thanks,
Takashi
-------------------------------------------------------
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390
next prev parent reply other threads:[~2002-08-20 12:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-20 11:06 Kernel OOP with alsaplayer driver Andy Lo-A-Foe
2002-08-20 12:27 ` Takashi Iwai [this message]
2002-08-20 12:59 ` Andy Lo-A-Foe
2002-08-20 13:15 ` Jaroslav Kysela
2002-08-20 15:02 ` Andy Lo-A-Foe
2002-08-20 17:27 ` Benny Sjostrand
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=s5hk7mlsok4.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=andy@alsaplayer.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 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.