From: Steve deRosier <derosier@pianodisc.com>
To: Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: frozen MIDI connections
Date: Mon, 08 Aug 2005 14:26:06 -0700 [thread overview]
Message-ID: <42F7CDEE.2070407@pianodisc.com> (raw)
All,
I'm hoping that somebody here has seen this and can help. We have a system with Alsa, using the generic midi serial port device (serial-u16550), that after playing for a while randomly just stops sending data. We have a player program (port 132:0), connected to a midi "router" program (port 128:0) that then sends it to the real device (port 72:*)
A couple of interesting symptoms (other than no data physically going out the port):
1. /proc/asound/seq/clients is showing a constantly increasing alloc failures count on port 132, with some (but not as fast) increase in alloc success. No other port shows the failures.
2. When I 'aconnect -d 132:0 128:0' I get: "Disconnection failed (Operation not permitted)", even though 'acconect -lo' shows the connection. An 'aconnect -x' kills all the connections except the 132->128 connection (but gives no error message at this point).
Killing the player program and restarting it or another player program doesn't cause MIDI to return.
Other than these two items (and the fact that it has stopped sending data out the physical port), we don't see any other anomalies.
Clearly there's a bug, but at this point I've no clue which of my programs to look in, or even the alsa lib or the driver. Has anyone ever seen a case like this, or have any suggestions of where to look?
Thanks,
- Steve
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
reply other threads:[~2005-08-08 21:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=42F7CDEE.2070407@pianodisc.com \
--to=derosier@pianodisc.com \
--cc=alsa-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.