Hi, >> Just curious. The crash log shows the following UDC driver code which >> is responsible to receive endpoint 0 setup data. However, the host PC >> is sending SCSI_WRITE_10 command at the time of the crash. These two >> does not correlate, right? >> >> unsigned int rdata, rdata1; >> >> // setup data valid >> val = readl(dev->base_addr + 0+0xfb0/0x199c [kagen2_udc] > > The crash log should not include any driver code. > > What data were you writing to the gadget when the crash occurred? > Were you sending the source code for the UDC driver? If you were, > maybe that data got written to a wrong area in memory. Yes, you are right! I was sending the source code of the UDC driver when the crash occurred. Another question from the bulk_out_complete() printout which is shown below. The req->actual is 512 byte. The bh->bulk_out_intended_length is 31. Is this a bug? g_file_storage gadget: get_next_command [start_transfer] 6f007442 7000 ept1 out queue len 0x200, buffer 0xc1330000 kagen2_ep_queue 512 512 512 g_file_storage gadget: bulk_out_complete --> 0, 512/31 ..... thanks, victor -- 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
