From: Clemens Ladisch <clemens@ladisch.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: Takashi Iwai <tiwai@suse.de>, Ingo Molnar <mingo@elte.hu>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.26.[6|7]-rt11, alsa rawmidi, seq hang
Date: Fri, 07 Nov 2008 10:12:35 +0100 [thread overview]
Message-ID: <49140683.9040008@ladisch.de> (raw)
In-Reply-To: <1226019485.3135.31.camel@localhost.localdomain>
Fernando Lopez-Lezcano wrote:
> 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).
Please try the snd-virmidi driver, then we'd have a test case that does
not require MIDI hardware.
> ... including the output of a "echo t >/proc/sysrq-trigger" that
> should show where aseqdump currently hangs (or so I think).
It hangs in tasklet_kill(), which gets called while it tries to close
the rawmidi port.
The rawmidi framework uses this tasklet to notify the sequencer that new
MIDI data is available. The handler function is
snd_rawmidi_input_event_tasklet() in sound/core/rawmidi.c; the sequencer
callback that gets called from there is snd_midi_input_event() in
core/seq/seq_midi.c.
You say that the first event gets delivered, so it might be possible
that the tasklet never finishes executing. Please check whether the
call to snd_seq_kernel_client_dispatch() in snd_midi_input_event()
ever returns.
I vaguely remember that we had exactly the same problem (hangs when
using sequencer on RT kernel) some time ago, and that it was somehow
related to tasklets.
Regards,
Clemens
next prev parent reply other threads:[~2008-11-07 9:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-07 0:58 2.6.26.[6|7]-rt11, alsa rawmidi, seq hang Fernando Lopez-Lezcano
2008-11-07 9:12 ` Clemens Ladisch [this message]
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=49140683.9040008@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nando@ccrma.Stanford.EDU \
--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