From alsa-devel-owner@alsa.jcu.cz  Fri Jan 15 19:20:43 1999
Received: from cheetah.it.wsu.edu (mwoods@cheetah.it.wsu.edu [134.121.1.8])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id TAA01006
	for <alsa-devel@alsa.jcu.cz>; Fri, 15 Jan 1999 19:19:20 +0100
Received: from localhost (mwoods@localhost)
	by cheetah.it.wsu.edu (8.8.7/8.8.7) with SMTP id KAA20452
	for <alsa-devel@alsa.jcu.cz>; Fri, 15 Jan 1999 10:19:19 -0800 (PST)
Date: Fri, 15 Jan 1999 10:19:19 -0800 (PST)
From: Mike Woods <mwoods@mail.wsu.edu>
To: alsa-devel@alsa.jcu.cz
Subject: Re: Ultrasound Midi.
In-Reply-To: <Pine.LNX.3.96.990113210717.19268B-100000@entry.jcu.cz>
Message-ID: <Pine.OSF.3.95.990115101552.17694A-100000@cheetah.it.wsu.edu>
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 Wed, 13 Jan 1999, Jaroslav Kysela wrote:

> On Wed, 13 Jan 1999, Mike Woods wrote:
> 
> > On Wed, 13 Jan 1999, Steve Ratcliffe wrote:
> > 
> > > > problems with it, except for the midi. I know it is still under
> > > > development, but whenever I try raw midi, or the sequencer, my whole
> > > > system locks up. I have an Gravis Ultrasound PnP Pro card. I have recently
> > > > ran the test programs included in the alsa-lib. The decoder bit worked,
> > > > but the sender locked everything. Any ideas of what might be going wrong?
> > > 
> > > Is that straight away, or after a while?
> > > 
> > > This is what happens for me:
> > > 
> > > First I applied the appended patch so that reads return as soon as there
> > > is some data.
> 
> Oops. Bug in alsa-lib (which don't set O_NONBLOCK correctly). I fixed this
> bug today. Get latest CVS sources.
> 
> > > The decoder works fine, and I get an event printed every time that I
> > > hit a key on my keyboard.
> > > 
> > > Sender works at first and I get the ECHO event printed every second until
> > > about 200 seconds after alsa was loaded, when the whole system locks up
> > > completely.  However this only happens when my midi keyboard is switched on,
> > > it does not appear to lock up when it is switched off.
> > > 
> > > It could be that the active sensing signals are piling up somewhere and
> > > causing a problem when some limit is reached.
> 
> Small bug in GF1 UART driver.. Check CVS.. Now should be all ok..
> 

I tried the ./seq sender 64.0 from alsa-lib again, but I found the same
result. It tells me queue 0 is being used and client 128, then immediately
freezes everything. I also used debug and verbose with this program and
did not find any additional output.

> 							Jaroslav
> 
> -----
> Jaroslav Kysela <perex@jcu.cz>
> Academic Computer Centre, University of South Bohemia
> Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic
> 
> 
> ------
> To unsubscribe from <alsa-devel@alsa.jcu.cz> mailing list send message
> 'unsubscribe' in the body of message to <alsa-devel-request@alsa.jcu.cz>.
> 


