Re: [alsa-devel] 2.6.26.[6|7] vs. rt11 vs. alsa (usb) midi

[Fernando Lopez-Lezcano]

On Wed, 2008-10-29 at 12:10 +0100, Takashi Iwai wrote:
> At Tue, 28 Oct 2008 14:35:55 -0700,
> Fernando Lopez-Lezcano wrote:
> > 
> > On Mon, 2008-10-27 at 09:13 +0100, Takashi Iwai wrote:
> > > At Sat, 25 Oct 2008 19:46:27 -0700,
> > > Fernando Lopez-Lezcano wrote:
> > > > 
> > > > Hi... anyone out there also having problem with this combination?
> > > >    2.6.26.7 or 2.6.26.6 with 2.6.26.6-rt11 and alsa MIDI
> > > > It looks to me like alsa midi is broken. 
> > > > 
> > > > Probably an interaction with the realtime kernel patch. A Fedora kernel
> > > > based on 2.6.26.6 (2.6.26.6-49 on fc8) works fine, a very similarly
> > > > patched kernel that includes the realtime patch does not. The
> > > > configurations for both are almost the same (today I tried to change
> > > > some of the most obvious differences and rebuild, with the same
> > > > result). 
> > > > 
> > > > No problems with 2.6.24.7-rt21. 

(but on Fedora 9 I get X segfaults with it... so not really usable
either)

> > > > Test: boot, login, plugin an external usb keyboard (Yamaha P250), it is
> > > > recognized, use qjackctl alsa patchbay to connect it to kmidimon,
> > > > kmidimon sees only _one_ midi message and that's it. Kmidimon can't be
> > > > killed after that. 
> > > 
> > > What about other MIDI devices on other bus, e.g. an MPU401 on a PCI
> > > soundcard or so?  There is a possibility of breakage in the USB driver
> > > side, too.
> > 
> > I just tested an RME PCMCIA card + Multiface interface and it shows the
> > same problem. No MIDI messages get through (but the LED in the Multiface
> > blinks). Same hardware booted into 2.6.24.7-rt21 works fine. 
> 
> Then this should be in RT side.  There is no fundamental change
> regarding rawmidi since some time ago...

Hmm, why do you say rawmidi? This is happening with the sequencer
interface, AFAIK. 

I just tested this with the rawmidi.c test program that comes with alsa
and the rawmidi interface _is_ working ("rawmidi -v -i hw:1,0" outputs
the raw bytes being received). 

Now I start qjackctl to patch the sequencer output of the P250 to
kmidimon and I get just one "active sensing" message in the messages
window of kmidimon. This is what I see in the proc/asound/seq/clients
file:

----
$ cat /proc/asound/seq/clients 
Client info
  cur  clients : 6
  peak clients : 6
  max  clients : 192

Client   0 : "System" [Kernel]
  Port   0 : "Timer" (Rwe-)
  Port   1 : "Announce" (R-e-)
    Connecting To: 15:0, 128:0, 129:0
Client  14 : "Midi Through" [Kernel]
  Port   0 : "Midi Through Port-0" (RWe-)
Client  15 : "OSS sequencer" [Kernel]
  Port   0 : "Receiver" (-we-)
    Connected From: 0:1
Client  20 : "P-250" [Kernel]
  Port   0 : "P-250 MIDI 1" (RWeX)
    Connecting To: 129:0
  Port   1 : "P-250 MIDI 2" (-We-)
Client 128 : "Client-128" [User]
  Port   0 : "qjackctl" (-W--)
    Connected From: 0:1
  Input pool :
    Pool size          : 200
    Cells in use       : 0
    Peak cells in use  : 3
    Alloc success      : 5
    Alloc failures     : 0
Client 129 : "KMidimon" [User]
  Port   0 : "input" (-We-)
    Connected From: 0:1, 20:0
  Output pool :
    Pool size          : 500
    Cells in use       : 0
    Peak cells in use  : 0
    Alloc success      : 0
    Alloc failures     : 0
  Input pool :
    Pool size          : 200
    Cells in use       : 0
    Peak cells in use  : 2
    Alloc success      : 4
    Alloc failures     : 0
----

Now I quit kmidimon...

----
$ cat /proc/asound/seq/clients
----

Hangs!
Can't ctrl-c out of it. 
Kmidimon is (sort of) still around:

----
nando     7696  0.3  0.0      0     0 ?        Zl   22:41   0:01
[kmidimon] <defunct>
----

Rawmidi does not work anymore, of course, hangs and can't be ctrl'c'ed
either. Everything that touches midi seems to hang waiting for something
that is never going to happen. And this only appears to happen when I
try to use the sequencer api. Before that the rawmidi program happily
prints midi bytes as they arrive. 

Maybe this points to a possible culprit?
Any more data I could provide that would be useful?
Any help in debugging this would be appreciated. At this point no
realtime kernel is usable for the tasks I need it for. 

-- Fernando


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/