From: Colin Fletcher <colinf@axicon.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: linux-usb-devel@lists.sourceforge.net,
alsa-devel@lists.sourceforge.net, Andrew Morton <akpm@osdl.org>
Subject: Re: [linux-usb-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface
Date: Fri, 24 Jun 2005 10:35:36 +0100 [thread overview]
Message-ID: <42BBD3E8.5070505@axicon.com> (raw)
In-Reply-To: <1119527109.42baa0c5df4ea@www.domainfactory-webmail.de>
Clemens Ladisch wrote:
> You didn't mention that the device was currently playing/recording, so
> I assume it wasn't.
Correct. Simply plugging in and unplugging the USB cable (or powering
the UA-1000 on and off) causes the oops every time.
> In this case, the oops apparently happens when the
> MIDI URBs are canceled (the MIDI input URBs are active as long as the
> driver is loaded). Please try the attached patch; it adds two printk()s
> around the snd_usbmidi_disconnect() function. If my theory is correct,
> the oops should happen immediately after the "killing MIDI URBs..."
> message.
I don't see the "killing MIDI URBs..." message at all.
> BTW: I never had the opportunity to test my code for the UA-1000.
> Does playback/capture/MIDI work?
jackd will connect to the UA-1000, at which point the 10 output state
LEDs on the front light up, and the output meter shows signals when I
play sound through it, but it's a bit unstable: it will stop working
after a short while. I haven't investigated any further.
Colin Fletcher.
--
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-06-24 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050623024635.5b873305.akpm@osdl.org>
2005-06-23 11:45 ` [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface Clemens Ladisch
2005-06-24 9:35 ` Colin Fletcher [this message]
2005-06-24 10:28 ` [linux-usb-devel] " Clemens Ladisch
2005-06-24 13:39 ` [alsa-devel] " Colin Fletcher
2005-06-27 15:05 ` [linux-usb-devel] " Clemens Ladisch
2005-06-27 21:32 ` [alsa-devel] " Colin Fletcher
2005-06-28 2:03 ` david-b
2005-06-28 2:30 ` Lee Revell
2005-06-28 3:31 ` [linux-usb-devel] " david-b
2005-06-28 4:10 ` [alsa-devel] " Lee Revell
2005-06-28 10:19 ` Colin Fletcher
2005-06-28 13:39 ` Clemens Ladisch
2005-06-28 6:56 ` Clemens Ladisch
2005-06-28 10:23 ` Colin Fletcher
2005-07-06 18:24 ` [linux-usb-devel] " Colin Fletcher
2005-07-07 11:07 ` Clemens Ladisch
2005-07-08 16:37 ` UA-1000 MIDI control port (was - Re: [linux-usb-devel] [alsa-devel] Fw: BUG: Kernel panic when disconnecting Edirol USB2 audio interface) Colin Fletcher
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=42BBD3E8.5070505@axicon.com \
--to=colinf@axicon.com \
--cc=akpm@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=clemens@ladisch.de \
--cc=linux-usb-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.