google-coral / edgetpu

Coral issue tracker (and legacy Edge TPU API source)
https://coral.ai
Apache License 2.0
428 stars 125 forks source link

USB EdgeTPU keeps disconnecting #675

Closed tyfoon closed 2 years ago

tyfoon commented 2 years ago

Description

The TPU works for a few mins, then after a few minutes the USB TPU disconnects and goes into led blinking stage (2, 3 or 5 blinks). Ubuntu on bear intel J4125 metal

What I tried:

Log below (this is whit the USB powered hub but output is similar wit or with & without hub and without or without USB 2 or 3 and on 2 systems). Starting with plugging in until disconnect.

What to try next?

Click to expand! ### Issue Type Support ### Operating System Ubuntu ### Coral Device _No response_ ### Other Devices _No response_ ### Programming Language _No response_ ### Relevant Log Output ```shell [ 1106.512126] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice= 6.63 [ 1106.512136] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1106.512138] usb 1-1: Product: USB2.1 Hub [ 1106.512140] usb 1-1: Manufacturer: GenesysLogic [ 1106.512995] hub 1-1:1.0: USB hub found [ 1106.513284] hub 1-1:1.0: 4 ports detected [ 1106.637208] usb 2-1: new SuperSpeed USB device number 4 using xhci_hcd [ 1106.665833] usb 2-1: New USB device found, idVendor=05e3, idProduct=0626, bcdDevice= 6.63 [ 1106.665843] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1106.665845] usb 2-1: Product: USB3.1 Hub [ 1106.665848] usb 2-1: Manufacturer: GenesysLogic [ 1106.668579] hub 2-1:1.0: USB hub found [ 1106.669414] hub 2-1:1.0: 4 ports detected [ 1122.541035] usb 2-1.4: new SuperSpeed USB device number 5 using xhci_hcd [ 1122.561690] usb 2-1.4: New USB device found, idVendor=1a6e, idProduct=089a, bcdDevice= 1.00 [ 1122.561711] usb 2-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1127.918540] br-7002fc0ca18f: port 1(vethfe2e242) entered disabled state [ 1127.918735] veth073514f: renamed from eth0 [ 1128.001227] br-7002fc0ca18f: port 1(vethfe2e242) entered disabled state [ 1128.002982] device vethfe2e242 left promiscuous mode [ 1128.002995] br-7002fc0ca18f: port 1(vethfe2e242) entered disabled state [ 1128.123730] br-7002fc0ca18f: port 1(vethe709df8) entered blocking state [ 1128.123739] br-7002fc0ca18f: port 1(vethe709df8) entered disabled state [ 1128.123993] device vethe709df8 entered promiscuous mode [ 1128.125426] br-7002fc0ca18f: port 1(vethe709df8) entered blocking state [ 1128.125433] br-7002fc0ca18f: port 1(vethe709df8) entered forwarding state [ 1128.513556] eth0: renamed from veth2bb80d2 [ 1128.541363] IPv6: ADDRCONF(NETDEV_CHANGE): vethe709df8: link becomes ready [ 1131.560988] usb 2-1.4: reset SuperSpeed USB device number 5 using xhci_hcd [ 1133.432637] usb 2-1.4: reset SuperSpeed USB device number 5 using xhci_hcd [ 1133.457476] usb 2-1.4: LPM exit latency is zeroed, disabling LPM. [ 1133.457490] usb 2-1.4: device firmware changed [ 1133.458210] usb 2-1.4: USB disconnect, device number 5 [ 1133.784611] usb 2-1.4: new SuperSpeed USB device number 6 using xhci_hcd [ 1133.804812] usb 2-1.4: LPM exit latency is zeroed, disabling LPM. [ 1133.805145] usb 2-1.4: New USB device found, idVendor=18d1, idProduct=9302, bcdDevice= 1.00 [ 1133.805150] usb 2-1.4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [ 1164.484537] br-7002fc0ca18f: port 1(vethe709df8) entered disabled state [ 1164.484897] veth2bb80d2: renamed from eth0 [ 1164.545049] br-7002fc0ca18f: port 1(vethe709df8) entered disabled state [ 1164.546294] device vethe709df8 left promiscuous mode [ 1164.546306] br-7002fc0ca18f: port 1(vethe709df8) entered disabled state [ 1164.646912] br-7002fc0ca18f: port 1(veth4751716) entered blocking state [ 1164.646920] br-7002fc0ca18f: port 1(veth4751716) entered disabled state [ 1164.647071] device veth4751716 entered promiscuous mode [ 1164.647962] br-7002fc0ca18f: port 1(veth4751716) entered blocking state [ 1164.647967] br-7002fc0ca18f: port 1(veth4751716) entered forwarding state [ 1165.076654] eth0: renamed from veth2e94bb4 [ 1165.100354] IPv6: ADDRCONF(NETDEV_CHANGE): veth4751716: link becomes ready [ 1168.739641] usb 2-1.4: reset SuperSpeed USB device number 6 using xhci_hcd [ 1168.759774] usb 2-1.4: LPM exit latency is zeroed, disabling LPM. [ 1345.083754] br-7002fc0ca18f: port 1(veth4751716) entered disabled state [ 1345.085992] veth2e94bb4: renamed from eth0 [ 1345.157053] br-7002fc0ca18f: port 1(veth4751716) entered disabled state [ 1345.158491] device veth4751716 left promiscuous mode [ 1345.158500] br-7002fc0ca18f: port 1(veth4751716) entered disabled state [ 1345.242755] br-7002fc0ca18f: port 1(veth8484006) entered blocking state [ 1345.242764] br-7002fc0ca18f: port 1(veth8484006) entered disabled state [ 1345.244103] device veth8484006 entered promiscuous mode [ 1345.244328] br-7002fc0ca18f: port 1(veth8484006) entered blocking state [ 1345.244333] br-7002fc0ca18f: port 1(veth8484006) entered forwarding state [ 1345.716749] eth0: renamed from veth532a5a7 [ 1345.743125] IPv6: ADDRCONF(NETDEV_CHANGE): veth8484006: link becomes ready [ 1349.347097] br-7002fc0ca18f: port 1(veth8484006) entered disabled state [ 1349.347338] veth532a5a7: renamed from eth0 [ 1349.406951] br-7002fc0ca18f: port 1(veth8484006) entered disabled state [ 1349.408541] device veth8484006 left promiscuous mode [ 1349.408555] br-7002fc0ca18f: port 1(veth8484006) entered disabled state [ 1349.485390] br-7002fc0ca18f: port 1(veth1906515) entered blocking state [ 1349.485399] br-7002fc0ca18f: port 1(veth1906515) entered disabled state [ 1349.485496] device veth1906515 entered promiscuous mode [ 1349.487314] br-7002fc0ca18f: port 1(veth1906515) entered blocking state [ 1349.487321] br-7002fc0ca18f: port 1(veth1906515) entered forwarding state [ 1349.966816] eth0: renamed from veth49447a9 [ 1349.983164] IPv6: ADDRCONF(NETDEV_CHANGE): veth1906515: link becomes ready [ 1353.918669] usb 2-1.4: reset SuperSpeed USB device number 6 using xhci_hcd [ 1353.942483] usb 2-1.4: LPM exit latency is zeroed, disabling LPM. [ 1356.526944] usb 2-1.4: USB disconnect, device number 6 ```
tyfoon commented 2 years ago

I just received another Coral and tested with that one; This one does NOT have this behavior! So this seems a hardware failure (yes, I have also switched cables etc).

hjonnala commented 2 years ago

I just received another Coral and tested with that one; This one does NOT have this behavior! So this seems a hardware failure (yes, I have also switched cables etc).

Yes, it seems to be a hardware failure. Thanks for letting us know.

google-coral-bot[bot] commented 2 years ago

Are you satisfied with the resolution of your issue? Yes No