From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: Takashi Iwai <tiwai@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: 2.6.26.[6|7]-rt11, alsa rawmidi, seq hang
Date: Thu, 06 Nov 2008 16:58:05 -0800 [thread overview]
Message-ID: <1226019485.3135.31.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1679 bytes --]
(starting a new thread with the hope of being more precise after a lot
of testing and rebooting)
I'm seeing a realtime patch related hard hang in the kernel alsa
subsystem (MIDI input/output). In a nutshell:
- alsa rawmidi works (ie: "rawmidi -v -i hw:0" outputs a stream of
messages when pointed to a midi capable card that has an external
keyboard connected).
- the alsa sequencer interface works (ie: aplaymidi connected to
aseqdump transfers data just fine).
- BOTH combined do NOT work (ie: use aconnect to connect the port that
corresponds to the external midi interface to aseqdump: aseqdump hangs
forever after transferring the first message and the only way out is a
reboot).
Just tested this on 2.6.26.7 + rt11, Gina3G soundcard with an external
MIDI keyboard sending messages. This is not specific to the Gina card, I
have tested also USB midi interfaces and an RME hdsp card with a
Multiface interface.
2.6.24.7 + rt21 works fine on the same hardware combinations. The
standard Fedora 9 2.6.26.x kernel works fine as well.
I'm attaching the kernel configuration for the kernel I'm currently
testing plus a dmesg dump of the whole boot process (rt kernel hackers
can find there some additional sleeping in wrong context warning
messages there), including the output of a "echo t >/proc/sysrq-trigger"
that should show where aseqdump currently hangs (or so I think).
Hopefully this will narrow the area affected enough so that a solution
can be found or more debugging info can be requested. Currently
2.6.26.x-rtx is unusable for musical purposes (at least when you have to
interact with external midi controllers).
Thanks for any help...
-- Fernando
[-- Attachment #2: dmesg.bz2 --]
[-- Type: application/x-bzip, Size: 38161 bytes --]
[-- Attachment #3: config-2.6.26.7-1.rt11.1fc9.ccrma.i686.rt.bz2 --]
[-- Type: application/x-bzip, Size: 21348 bytes --]
next reply other threads:[~2008-11-07 0:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 0:58 Fernando Lopez-Lezcano [this message]
2008-11-07 9:12 ` 2.6.26.[6|7]-rt11, alsa rawmidi, seq hang Clemens Ladisch
2008-11-07 9:37 ` Clemens Ladisch
2008-11-07 18:12 ` [alsa-devel] " Fernando Lopez-Lezcano
2008-11-07 18:36 ` Fernando Lopez-Lezcano
2008-11-07 23:12 ` Fernando Lopez-Lezcano
2008-11-08 0:48 ` Fernando Lopez-Lezcano
2008-11-08 1:14 ` Fernando Lopez-Lezcano
2008-11-13 21:01 ` Fernando Lopez-Lezcano
2008-11-13 22:56 ` [alsa-devel] " Fernando Lopez-Lezcano
2008-11-14 0:12 ` [alsa-devel] 2.6.26.[6|7]-rt11, alsa rawmidi, seq hang (tasklet_hi_schedule?) Fernando Lopez-Lezcano
2008-11-14 8:15 ` Clemens Ladisch
2008-11-14 8:46 ` Takashi Iwai
2008-11-14 18:57 ` Fernando Lopez-Lezcano
2008-11-19 11:44 ` Takashi Iwai
2008-11-27 16:50 ` Takashi Iwai
2008-12-11 11:58 ` Takashi Iwai
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=1226019485.3135.31.camel@localhost.localdomain \
--to=nando@ccrma.stanford.edu \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tiwai@suse.de \
/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