From: Mark Knecht <markknecht@attbi.com>
Cc: Takashi Iwai <tiwai@suse.de>,
Alsa-Devel <alsa-devel@lists.sourceforge.net>
Subject: Re: HDSP 9652 MIDI IN - stuck notes
Date: 28 Feb 2003 05:09:30 -0800 [thread overview]
Message-ID: <1046437770.1264.16.camel@Godzilla> (raw)
In-Reply-To: <1046436995.1264.5.camel@Godzilla>
On Fri, 2003-02-28 at 04:56, Mark Knecht wrote:
> > at least, we need to check whether the interrupts for MIDI are
> > generated properly.
> > please try the following.
> >
> > 1. connect HDSP MIDI1 input to HDSP MIDI1 output via aconnect.
> > 2. trigger a note from MIDI1 input.
> > check whether the IRQ count in /proc/interrupts (for HDSP)
> > increases.
> > during this test, don't use HDSP audio.
> >
>
> mark@Godzilla card1]$ more /proc/interrupts
> CPU0
> 0: 62488 XT-PIC timer
> 1: 816 XT-PIC keyboard
> 2: 0 XT-PIC cascade
> 5: 749 XT-PIC usb-uhci, usb-uhci, usb-uhci, eth0
> 8: 1 XT-PIC rtc
> 10: 94 XT-PIC hdsp
> 11: 5 XT-PIC ohci1394
> 12: 7033 XT-PIC PS/2 Mouse
> 14: 8556 XT-PIC ide2
> 15: 9005 XT-PIC ide3
> NMI: 0
> ERR: 0
> [mark@Godzilla card1]$
BTW - The HDSP interrupts above do not represent a failure. All I did is
what you asked me to do. If you asked me to wait for a failure, we'd
have 1000's on interrupts at least, I'm sure, and I don't know how we
would identify that one did not happen.
Also, if I wasn't clear earlier, the failure is ONE stuck note. The MIDI
input keeps working, and subsequent notes work properly. (both on and
off) It's just that a single note gets stuck every 1-2 minutes.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-02-28 13:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 4:47 HDSP 9652 MIDI IN - stuck notes Mark Knecht
2003-02-28 12:14 ` Takashi Iwai
2003-02-28 12:56 ` Mark Knecht
2003-02-28 13:09 ` Mark Knecht [this message]
2003-03-06 19:50 ` Mark Knecht
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=1046437770.1264.16.camel@Godzilla \
--to=markknecht@attbi.com \
--cc=alsa-devel@lists.sourceforge.net \
--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