Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA 0.9.3a sequencer/rawmidi oops
Date: Wed, 14 May 2003 15:31:02 +0200	[thread overview]
Message-ID: <s5h8yt9fyeh.wl@alsa2.suse.de> (raw)
In-Reply-To: <200305141246.h4ECk7232331@mercury.physics.adelaide.edu.au>

At Wed, 14 May 2003 22:16:07 +0930 (CST),
Jonathan Woithe wrote:
> 
> Hi Takashi
> 
> > > 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.


thanks,

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

  reply	other threads:[~2003-05-14 13:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-12  3:13 ALSA 0.9.3a sequencer/rawmidi oops Jonathan Woithe
2003-05-13 13:52 ` Takashi Iwai
2003-05-14 12:46   ` Jonathan Woithe
2003-05-14 13:31     ` Takashi Iwai [this message]
2003-05-15 23:18       ` Jonathan Woithe
2003-05-16 10:57         ` Takashi Iwai
2003-05-18 12:01           ` Jonathan Woithe
2003-05-19  7:12             ` Jaroslav Kysela
2003-05-21  6:39               ` Jonathan Woithe
2003-05-18 12:16           ` Jonathan Woithe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5h8yt9fyeh.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=jwoithe@physics.adelaide.edu.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox