On 2012-06-05 11:10, Christoph Fritz wrote: > Hi, Hi! > > after updating from an ancient kernel version, I encounter a problem > with isp1760: It does resetting all the time. > > Before this patch everything is fine: > > bedc0c31ac3db828e6ade7a8c5cb708688f0a7e1 > usb/isp1760: Move to native-endian ptds > > I did a usbmon capture as you can see below. The caputre file is in > pcap-format which can be read by wireshark. It is attached to this mail. > Just do "wireshark isp1760.pcap" to have a lucid look. > > If you more of an ascii fan, there is another sniff session attached > named isp1760_ascii_dump_sniff_session_console.log :) ... > > Any suggestions? > > Thanks, > -- Christoph > > root@phi:~# mount -t debugfs none_debugs /sys/kernel/debug > root@phi:~# modprobe usbmon > root@phi:~# tshark -i usbmon1 -w /tmp/isp1760.pcap & > [1] 965 > root@phi:~# Running as user "root" and group "root". This could be dangerous. > Capturing on USB bus number 1 > [ 73.509054] usb 1-1.1.7: new high-speed USB device number 4 using isp1760 > [ 73.615194] usb 1-1.1.7: New USB device found, idVendor=13fe, idProduct=3600 > [ 73.622309] usb 1-1.1.7: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [ 73.629825] usb 1-1.1.7: Product: USB DISK 2.0 > [ 73.634280] usb 1-1.1.7: Manufacturer: > [ 73.638820] usb 1-1.1.7: SerialNumber: 079A1B00CF4456D3 > [ 73.650681] scsi0 : usb-storage 1-1.1.7:1.0 > 66 [ 74.685939] scsi 0:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 0 CCS > 81 [ 75.760844] sd 0:0:0:0: [sda] 7811072 512-byte logical blocks: (3.99 GB/3.72 GiB) > [ 75.770725] sd 0:0:0:0: [sda] Write Protect is off > [ 75.776217] sd 0:0:0:0: [sda] No Caching mode page present > [ 75.781778] sd 0:0:0:0: [sda] Assuming drive cache: write through > 123 [ 106.169071] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > 135 [ 111.359121] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > [ 111.480947] sd 0:0:0:0: [sda] No Caching mode page present > [ 111.486530] sd 0:0:0:0: [sda] Assuming drive cache: write through > [ 111.523581] sda: sda4 > [ 111.535280] sd 0:0:0:0: [sda] No Caching mode page present > [ 111.540846] sd 0:0:0:0: [sda] Assuming drive cache: write through > [ 111.546959] sd 0:0:0:0: [sda] Attached SCSI removable disk > [ 111.699077] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > 423 [ 111.909071] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > [ 112.119062] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > [ 112.349068] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > [ 112.559071] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > [ 112.769119] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > 787 [ 112.895034] hub 1-1.1:1.0: cannot reset port 7 (err = -71) > [ 113.169079] usb 1-1.1.7: reset high-speed USB device number 4 using isp1760 > 936 > root@phi:~# fg > tshark -i usbmon1 -w /tmp/isp1760.pcap > ^Croot@phi:~# > Is it correct that the device "sort of" works, just with frequent resets? If it was an endian problem, it seems to me that things should not work at all? Some of the changes made in this patch also affect memory timings. Do you use a custom-made hardware? If so, you could try to modify the ndelay(90) calls (increase the value). Also, if your isp176x is not connected as a PCI device, make sure the signal timings are set up correctly (i.e. if you used a custom avr32 board you would call smc_set_timing() in your platform device init routine; I'm not sure about the procedure for this on arm). -- Arvid Brodin | Consultant (Linux) XDIN AB | Jan Stenbecks Torg 17 | SE-164 40 Kista | Sweden | xdin.com-- 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
