Hi , We debugged and found that by commenting the below line in retire_capture_urb() function /* snd_printd(KERN_ERR "frame %d active: %d\n", i, urb->iso_frame_desc[i].status); */ we get proper usb disconnect and sound cleanup is done automatically with existing functions at usb disconnect during audio play . so things are summarized as : 1) if above snd_printd statement is not commented , system is stuck into continous frame 0 active : alsa -71 , alsa -18 mesages loops and no usb disconnect message comes from lower layer . 2) but if above snd_printd statement is commented , proper usb disconnect message comes and sound cleanup functions are called in snd_complete_urb function starting with cannot submit urb : -19 messages , which is ok . can i be guided with some clue why the presence of snd_printd statement leads system into continous message loops and no usb disconnect message is reported from below usb stack , whereas with commenting snd_printd leads to proper cleanup and usb disconnect messages ? does it has some relation to the way serial and usb interrupts are serviced in the system ? Regards Amit Nagal On Fri, Oct 22, 2010 at 4:22 PM, Clemens Ladisch <clemens@xxxxxxxxxx> wrote: >>>>>> any clues / pointer to functions .changes which can resolve this >>>>>> problem in existing linux kernel ? >>>> >>>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=history;f=sound/usb;hb=HEAD > > There are three patches with "disconnect" in their title, two of which > are for the MIDI driver. > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
