From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: ALSA 0.9.3a sequencer/rawmidi oops Date: Fri, 16 May 2003 12:57:32 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <200305152318.h4FNInq19726@sprite.physics.adelaide.edu.au> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <200305152318.h4FNInq19726@sprite.physics.adelaide.edu.au> Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Jonathan Woithe Cc: alsa-devel@lists.sourceforge.net List-Id: alsa-devel@alsa-project.org At Fri, 16 May 2003 08:48:49 +0930 (CST), Jonathan Woithe wrote: > > > > > > Over the weekend I thought I'd give ALSA 0.9.3a a go. For the most part it > > > > > worked fine. However, there seems to be a bug in the sequencer or rawmidi > > > > > components. > > > > > > > > > > If any application connects to a sequencer port, a oops results and the > > > > > machine is locked solid. An example decoded oops is given at the end of > > > > > this email. Initially I was testing using jazz++ 4.1.3 and OSS emulation, > > > > > but the oops occurs if pmidi is used. Because pmidi is a native ALSA app, > > > > > it tends to suggest the problem is within the sequencer and/or MPU401 > > > > > rawmidi components. The oops given occurred when pmidi was invoked as: > > > > > pmidi -p 64:0 > > > > > where "64:0" was the port corresponding to the ens1370's external midi > > > > > interface. > > > > > > > > > > ALSA 0.9.2 gives no trouble at all. > > > > > > > > > > The soundcard in use is an Ensoniq AudioPCI (ens1370). > > > > > > > > > > Does anyone have any ideas here? > > > > > > > > does this still happen on the cvs version? > > > > > > The current CVS version is worse. I grabbed a version at around 0900 > > > UT+0930 today (Wed 14 May). I have just compiled this and loaded it. When > > > pmidi -l > > > or > > > pmidi -p 64:0 > > > is run, we now get an error about being unable to open the sequencer. Then > > > when > > > ls /proc/asound > > > is executed the kernel oopses. It's not a hard lock - the machine keeps > > > going - but it's an oops non-the-less which clearly shouldn't happen. It > > > seems that there is something strange lurking in the sequencer. The decoded > > > oops is reproduced below. > > > > yep, there is a bug in the recent cvs version. > > right now i fixed it and committed. please update your tree again. > > I grabbed an update at 1700 UT+0930 on 15 Mat 2003. The kernel oops when > accessing /proc/asound/ is gone now. However, there are still major > problems with this release: > 1) trying to access any of the pseudo files under /proc/asound results > in "no such device" errors. hmm, i saw this phenomenon once but after rebuilding the latest drivers it doesn't appear any more. /proc/asound/dev is no longer created with the latest cvs version. if you used symlink /dev/snd -> /proc/asound/dev, you'll need to run snddevices script once. Takashi ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com