From alsa-devel-owner@alsa.jcu.cz  Mon Oct 12 23:13:15 1998
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id XAA20103;
	Mon, 12 Oct 1998 23:13:11 +0200
Date: Mon, 12 Oct 1998 23:13:10 +0200 (CEST)
From: Jaroslav Kysela <perex@jcu.cz>
To: Andy Lo A Foe <arloafoe@cs.vu.nl>
cc: alsa-devel@jcu.cz
Subject: Re: S3 SonicVibes
In-Reply-To: <Pine.GSO.4.05.9810122220110.9722-100000@keg.cs.vu.nl>
Message-ID: <Pine.LNX.3.96.981012230713.25987C-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Mon, 12 Oct 1998, Andy Lo A Foe wrote:

> Hi,
> 
> I borrowed an S3 SonicVibes card from a friend to test it with ALSA.
> Detection is fine, sound is great! But sometimes the card will just
> stop responding i.e. no more interrupts. I can open the PCM device, etc.
> but writing data to it just blocks.. If this is a known problem I'll wait
> for the fix (sorry no time to go hunting for the bug myself right now). If
> noone experiences this I can try to produce some proper debugging output. I'm
> using the CVS version of alsa-driver (updated this afternoon). The code
> I'm testing it with is using small fragments.

Looks that this problem is serious. My colleague have same problem with
ALSA, but I didn't find any bug in code (yet). Seems that S3 SonicVibes
chip is going to some dead mode in some cases. This dead mode shouldn't
be break even with software reset (is this your case?). Only hard reset
helps. All looks good, but DDMA and IRQ isn't working...

Unfortunately this problem is rare (1x per day or something like this).
If you find some algorithm how can be this problem reached without this
long run, it will be fine for testing...

						Jaroslav


-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


