From: Pavel Hofman <pavel.hofman@insite.cz>
To: "Martin Krüger" <m_a_krueger@gmx.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: PATCH - MIDI on ice1724 - real-time kernel problem SOLVED(?)
Date: Fri, 27 Jun 2008 15:54:41 +0200 [thread overview]
Message-ID: <4864F121.8050405@insite.cz> (raw)
In-Reply-To: <4864039B.7020405@gmx.de>
Martin Krüger wrote:
> Martin Krüger schrieb:
>> Hi Pavel,
>>
>> sorry for the long break, i was really busy at studying.
>>
>> ---snip---
>>
>> Thanks a lot,
>> Martin
>> _______________________________________________
>> Alsa-devel mailing list
>> Alsa-devel@alsa-project.org
>> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>>
>
> Hi again,
>
> i did some other playing around this evening. (Debugging would be a word
> much too big...)
>
> I commented out the logic stuff in the following subroutines of the
> ice1724.c:
>
> - static int vt1724_midi_output_open(struct snd_rawmidi_substream *s)
> - static int vt1724_midi_output_close(struct snd_rawmidi_substream *s)
> - static void vt1724_midi_output_trigger(struct snd_rawmidi_substream
> *s, int up)
> - static void vt1724_midi_output_drain(struct snd_rawmidi_substream *s)
>
> The vt1724_enable_midi_irq(s, VT1724_IRQ_MPU_TX, 1) is killing my
> kernel, i don't know why.
So enabling the MPU TX interrupt causes lockup. Very similar to my
experience with the previous version of the MIDI driver. Please put a
debug line to snd_vt1724_interrupt, listing status bits for each
interrupt. That was the place I experienced loops etc. In my case the
flood eventually fooled the logging facility, but I could still read the
first few logs.
> On the input side everything works, so i am a bit confused. Again. ;-)
I was also getting only TX interrupt floods, RX was OK.
Good luck,
Pavel.
next prev parent reply other threads:[~2008-06-27 13:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080520112539.81C9D2484D@alsa0.perex.cz>
2008-05-23 10:26 ` [alsa-cvslog] alsa-kmirror: ALSA kernel mirror repository branch, master now at 9d46f4a919532c3f29a4ca1df3a4ce4686b11f37 Thierry Vignaud
2008-05-24 16:53 ` PATCH - MIDI on ice1724 - real-time kernel problem SOLVED(?) Martin Krüger
2008-05-26 7:57 ` Pavel Hofman
2008-05-26 10:54 ` Martin Krüger
2008-05-26 14:53 ` Takashi Iwai
2008-05-26 16:29 ` Martin Krüger
2008-05-28 11:58 ` Martin Krüger
2008-05-29 9:35 ` Pavel Hofman
2008-05-29 14:03 ` "Martin Krüger"
2008-05-29 16:14 ` Pavel Hofman
2008-06-07 21:36 ` Pavel Hofman
2008-06-24 11:07 ` Martin Krüger
2008-06-26 21:01 ` Martin Krüger
2008-06-27 13:54 ` Pavel Hofman [this message]
2008-06-27 14:24 ` Takashi Iwai
2008-06-18 9:58 ` can we make the log appears in subject instead of useless sha1 ID? Thierry Vignaud
2008-06-19 9:54 ` 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=4864F121.8050405@insite.cz \
--to=pavel.hofman@insite.cz \
--cc=alsa-devel@alsa-project.org \
--cc=m_a_krueger@gmx.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