From alsa-devel-owner@alsa.jcu.cz  Mon Oct 12 23:17:58 1998
Received: from keg.cs.vu.nl (root@keg.cs.vu.nl [130.37.24.4])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id XAA20404;
	Mon, 12 Oct 1998 23:17:55 +0200
Received: from localhost by keg.cs.vu.nl with esmtp
	(Smail3.1.28.1 #56) id m0zSpLi-00078yC; Mon, 12 Oct 98 23:17 +0200
Date: Mon, 12 Oct 1998 23:17:50 +0200 (MET DST)
From: Andy Lo A Foe <arloafoe@cs.vu.nl>
To: Jaroslav Kysela <perex@jcu.cz>
cc: alsa-devel@jcu.cz
Subject: Re: S3 SonicVibes
In-Reply-To: <Pine.LNX.3.96.981012230713.25987C-100000@entry.jcu.cz>
Message-ID: <Pine.GSO.4.05.9810122315050.9722-100000@keg.cs.vu.nl>
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, Jaroslav Kysela wrote:

> 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...

Yes, sorry, forgot to mention it, only a hard reset will solve this :(

> 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...

I'm afraid it is quite random, but I got it within 15 minutes of playing
with AlsaPlayer. I'll reset now and see how long it takes and when it
happens...

Andy
--
Andy Lo A Foe, arloafoe@cs.vu.nl |  Linux v2.1.115  | PII 233 
http://www.cs.vu.nl/~arloafoe    | GSM: 0622-440695 | Bebox 133
http://orbital.xs4all.nl/andy    |   ICQ: 7472949   | IRC: Adnans


