Re: [Alsa-devel] my first usb-midi experiment ends with segmentation fault

2002-07-30 Thread Pedro Lopez-Cabanillas

El Mar 30 Jul 2002 15:09, Clemens Ladisch escribió:
 - if (port  0)
 + if (port  0) {
 + snd_printk(KERN_ERR cannot create port (error code %d)\n, 
err);
   return port;

I think that you mean:
snd_printk(KERN_ERR cannot create port (error code %d)\n, 
port);

Right? :)

Pedro.


---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel



Re: [Alsa-devel] my first usb-midi experiment ends with segmentation fault

2002-07-30 Thread Martin Langer

On Tue, Jul 30, 2002 at 03:09:37PM +0200, Clemens Ladisch wrote:
 Martin Langer wrote:
  snd-usb-midi: detected Evolution Electronics L MK-249C USB MIDI keyboa
 
 As Pedro said, subclass 1 is an AudioControl interface. There should be
 two cards, one created by snd-usb-audio, and the other one created by
 snd-usb-midi (see /proc/asound/cards). The contents of the control
 interface (if there are any controls) should be visible in the output
 of the lsusb command.
 
 Your keyboard is unusual in two respects: it's an Audio Class compliant
 device (yes, this _is_ unusual for USB MIDI devices :-) , and it uses
 two endpoints, one for each direction. The combination of these two
 triggers an ugly bug in the descriptor parsing code (device_info isn't
 initialized).
 
 Please try the following patch (the current taciturnity of the driver
 is somewhat inconvenient, so it adds some error messages as well).
 

Thanks for all patches, but I don't found an error in the log-files. The last
line is/was always the detection, which seems to work fine (see above). I'm 
still missing a client in /proc/asound/seq/clients, so the driver never
reaches the port creation and I have no additional output from your patch.
Something else must be between usb-detection and creation of the port!

Also the entry in the /proc/asound/cards is/was all the time there, btw: I
have no hotplugtools installed, everything is manually loaded on my machine.

tuba:~# cat /proc/asound/cards 
0 [card0  ]: USB MIDI - Evolution Electronics L MK-249C Evolution
Electronics L MK-249C Evolution Elect (a4d:8e if 1 at 001/002)
 Evolution Electronics L MK-249C Evolution Elect (a4d:8e
if 1 at 001/002)
1 [card1  ]: USB-Audio - USB Audio Driver
 Evolution Electronics Ltd. MK-249C USB MIDI keyboard


The only strange thing I found are the unknown parts of the lsusb output
(broken descriptor?) and the impossible module reload = segfault.

martin


Bus 001 Device 002: ID 0a4d:008e  
  Language IDs: none (invalid length string descriptor bf; len=0)
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.00
  bDeviceClass1 Audio
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  bMaxPacketSize064
  idVendor   0x0a4d 
  idProduct  0x008e 
  bcdDevice2.00
  iManufacturer   1 
  iProduct2 
  iSerial 0 
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  101
bNumInterfaces  2
bConfigurationValue 1
iConfiguration  3
bmAttributes 0xc0
  Self Powered
MaxPower0mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   0
  bInterfaceClass 1 Audio
  bInterfaceSubClass  1 Control Device
  bInterfaceProtocol  0 
  iInterface  0 
  AudioControl Interface Descriptor:
bLength 9
bDescriptorType36
bDescriptorSubtype  1 (HEADER)
bcdADC   1.00
wTotalLength9
bInCollection   1
baInterfaceNr( 0)   1
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass 1 Audio
  bInterfaceSubClass  3 Non Streaming
  bInterfaceProtocol  0 
  iInterface  0 
  unknown descriptor type: 07 24 01 00 01 41 00
  unknown descriptor type: 06 24 02 01 01 00
  unknown descriptor type: 06 24 02 02 02 00
  unknown descriptor type: 09 24 03 01 03 01 02 01 00
  unknown descriptor type: 09 24 03 02 04 01 01 01 00
  Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   none
wMaxPacketSize 64
bInterval   0
bRefresh0
bSynchAddress   0
  unknown descriptor type: 05 25 01 01 03
  Endpoint Descriptor:
bLength 9
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   none
wMaxPacketSize 64
bInterval   0
bRefresh0
bSynchAddress   0
  unknown descriptor type: 05 25 01 01 01
  Language IDs: none (invalid length string descriptor bf; len=0)




---
This 

Re: [Alsa-devel] my first usb-midi experiment ends with segmentation fault

2002-07-30 Thread Martin Langer

On Tue, Jul 30, 2002 at 08:18:34PM +0200, Martin Langer wrote:
 Bus 001 Device 002: ID 0a4d:008e  
   Language IDs: none (invalid length string descriptor bf; len=0)
 Device Descriptor:
   bLength18

Oh, two lines of lsusb were missing in my mail. 
It has to be so (with string descriptor X invalid ...):


Bus 001 Device 002: ID 0a4d:008e  
  Language IDs: none (invalid length string descriptor bf; len=0)
string descriptor 1 invalid (bf bf; len=0)
string descriptor 2 invalid (bf bf; len=0)
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   1.00
  bDeviceClass1 Audio
  bDeviceSubClass 0 
  bDeviceProtocol 0 
  


---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel



Re: [Alsa-devel] my first usb-midi experiment ends with segmentation fault

2002-07-30 Thread Pedro Lopez-Cabanillas

El Mar 30 Jul 2002 20:18, Martin Langer escribió:
 The only strange thing I found are the unknown parts of the lsusb output
 (broken descriptor?) and the impossible module reload = segfault.


These 'unknown descriptor' lines at lsusb output are jack descriptors and MS 
endpoint descriptors, as required by the specification documents (see 
midi10.pdf, pages 39-43). The lsusb utility should be updated.

I will try to manually decode that descriptors.


 Bus 001 Device 002: ID 0a4d:008e
   Language IDs: none (invalid length string descriptor bf; len=0)
 Device Descriptor:
   bLength18
   bDescriptorType 1
   bcdUSB   1.00
   bDeviceClass1 Audio
   bDeviceSubClass 0
   bDeviceProtocol 0
   bMaxPacketSize064
   idVendor   0x0a4d
   idProduct  0x008e
   bcdDevice2.00
   iManufacturer   1
   iProduct2
   iSerial 0
   bNumConfigurations  1
   Configuration Descriptor:
 bLength 9
 bDescriptorType 2
 wTotalLength  101
 bNumInterfaces  2
 bConfigurationValue 1
 iConfiguration  3
 bmAttributes 0xc0
   Self Powered
 MaxPower0mA
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber0
   bAlternateSetting   0
   bNumEndpoints   0
   bInterfaceClass 1 Audio
   bInterfaceSubClass  1 Control Device
   bInterfaceProtocol  0
   iInterface  0
   AudioControl Interface Descriptor:
 bLength 9
 bDescriptorType36
 bDescriptorSubtype  1 (HEADER)
 bcdADC   1.00
 wTotalLength9
 bInCollection   1
 baInterfaceNr( 0)   1
 Interface Descriptor:
   bLength 9
   bDescriptorType 4
   bInterfaceNumber1
   bAlternateSetting   0
   bNumEndpoints   2
   bInterfaceClass 1 Audio
   bInterfaceSubClass  3 Non Streaming
   bInterfaceProtocol  0
   iInterface  0
   unknown descriptor type: 07 24 01 00 01 41 00
Class Specific Interface Descriptor
bLength 7
bDescriptorType 0x24  (CS_INTERFACE)
bDescriptorSubtype  1  header
bcdADC  1.0
wTotalLength65 

   unknown descriptor type: 06 24 02 01 01 00
MIDI Jack Descriptor
bLength 6
bDescriptorType 0x24
bDescriptorSubtype  2  IN
bJackType   1  EMBEDDED
bJackID 1

   unknown descriptor type: 06 24 02 02 02 00
MIDI Jack Descriptor
bLength 6
bDescriptorType 0x24
bDescriptorSubtype  2  IN
bJackType   2  EXTERNAL
bJackID 2

   unknown descriptor type: 09 24 03 01 03 01 02 01 00
MIDI Jack Descriptor
bLength 9
bDescriptorType 0x24
bDescriptorSubtype  3  OUT
bJackType   1  EMBEDDED
bJackID 3
bNrInputPins1
BaSourceID  2
BaSourcePin 1

   unknown descriptor type: 09 24 03 02 04 01 01 01 00
MIDI Jack Descriptor
bLength 9
bDescriptorType 0x24
bDescriptorSubtype  3  OUT
bJackType   2  EXTERNAL
bJackID 4
bNrInputPins1
BaSourceID  1
BaSourcePin 1

   Endpoint Descriptor:
 bLength 9
 bDescriptorType 5
 bEndpointAddress 0x81  EP 1 IN
 bmAttributes2
   Transfer TypeBulk
   Synch Type   none
 wMaxPacketSize 64
 bInterval   0
 bRefresh0
 

Re: [Alsa-devel] my first usb-midi experiment ends with segmentation fault

2002-07-29 Thread Martin Langer

On Mon, Jul 29, 2002 at 12:40:51PM +0200, Takashi Iwai wrote:
 At Sun, 28 Jul 2002 23:39:24 +0200,
 Martin Langer wrote:
  ... and doing rmmod snd-usb-midi and rmmod snd-usb-audio ends here with 
  Segmentation fault:
  
  
  Jul 28 22:28:07 tuba kernel: usb.c: deregistering driver snd-usb-audio
  Jul 28 22:28:10 tuba kernel: usb.c: deregistering driver snd-usb-midi
  Jul 28 22:28:10 tuba kernel: Unable to handle kernel paging request at
  virtual address 29323034
  Jul 28 22:28:10 tuba kernel:  printing eip:
  Jul 28 22:28:10 tuba kernel: e2858329
  Jul 28 22:28:10 tuba kernel: *pde = 
  Jul 28 22:28:10 tuba kernel: Oops: 0002
  Jul 28 22:28:10 tuba kernel: CPU:0
  Jul 28 22:28:10 tuba kernel: EIP:
  
0010:[snd-dt019x:__insmod_snd-dt019x_O/lib/modules/2.4.19-rc1/kernel/sound/i+-195799/96]
 
 hmm, why snd-dt019x module appears here..?
 was it loaded?  the trace seems corrupted...
 

yes, snd-dt019x was loaded, but that make no difference.

 could you try to put snd-usb-audio to /etc/hotplug/blacklist, so that
 it's not automatically loaded.  then we'll know the problem is related
 only with snd-usb-midi.
 

in both cases:
- without snd-usb-audio
- without snd-usb-audio and without snd-dt019x 
the same occurs. Yes, good arguments for a problem in snd-usb-midi. Here is
what I have done: just a modprobe and rmmod.

---

tuba:~# lsmod 
Module  Size  Used byNot tainted
snd-mixer-oss   9056   0  (autoclean) (unused)
snd24136   0  (autoclean) [snd-mixer-oss]
soundcore   3364   0  (autoclean) [snd]
tuba:~# modprobe snd-usb-midi
tuba:~# rmmod snd-usb-midi
Segmentation fault
tuba:~# lsmod
Module  Size  Used byNot tainted
snd-usb-midi   0   0  (deleted)
snd-seq-virmidi 2728   0  [snd-usb-midi]
snd-seq-midi-event  2872   0  [snd-usb-midi snd-seq-virmidi]
snd-seq37356   0  [snd-usb-midi snd-seq-virmidi
snd-seq-midi-event]
snd-timer  10400   0  [snd-seq]
snd-rawmidi12224   0  [snd-seq-virmidi]
snd-seq-device  3856   0  [snd-usb-midi snd-seq snd-rawmidi]
snd-mixer-oss   9056   0  (autoclean) (unused)
snd24136   0  (autoclean) [snd-usb-midi snd-seq-virmidi
snd-seq-midi-event snd-seq snd-timer snd-rawmidi snd-seq-device snd-mixer-oss]
soundcore   3364   0  (autoclean) [snd]
tuba:~# 



Jul 29 14:15:09 tuba kernel: usb.c: registered new driver snd-usb-midi
Jul 29 14:15:09 tuba kernel: snd-usb-midi: using interface 1
Jul 29 14:15:09 tuba kernel: snd-usb-midi: MIDIStreaming version 01.00
Jul 29 14:15:09 tuba kernel: snd-usb-midi: using 1 input jack(s) on endpoint 1
Jul 29 14:15:09 tuba kernel: snd-usb-midi: using 1 output jack(s) on
endpoint 2
Jul 29 14:15:09 tuba kernel: snd-usb-midi: detected Evolution Electronics L
MK-2
49C USB MIDI keyboa
Jul 29 14:15:14 tuba kernel: usb.c: deregistering driver snd-usb-midi
Jul 29 14:15:14 tuba kernel:  printing eip:
Jul 29 14:15:14 tuba kernel: e2b20329
Jul 29 14:15:14 tuba kernel: Oops: 0002
Jul 29 14:15:14 tuba kernel: CPU:0
Jul 29 14:15:14 tuba kernel: EIP:0010:[e2b20329]Not tainted
Jul 29 14:15:14 tuba kernel: EFLAGS: 00210246
Jul 29 14:15:14 tuba kernel: eax: 29323030   ebx: db5021c0   ecx: db502204
edx
: db502100
Jul 29 14:15:14 tuba kernel: esi: db500c00   edi: 1fff   ebp: e2b3b7dc
esp
: db041ee4
Jul 29 14:15:14 tuba kernel: ds: 0018   es: 0018   ss: 0018
Jul 29 14:15:14 tuba kernel: Process rmmod (pid: 485, stackpage=db041000)
Jul 29 14:15:14 tuba kernel: Stack: daf98380 dd446e00 e2b203ed db500c00
e2b18e5a
 daf98380 1000 e2b18fc5 
 Jul 29 14:15:14 tuba kernel:dd446e00 db500c00 dd446e00 0001
e2b3b7c0
 e2b159ae dd446e00 0001 
 Jul 29 14:15:14 tuba kernel: e2b3aa01 dd446e00 dfe688d8
c021e47d
 dfe67800 dd446e00 dfe67300 
 Jul 29 14:15:14 tuba kernel: Call Trace: [e2b203ed] [e2b18e5a]
[e2b18fc5] 
[e2b3b7c0] [e2b159ae] 
Jul 29 14:15:14 tuba kernel:[e2b3aa01] [usb_drivers_purge+141/224]
[e2b3b
7c0] [usb_drivers_purge+62/224] [e2b3b7c0] [e2b3b7c0] 
Jul 29 14:15:14 tuba kernel:[usb_deregister+114/144] [e2b3b7c0]
[e2b3aa8a
] [e2b3b7c0] [free_module+23/160] [sys_delete_module+247/448] 
Jul 29 14:15:14 tuba kernel:[system_call+51/56] 
Jul 29 14:15:14 tuba kernel: 
Jul 29 14:15:14 tuba kernel: Code: 89 50 04 89 02 ff 4b 3c ff 43 44 0f 8e 05
07 
00 00 53 56 e8 



---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel



Re: [Alsa-devel] my first usb-midi experiment ends with segmentation fault

2002-07-29 Thread Pedro Lopez-Cabanillas

Hello!

I'm happy to see that I'm not the only MIDI guy at ALSA-USB world :)

El Dom 28 Jul 2002 23:39, Martin Langer escribió:
 my new USB-MIDI-Keyboard has two USB subclasses usb-midi and usb-audio.
 Evolution, the manufacturer, told me it's an Audio Class compliant
 device, but I don't find a new entry in /proc/asound/seq/clients after
 loading the modules.

 cat /proc/bus/usb/devices

 T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
 D:  Ver= 1.00 Cls=01(audio) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
 P:  Vendor=0a4d ProdID=008e Rev= 2.00
 S:  Manufacturer=Evolution Electronics Ltd.
 S:  Product=MK-249C USB MIDI keyboard
 C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=  0mA
 I:  If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
 I:  If#= 1 Alt= 0 #EPs= 2 Cls=01(audio) Sub=03 Prot=00 Driver=snd-usb-midi
 E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
 E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms


 dmesg:

 usb.c: registered new driver snd-usb-audio
 usb.c: snd-usb-audio driver claimed interface dfe688c0
 usb.c: registered new driver snd-usb-midi
 snd-usb-midi: using interface 1
 snd-usb-midi: MIDIStreaming version 01.00
 snd-usb-midi: using 1 input jack(s) on endpoint 1
 snd-usb-midi: using 1 output jack(s) on endpoint 2
 snd-usb-midi: detected Evolution Electronics L MK-249C USB MIDI keyboa
 usb.c: snd-usb-midi driver claimed interface dfe688d8



 It's not typical to have a midi-keyboard with two subclasses, or?

IMHO, those descriptors are very close to the USB-Audio specification. Your 
keyboard presents two interfaces: an AudioControl interface (Sub=01) and a  
MIDIStreaming one (Sub=03). Perhaps the snd-usb-audio claims making a very 
quick decision based only on the AudioControl interface. The AudioStreaming 
interface is Sub=02, and your keyboard has not one.

I am using two USB MIDI devices at home, both with the snd-usb-midi driver; an  
Edirol UM-2 (semi-compliant) and a Midiman Midisport 2x2, with a nice GPL  
firmware by Lars Doelle, that tryes to follow the standard. FYI, these are my 
last device descriptors:

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=02 Dev#=  4 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0763 ProdID=1110 Rev= 0.01
S:  Manufacturer=Midiman
S:  Product=Midisport 2x2
S:  SerialNumber=Copyright (GPLv2) 2001 by Lars Doelle 
[EMAIL PROTECTED]
C:* #Ifs= 2 Cfg#= 1 Atr=00 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=(none)
I:  If#= 1 Alt= 0 #EPs= 2 Cls=01(audio) Sub=03 Prot=00 Driver=snd-usb-midi
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=  0ms
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=  0ms

As you can see, very similar to yours.

You can find the specs at http://www.usb.org/
The relevant documents about USB Audio Class and USB MIDI subclass are:
- Universal Serial Bus Revision 1.1 specification,
http://www.usb.org/developers/data/usbspec.zip
- Audio Device Document 1.0,
http://www.usb.org/developers/data/devclass/audio10.pdf
- USB MIDI Devices 1.0,
http://www.usb.org/developers/data/devclass/midi10.pdf


 ... and doing rmmod snd-usb-midi and rmmod snd-usb-audio ends here with
 Segmentation fault:


I can't reproduce this behaviour at home. Perhaps the jack or endpoint 
descriptor parser in snd-usb-midi gets confused for your keyboard. AFAIK, the 
MK-249C is not listed as tested or supported, though.

What I do is blacklist all the snd-usb-* and the corresponding usb oss 
modules, avoiding hotplug from loading them. Instead, the /etc/init.d/alsa 
boot script loads them, with some /etc/modules.conf lines like these:

alias char-major-14 soundcore
alias char-major-116 snd
alias snd-card-0 snd-ens1371
alias snd-card-1 snd-usb-midi
alias sound-slot-0 snd-card-0
alias sound-slot-1 snd-card-1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss

This is not very coherent with the usual USB devices hotplugging capabilities, 
but you have the chance of setting some options. Anyway, if your device is 
not 100% standard, perhaps you have to tweak the alsa-driver/usb/usbmidi.c 
file (search for 'snd_usbmidi_usb_id_table').

Another option is to use the daemon, that runs in userspace, and perhaps can 
be easy for experiment with it, along with hotplug.
You can find it at: http://www.informatik.uni-halle.de/~ladischc/usbmidid.html


Regards,
Pedro



---
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel



[Alsa-devel] my first usb-midi experiment ends with segmentation fault

2002-07-28 Thread Martin Langer


Hi,

my new USB-MIDI-Keyboard has two USB subclasses usb-midi and usb-audio.
Evolution, the manufacturer, told me it's an Audio Class compliant device, 
but I don't find a new entry in /proc/asound/seq/clients after loading the
modules.

cat /proc/bus/usb/devices 

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=01(audio) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0a4d ProdID=008e Rev= 2.00
S:  Manufacturer=Evolution Electronics Ltd.
S:  Product=MK-249C USB MIDI keyboard
C:* #Ifs= 2 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 0 Cls=01(audio) Sub=01 Prot=00 Driver=snd-usb-audio
I:  If#= 1 Alt= 0 #EPs= 2 Cls=01(audio) Sub=03 Prot=00 Driver=snd-usb-midi
E:  Ad=81(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms


dmesg:

usb.c: registered new driver snd-usb-audio
usb.c: snd-usb-audio driver claimed interface dfe688c0
usb.c: registered new driver snd-usb-midi
snd-usb-midi: using interface 1
snd-usb-midi: MIDIStreaming version 01.00
snd-usb-midi: using 1 input jack(s) on endpoint 1
snd-usb-midi: using 1 output jack(s) on endpoint 2
snd-usb-midi: detected Evolution Electronics L MK-249C USB MIDI keyboa
usb.c: snd-usb-midi driver claimed interface dfe688d8



It's not typical to have a midi-keyboard with two subclasses, or?
... and doing rmmod snd-usb-midi and rmmod snd-usb-audio ends here with 
Segmentation fault:


Jul 28 22:28:07 tuba kernel: usb.c: deregistering driver snd-usb-audio
Jul 28 22:28:10 tuba kernel: usb.c: deregistering driver snd-usb-midi
Jul 28 22:28:10 tuba kernel: Unable to handle kernel paging request at
virtual address 29323034
Jul 28 22:28:10 tuba kernel:  printing eip:
Jul 28 22:28:10 tuba kernel: e2858329
Jul 28 22:28:10 tuba kernel: *pde = 
Jul 28 22:28:10 tuba kernel: Oops: 0002
Jul 28 22:28:10 tuba kernel: CPU:0
Jul 28 22:28:10 tuba kernel: EIP:
0010:[snd-dt019x:__insmod_snd-dt019x_O/lib/modules/2.4.19-rc1/kernel/sound/i+-195799/96]
   Not tainted
   Jul 28 22:28:10 tuba kernel: EFLAGS: 00210246
   Jul 28 22:28:10 tuba kernel: eax: 29323030   ebx: dcb21940   ecx:
dcb21984   edx: dcb21900
Jul 28 22:28:10 tuba kernel: esi: d900d000   edi: 1fff   ebp: e2b637dc
esp: d84cdee4
Jul 28 22:28:10 tuba kernel: ds: 0018   es: 0018   ss: 0018
Jul 28 22:28:10 tuba kernel: Process rmmod (pid: 529, stackpage=d84cd000)
Jul 28 22:28:10 tuba kernel: Stack: d9662dc0 db38cc00 e28583ed d900d000
e2854e5a d9662dc0 1000 e2854fc5 
Jul 28 22:28:10 tuba kernel:db38cc00 d900d000 db38cc00 0001
e2b637c0 e28519ae db38cc00 0001 
Jul 28 22:28:10 tuba kernel: e2b62a01 db38cc00 dfe68898
c021e47d dfe67800 db38cc00 dfe67300 
Jul 28 22:28:10 tuba kernel: Call Trace:
[snd-dt019x:__insmod_snd-dt019x_O/lib/modules/2.4.19-rc1/kernel/sound/i+-195603/96]
[snd-dt019x:__insmod_snd-dt019x_O/lib/modules/2.4.19-rc1/kernel/sound/i+-209318/96]
[snd-dt019x:__insmod_snd-dt019x_O/lib/modules/2.4.19-rc1/kernel/sound/i+-208955/96]
[e2b637c0]
[snd-dt019x:__insmod_snd-dt019x_O/lib/modules/2.4.19-rc1/kernel/sound/i+-222802/96]

Jul 28 22:28:10 tuba kernel:[e2b62a01] [usb_drivers_purge+141/224]
[e2b637c0] [usb_drivers_purge+62/224] [e2b637c0] [e2b637c0] 
Jul 28 22:28:10 tuba kernel:[usb_deregister+114/144] [e2b637c0]
[e2b62a8a] [e2b637c0] [free_module+23/160] [sys_delete_module+247/448] 
Jul 28 22:28:10 tuba kernel:[system_call+51/56] 
Jul 28 22:28:10 tuba kernel: 
Jul 28 22:28:10 tuba kernel: Code: 89 50 04 89 02 ff 4b 3c ff 43 44 0f 8e 05
07 00 00 53 56 e8 


a small bug or a big hole?

martin


---
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
___
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel