On Mon, 14 May 2012, Oncaphillis wrote: > length m/n tells you the actual_length/transfer_buffer_length > The last pair while accessing the tranfer_buffer seems to be 0/512 > > <snip> > === proc_do_submiturb uurb->type==1:USBDEVFS_URB_TYPE_INTERRUPT alloc > tb:0xffff880077cfadf0 (512) > === async_completed status==0 length:2/512 e=0 > tb:0xffff880077cfadf0[00][41] last tb:0xffff880079612690[6b][6b] > === free_async free tb:0xffff880077cfadf0 > === proc_do_submiturb uurb->type==1:USBDEVFS_URB_TYPE_INTERRUPT alloc > tb:0xffff880077cfadf0 (512) > === async_completed status==-2 length:0/512 e=0 Status = -2 means this URB was unlinked. What does "e=0" mean? > tb:0xffff880077cfadf0[6b][6b] last tb:0xffff880077cfadf0[6b][6b] > === free_async free tb:0xffff880077cfadf0 > === proc_do_submiturb uurb->type==3:USBDEVFS_URB_TYPE_BULK alloc > tb:0xffff880079612690 (2) > === async_completed status==0 length:2/2 e=0 > tb:0xffff880079612690[9d][8d] last tb:0xffff880077cfadf0[9d][8d] > === free_async free tb:0xffff880079612690 > ============================================================================= > BUG kmalloc-512 (Not tainted): Poison overwritten > ----------------------------------------------------------------------------- > INFO: 0xffff880077cfadf0-0xffff880077cfadf1. First byte 0x9d instead > of 0x6b > </snip> Which host controller driver is this device using? And what type of device is it? Alan Stern -- 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
