From alsa-devel-owner@alsa.jcu.cz  Sun Mar  8 23:25:42 1998
Received: from entry.jcu.cz (perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.8.8/8.8.8) with SMTP id XAA07967;
	Sun, 8 Mar 1998 23:25:41 +0100
Date: Sun, 8 Mar 1998 23:25:41 +0100 (MET)
From: Jaroslav Kysela <perex@jcu.cz>
To: alsa-devel@alsa.jcu.cz
cc: Chris Butler <chrisb@sandy.force9.co.uk>
Subject: Re: Hanging with kernel 2.1.88 (and 2.1.84)
In-Reply-To: <199803081711.RAA08587@sandy.force9.co.uk>
Message-ID: <Pine.LNX.3.96.980308231937.22324H-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 Sun, 8 Mar 1998, root wrote:

> Hi!
> 
> When I try to record from the SBPro (using cat), it hangs after a bit
> under the 2.1.84 & 2.1.88 kernel. I get some data, then a pause, then
> the system just locks up totally (not even the Vulcan Nerve Pinch (tm)
> worked).
> 
> Works fine under 2.0.33 (or at least until I stopped it at ~500k), so
> it must be a kernel problem. Possibly the memory-management and/or DMA?
> 
> Eeek, I've just remembered I offered to maintain these drivers.. :-)
> Any pointers about where I should start looking?

Maybe this problem cause wrong SMP testing in 0.0.5- versions of driver,
but I'm not sure. I tried 0.0.6 (ES1688 soundcard) with 2.1.89 and seems
that all works ok.

Otherwise this problem is caused in most cases if wrong memory place is
rewriten... We should detect at first if problem is general or lowlevel
specific. Anyone else have this problem with 0.0.6 driver?

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


