On Thu, 29 Nov 2001, Steve Harris wrote:
> On Wed, Nov 28, 2001 at 05:32:15PM +0100, Jaroslav Kysela wrote:
> > It's very much better to use the alsa-driver/utils/insert script, and look
> > to alsa-driver/snd.map file for the IP address, where driver crashed. We
> > can determine easily the function.
>
> OK, done that now. I'm a bit lost now though. The EIP was at e0b20586 which
> corresponds to snd_pcm_period_elapsed_Rsmp_ee56678a, but the top of the
> call trace was at e0c42e01 with is just off the end of the module (I
> think), it ends like:
Can you try the lasest CVS code or this patch?
Index: card-ens1370.c
===================================================================
RCS file: /cvsroot/alsa/alsa-driver/cards/card-ens1370.c,v
retrieving revision 1.125
diff -u -r1.125 card-ens1370.c
--- card-ens1370.c 2001/10/12 10:43:18 1.125
+++ card-ens1370.c 2001/11/29 15:20:40
@@ -1936,11 +1936,11 @@
if (status & ES_UART)
snd_ensoniq_midi_interrupt(ensoniq);
- if (status & ES_DAC2)
+ if ((status & ES_DAC2) && ensoniq->playback2_substream)
snd_pcm_period_elapsed(ensoniq->playback2_substream);
- if (status & ES_ADC)
+ if ((status & ES_ADC) && ensoniq->capture_substream)
snd_pcm_period_elapsed(ensoniq->capture_substream);
- if (status & ES_DAC1)
+ if ((status & ES_DAC1) && ensoniq->playback1_substream)
snd_pcm_period_elapsed(ensoniq->playback1_substream);
}
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
SuSE Linux http://www.suse.com
ALSA Project http://www.alsa-project.org
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
