Both USB Type C are not working

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
1

Hi, I am using Jetson AGX Xavier DevKit, jetpack 5.0.1. Before the USB were broken, I connected one of the USB C to Arduino, the other one to a wifi link (Both through USB A to C adapter). I also connected a USB hub to USB A/eSATA. The system is powered by a 19V ACDC voltage adapter.

Normally I connect the Jetson via Wifi. But one day I used an ethernet cable, and also replaced the Arduino with a realsense camera. After that both USB C don’t work anymore. Everything else works fine, including USB A/eSATA.

I find these lines in dmesg, seems that vdd-usb-3v3 could not find a regulator:

[    3.494353] vdd-1v0: supplied by regulator-dummy
[    3.500135] vdd-1v8-hs: supplied by regulator-dummy
[    3.505287] vdd-1v8-ls: supplied by regulator-dummy
[    3.510426] vdd-1v8-ao: supplied by regulator-dummy
[    3.514577] vddio-ddr-1v1: supplied by regulator-dummy
[    3.519573] vdd-rtc: supplied by regulator-dummy
[    3.521883] spmic-ldo1: supplied by regulator-dummy
[    3.523789] vdd-ao-3v3: supplied by regulator-dummy
[    3.530588] vddio-emmc-3v3: supplied by regulator-dummy
[    3.537282] spmic-ldo4: supplied by regulator-dummy
[    3.539076] vdd-usb-3v3: supplied by regulator-dummy
[    3.545820] vddio-sdmmc1-3v3: supplied by regulator-dummy

I have measured the 3V3 and 5V at JTAG. They are fine.
I have tried to set /sys/module/usbcore/parameters/autosuspend to -1. It didn’t work.

Whatever I plug in to USB C, nothing shows up in dmesg.

The full dmesg, boot log and device tree are attached.
boot.log (227.6 KB)
devicetree.dtsi (914.1 KB)
dmesg_full.log (76.7 KB)

Any ideas are appreciated.

2

This might be completely off, but it isn’t unusual for a camera to take a lot of power such that power supplied by the Jetson might be insufficient. Can you use a powered HUB (at least temporarily for testing) and see if externally supplied power solves this?

3

I don’t think so. Now if I connect to my mouse or even my cellphone, it won’t show anything.

4

Do those other devices still fail if the camera is removed? Or is it just temporary when the camera is connected?

Is this the original kernel and kernel configuration? Has there been any configuration related to realtime or a specific CPU being set to handle some process? I don’t see USB information of use, and mostly what I see that is unusual is related to the kernel or kernel scheduling.

5

@linuxdev Yes. Even if I remove the camera, other devices still fail.

I didn’t modify any kernel configuration. Can you be more specific about what you think is unusual? Thanks.

6

Nothing in particular, but here is a recap of some “interesting” log lines:

Apr 21 14:54:40 ubuntu systemd-udevd[372]: /usr/lib/udev/rules.d/60-librealsense2-udev-rules.rules:81 Invalid value "/bin/sh -c '(major=`uname -r | cut -d "." -f1` && minor=`uname -r | cut -d "." -f2` && (([ $major -eq 4 ] && [ $minor -ge 15 ]) || [ $major -ge 5 ])) && (enamefile=/sys/%p/name && [ `cat $enamefile` = "accel_3d" ]) && enfile=/sys/%p/buffer/enable && echo "COUNTER=0; while [ \$COUNTER -lt 20 ] && grep -q 0 $enfile; do sleep 0.01; COUNTER=\$((COUNTER+1)); done && echo 0 > $enfile" | at now'" for RUN (char 188: invalid substitution type), ignoring, but please fix it.

(the above makes me wonder if the camera is still there or if librealsense install broke something in USB…something related to “/usr/lib/udev/rules.d/60-librealsense2-udev-rules” seems broken, and perhaps the actual location this is loaded is"`/etc/udev/rules.d/60-librealsense2-udev-rules" as a symbolic link)

Also:

Jul 22 17:25:46 ubuntu kernel: IRQ221: set affinity failed(-22).
Jul 22 17:25:46 ubuntu kernel: IRQ281: set affinity failed(-22).
Jul 22 17:25:46 ubuntu kernel: CPU4: shutdown
Jul 22 17:25:46 ubuntu kernel: psci: CPU4 killed (polled 0 ms)
Jul 22 17:25:46 ubuntu dbus-daemon[429]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 22 17:25:46 ubuntu kernel: IRQ221: set affinity failed(-22).
Jul 22 17:25:46 ubuntu kernel: IRQ281: set affinity failed(-22).
Jul 22 17:25:46 ubuntu kernel: CPU5: shutdown
Jul 22 17:25:46 ubuntu kernel: psci: CPU5 killed (polled 0 ms)
Jul 22 17:25:46 ubuntu ModemManager[544]: <info>  [base-manager] couldn't check support for device '/sys/devices/platform/3610000.xhci/usb1/1-4/1-4.3': not supported by any plugin
Jul 22 17:25:46 ubuntu ModemManager[544]: <info>  [base-manager] couldn't check support for device '/sys/devices/platform/3550000.xudc': not supported by any plugin
Jul 22 17:25:46 ubuntu kernel: IRQ221: set affinity failed(-22).
Jul 22 17:25:46 ubuntu kernel: IRQ281: set affinity failed(-22).
Jul 22 17:25:46 ubuntu kernel: CPU6: shutdown
Jul 22 17:25:46 ubuntu kernel: psci: CPU6 killed (polled 0 ms)
Jul 22 17:25:46 ubuntu kernel: hid-sensor-hub 0003:8086:0B5C.0001: No report with id 0xffffffff found
Jul 22 17:25:46 ubuntu kernel: IRQ221: set affinity failed(-22).
Jul 22 17:25:46 ubuntu kernel: IRQ281: set affinity failed(-22).
Jul 22 17:25:46 ubuntu kernel: CPU7: shutdown
Jul 22 17:25:46 ubuntu kernel: psci: CPU7 killed (polled 0 ms)

(the above implies an attempt to run a process on particular cores, and failure which killed cores related to that…normally such affinity setting is only done manually by a user or software designed to modify kernel or priorities)

If you still have either ssh or serial console access, can you see if you have “`/etc/udev/rules.d/60-librealsense2-udev-rules”, and if so, if it is a symbolic link?

ls -l /etc/udev/rules.d/60-librealsense2-udev-rules

If you do have this, then could your remove it? And ifthings then work, you could relink it and see if the problem comes back via:

ln -s /usr/lib/udev/rules.d/60-librealsense2-udev-rules /etc/udev/rules.d/60-librealsense2-udev-rules
7

Thanks for your response. I just tried that, but it doesn’t work… Also this file is not in /etc/udev/rules.d. The one in /usr/lib/udev is the original one.

8

It looks like the type C controller is missing. Is this devkit or some custom board?

Could you also flash the board back to rel-32 and see if it can have type C back to work?

9

It is the devkit. I will reflash the system later since I have to find something to back up the files. But is it necessary to flash back to rel-32? My plan is just to re-flash.

Also, is type-c controller missing normal for devkit?

10

Of course not normal. That is why I want to check rel-32. As you know rel-32.x are still the most stable release so far.

Rel-34 are still developer preview.

11

You could temporarily disable the original udev file in “/usr/lib/udev” by compressing it with gzip, and then later reactivate it with gunzip. Try that and reboot (it might not change anything, but it is very easy to test). Then also try the reflash mentioned by @WayneWWW (this would also revert any of the librealsense install changes).

12

I reflashed rel 34. It doesn’t work. I also flashed back to rel32.7.2, jetpack 4.6.2. Two USB C are still not working. But the errors showing in rel34 are not there any more. vdd-usb-3v3- is now “at 3300mV”. The output of command dmesg | grep usb of rel32 is this:

[    0.000000] Kernel command line: console=ttyTCU0,115200 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4 nv-auto-config  video=tegrafb earlycon=tegra_comb_uart,mmio32,0x0c168000 gpt rootfs.slot_suffix= tegra_fbmem=0x140000@0xa06ab000 lut_mem=0x2008@0xa06a6000 usbcore.old_scheme_first=1 tegraid=19.1.2.0.0 maxcpus=8 boot.slot_suffix= boot.ratchetvalues=0.4.2 vpr_resize sdhci_tegra.en_boot_part_access=1  
[    0.975151] usbcore: registered new interface driver usbfs
[    0.975219] usbcore: registered new interface driver hub
[    0.975295] usbcore: registered new device driver usb
[    1.073487] vdd-usb-3v3: at 3300 mV 
[    4.620464] usbcore: registered new interface driver r8152
[    4.620501] usbcore: registered new interface driver asix
[    4.620529] usbcore: registered new interface driver ax88179_178a
[    4.620553] usbcore: registered new interface driver cdc_ether
[    4.620577] usbcore: registered new interface driver net1080
[    4.620602] usbcore: registered new interface driver cdc_subset
[    4.620655] usbcore: registered new interface driver zaurus
[    4.620722] usbcore: registered new interface driver cdc_ncm
[    4.627705] tegra-xusb 3610000.xhci: USB2 port 0 has OTG_CAP
[    4.627709] tegra-xusb 3610000.xhci: USB3 port 2 has OTG_CAP
[    4.633983] usbcore: registered new interface driver uas
[    4.634021] usbcore: registered new interface driver usb-storage
[    4.634072] usbcore: registered new interface driver usbserial
[    4.661480] usbcore: registered new interface driver xpad
[    5.565603] usbcore: registered new interface driver usbhid
[    5.570347] usbhid: USB HID core driver
[    5.654831] usbcore: registered new interface driver snd-usb-audio
[    9.427728] tegra-xusb 3610000.xhci: USB2 port 0 has OTG_CAP
[    9.427732] tegra-xusb 3610000.xhci: USB3 port 2 has OTG_CAP
[    9.430310] tegra-xusb 3610000.xhci: extcon 0: ffffffc7c7aa4800 id
[    9.433048] tegra-xusb 3610000.xhci: Firmware timestamp: 2020-09-11 16:55:03 UTC, Version: 60.09 release
[    9.433089] tegra-xusb 3610000.xhci: xHCI Host Controller
[    9.433114] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[    9.433780] tegra-xusb 3610000.xhci: hcc params 0x0184ff25 hci version 0x110 quirks 0x00050810
[    9.433805] tegra-xusb 3610000.xhci: irq 474, io mem 0x03610000
[    9.433933] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    9.433936] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.433938] usb usb1: Product: xHCI Host Controller
[    9.433940] usb usb1: Manufacturer: Linux 4.9.253-tegra xhci-hcd
[    9.433942] usb usb1: SerialNumber: 3610000.xhci
[    9.434479] tegra-xusb 3610000.xhci: xHCI Host Controller
[    9.434485] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 2
[    9.434490] tegra-xusb 3610000.xhci: Host supports USB 3.1 Enhanced SuperSpeed
[    9.434622] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    9.434624] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.434627] usb usb2: Product: xHCI Host Controller
[    9.434642] usb usb2: Manufacturer: Linux 4.9.253-tegra xhci-hcd
[    9.434644] usb usb2: SerialNumber: 3610000.xhci
[    9.435412] tegra-xusb 3610000.xhci: Upgrade port 0 to USB3.0
[    9.435415] tegra-xusb 3610000.xhci: Upgrade port 1 to USB3.0
[    9.538876] usb usb1: usb_suspend_both: status 0
[    9.542881] usb usb2: usb_suspend_both: status 0
[   10.316887] usb 2-4: new SuperSpeed USB device number 2 using tegra-xusb
[   10.366609] usb 2-4: New USB device found, idVendor=2109, idProduct=0815
[   10.368263] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.369736] usb 2-4: Product: USB3.0 Hub             
[   10.371151] usb 2-4: Manufacturer: VIA Labs, Inc.         
[   10.546743] usb 1-4: new high-speed USB device number 2 using tegra-xusb
[   10.568324] usb 1-4: New USB device found, idVendor=2109, idProduct=2815
[   10.569889] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.571404] usb 1-4: Product: USB2.0 Hub             
[   10.572882] usb 1-4: Manufacturer: VIA Labs, Inc.         
[   11.055071] usb 2-4.2: new SuperSpeed USB device number 3 using tegra-xusb
[   11.077689] usb 2-4.2: New USB device found, idVendor=05e3, idProduct=0612
[   11.077698] usb 2-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   11.077702] usb 2-4.2: Product: USB3.1 Hub
[   11.077707] usb 2-4.2: Manufacturer: GenesysLogic
[   11.206716] usb 2-4.2: usb_suspend_both: status 0
[   11.290734] usb 2-4: usb_suspend_both: status 0
[   11.290962] usb usb2: usb_suspend_both: status 0
[   11.318728] usb 1-4.1: new high-speed USB device number 3 using tegra-xusb
[   11.339311] usb 1-4.1: New USB device found, idVendor=2357, idProduct=0138
[   11.339320] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   11.339324] usb 1-4.1: Product: 802.11ac NIC
[   11.339327] usb 1-4.1: Manufacturer: Realtek
[   11.339330] usb 1-4.1: SerialNumber: 123456
[   11.470729] usb 1-4.2: new high-speed USB device number 4 u[    0.000000] Kernel command line: console=ttyTCU0,115200 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyTCU0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 rootfstype=ext4 nv-auto-config  video=tegrafb earlycon=tegra_comb_uart,mmio32,0x0c168000 gpt rootfs.slot_suffix= tegra_fbmem=0x140000@0xa06ab000 lut_mem=0x2008@0xa06a6000 usbcore.old_scheme_first=1 tegraid=19.1.2.0.0 maxcpus=8 boot.slot_suffix= boot.ratchetvalues=0.4.2 vpr_resize sdhci_tegra.en_boot_part_access=1  
[    0.975151] usbcore: registered new interface driver usbfs
[    0.975219] usbcore: registered new interface driver hub
[    0.975295] usbcore: registered new device driver usb
[    1.073487] vdd-usb-3v3: at 3300 mV 
[    4.620464] usbcore: registered new interface driver r8152
[    4.620501] usbcore: registered new interface driver asix
[    4.620529] usbcore: registered new interface driver ax88179_178a
[    4.620553] usbcore: registered new interface driver cdc_ether
[    4.620577] usbcore: registered new interface driver net1080
[    4.620602] usbcore: registered new interface driver cdc_subset
[    4.620655] usbcore: registered new interface driver zaurus
[    4.620722] usbcore: registered new interface driver cdc_ncm
[    4.627705] tegra-xusb 3610000.xhci: USB2 port 0 has OTG_CAP
[    4.627709] tegra-xusb 3610000.xhci: USB3 port 2 has OTG_CAP
[    4.633983] usbcore: registered new interface driver uas
[    4.634021] usbcore: registered new interface driver usb-storage
[    4.634072] usbcore: registered new interface driver usbserial
[    4.661480] usbcore: registered new interface driver xpad
[    5.565603] usbcore: registered new interface driver usbhid
[    5.570347] usbhid: USB HID core driver
[    5.654831] usbcore: registered new interface driver snd-usb-audio
[    9.427728] tegra-xusb 3610000.xhci: USB2 port 0 has OTG_CAP
[    9.427732] tegra-xusb 3610000.xhci: USB3 port 2 has OTG_CAP
[    9.430310] tegra-xusb 3610000.xhci: extcon 0: ffffffc7c7aa4800 id
[    9.433048] tegra-xusb 3610000.xhci: Firmware timestamp: 2020-09-11 16:55:03 UTC, Version: 60.09 release
[    9.433089] tegra-xusb 3610000.xhci: xHCI Host Controller
[    9.433114] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 1
[    9.433780] tegra-xusb 3610000.xhci: hcc params 0x0184ff25 hci version 0x110 quirks 0x00050810
[    9.433805] tegra-xusb 3610000.xhci: irq 474, io mem 0x03610000
[    9.433933] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    9.433936] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.433938] usb usb1: Product: xHCI Host Controller
[    9.433940] usb usb1: Manufacturer: Linux 4.9.253-tegra xhci-hcd
[    9.433942] usb usb1: SerialNumber: 3610000.xhci
[    9.434479] tegra-xusb 3610000.xhci: xHCI Host Controller
[    9.434485] tegra-xusb 3610000.xhci: new USB bus registered, assigned bus number 2
[    9.434490] tegra-xusb 3610000.xhci: Host supports USB 3.1 Enhanced SuperSpeed
[    9.434622] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    9.434624] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    9.434627] usb usb2: Product: xHCI Host Controller
[    9.434642] usb usb2: Manufacturer: Linux 4.9.253-tegra xhci-hcd
[    9.434644] usb usb2: SerialNumber: 3610000.xhci
[    9.435412] tegra-xusb 3610000.xhci: Upgrade port 0 to USB3.0
[    9.435415] tegra-xusb 3610000.xhci: Upgrade port 1 to USB3.0
[    9.538876] usb usb1: usb_suspend_both: status 0
[    9.542881] usb usb2: usb_suspend_both: status 0
[   10.316887] usb 2-4: new SuperSpeed USB device number 2 using tegra-xusb
[   10.366609] usb 2-4: New USB device found, idVendor=2109, idProduct=0815
[   10.368263] usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.369736] usb 2-4: Product: USB3.0 Hub             
[   10.371151] usb 2-4: Manufacturer: VIA Labs, Inc.         
[   10.546743] usb 1-4: new high-speed USB device number 2 using tegra-xusb
[   10.568324] usb 1-4: New USB device found, idVendor=2109, idProduct=2815
[   10.569889] usb 1-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   10.571404] usb 1-4: Product: USB2.0 Hub             
[   10.572882] usb 1-4: Manufacturer: VIA Labs, Inc.         
[   11.055071] usb 2-4.2: new SuperSpeed USB device number 3 using tegra-xusb
[   11.077689] usb 2-4.2: New USB device found, idVendor=05e3, idProduct=0612
[   11.077698] usb 2-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   11.077702] usb 2-4.2: Product: USB3.1 Hub
[   11.077707] usb 2-4.2: Manufacturer: GenesysLogic
[   11.206716] usb 2-4.2: usb_suspend_both: status 0
[   11.290734] usb 2-4: usb_suspend_both: status 0
[   11.290962] usb usb2: usb_suspend_both: status 0
[   11.318728] usb 1-4.1: new high-speed USB device number 3 using tegra-xusb
[   11.339311] usb 1-4.1: New USB device found, idVendor=2357, idProduct=0138
[   11.339320] usb 1-4.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   11.339324] usb 1-4.1: Product: 802.11ac NIC
[   11.339327] usb 1-4.1: Manufacturer: Realtek
[   11.339330] usb 1-4.1: SerialNumber: 123456
[   11.470729] usb 1-4.2: new high-speed USB device number 4 using tegra-xusb
[   11.493818] usb 1-4.2: New USB device found, idVendor=05e3, idProduct=0610
[   11.493826] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   11.493830] usb 1-4.2: Product: USB2.0 Hub
[   11.493833] usb 1-4.2: Manufacturer: GenesysLogic
[   11.630734] usb 1-4.3: new low-speed USB device number 5 using tegra-xusb
[   11.656325] usb 1-4.3: New USB device found, idVendor=046a, idProduct=0023
[   11.656333] usb 1-4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   11.896660] usb0: HOST MAC 72:fd:50:0f:c0:ae
[   11.896699] usb0: MAC 72:fd:50:0f:c0:af
[   11.920848] l4tbr0: port 2(usb0) entered blocking state
[   11.920855] l4tbr0: port 2(usb0) entered disabled state
[   11.920988] device usb0 entered promiscuous mode
[   11.925615] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   12.454128] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[   12.930727] usb 1-4.2.3: new low-speed USB device number 7 using tegra-xusb
[   12.956912] usb 1-4.2.3: New USB device found, idVendor=046d, idProduct=c050
[   12.956920] usb 1-4.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   12.956923] usb 1-4.2.3: Product: USB-PS/2 Optical Mouse
[   12.956927] usb 1-4.2.3: Manufacturer: Logitech
[   12.961683] input: Logitech USB-PS/2 Optical Mouse as /devices/3610000.xhci/usb1/1-4/1-4.2/1-4.2.3/1-4.2.3:1.0/0003:046D:C050.0003/input/input6
[   12.962058] hid-generic 0003:046D:C050.0003: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-3610000.xhci-4.2.3/input0
[   13.330566] input: HID 046a:0023 as /devices/3610000.xhci/usb1/1-4/1-4.3/1-4.3:1.0/0003:046A:0023.0001/input/input7
[   13.387449] cherry 0003:046A:0023.0001: input,hidraw1: USB HID v1.11 Keyboard [HID 046a:0023] on usb-3610000.xhci-4.3/input0
[   13.389316] input: HID 046a:0023 as /devices/3610000.xhci/usb1/1-4/1-4.3/1-4.3:1.1/0003:046A:0023.0002/input/input8
[   13.507112] cherry 0003:046A:0023.0002: input,hidraw2: USB HID v1.11 Device [HID 046a:0023] on usb-3610000.xhci-4.3/input1
[   14.930957] l4tbr0: port 2(usb0) entered blocking state
[   14.930963] l4tbr0: port 2(usb0) entered forwarding state
[   88.983933] l4tbr0: port 2(usb0) entered disabled state
[   90.380393] device usb0 left promiscuous mode
[   90.380425] l4tbr0: port 2(usb0) entered disabled state
[   93.103511] usb0: HOST MAC 72:fd:50:0f:c0:ae
[   93.103621] usb0: MAC 72:fd:50:0f:c0:af
[   93.119440] l4tbr0: port 2(usb0) entered blocking state
[   93.119446] l4tbr0: port 2(usb0) entered disabled state
[   93.119746] device usb0 entered promiscuous mode
[   93.124556] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   93.539228] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[   96.082634] l4tbr0: port 2(usb0) entered blocking state
[   96.082642] l4tbr0: port 2(usb0) entered forwarding state
[  184.513938] l4tbr0: port 2(usb0) entered disabled state
sing tegra-xusb
[   11.493818] usb 1-4.2: New USB device found, idVendor=05e3, idProduct=0610
[   11.493826] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   11.493830] usb 1-4.2: Product: USB2.0 Hub
[   11.493833] usb 1-4.2: Manufacturer: GenesysLogic
[   11.630734] usb 1-4.3: new low-speed USB device number 5 using tegra-xusb
[   11.656325] usb 1-4.3: New USB device found, idVendor=046a, idProduct=0023
[   11.656333] usb 1-4.3: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   11.896660] usb0: HOST MAC 72:fd:50:0f:c0:ae
[   11.896699] usb0: MAC 72:fd:50:0f:c0:af
[   11.920848] l4tbr0: port 2(usb0) entered blocking state
[   11.920855] l4tbr0: port 2(usb0) entered disabled state
[   11.920988] device usb0 entered promiscuous mode
[   11.925615] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   12.454128] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[   12.930727] usb 1-4.2.3: new low-speed USB device number 7 using tegra-xusb
[   12.956912] usb 1-4.2.3: New USB device found, idVendor=046d, idProduct=c050
[   12.956920] usb 1-4.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[   12.956923] usb 1-4.2.3: Product: USB-PS/2 Optical Mouse
[   12.956927] usb 1-4.2.3: Manufacturer: Logitech
[   12.961683] input: Logitech USB-PS/2 Optical Mouse as /devices/3610000.xhci/usb1/1-4/1-4.2/1-4.2.3/1-4.2.3:1.0/0003:046D:C050.0003/input/input6
[   12.962058] hid-generic 0003:046D:C050.0003: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-3610000.xhci-4.2.3/input0
[   13.330566] input: HID 046a:0023 as /devices/3610000.xhci/usb1/1-4/1-4.3/1-4.3:1.0/0003:046A:0023.0001/input/input7
[   13.387449] cherry 0003:046A:0023.0001: input,hidraw1: USB HID v1.11 Keyboard [HID 046a:0023] on usb-3610000.xhci-4.3/input0
[   13.389316] input: HID 046a:0023 as /devices/3610000.xhci/usb1/1-4/1-4.3/1-4.3:1.1/0003:046A:0023.0002/input/input8
[   13.507112] cherry 0003:046A:0023.0002: input,hidraw2: USB HID v1.11 Device [HID 046a:0023] on usb-3610000.xhci-4.3/input1
[   14.930957] l4tbr0: port 2(usb0) entered blocking state
[   14.930963] l4tbr0: port 2(usb0) entered forwarding state
[   88.983933] l4tbr0: port 2(usb0) entered disabled state
[   90.380393] device usb0 left promiscuous mode
[   90.380425] l4tbr0: port 2(usb0) entered disabled state
[   93.103511] usb0: HOST MAC 72:fd:50:0f:c0:ae
[   93.103621] usb0: MAC 72:fd:50:0f:c0:af
[   93.119440] l4tbr0: port 2(usb0) entered blocking state
[   93.119446] l4tbr0: port 2(usb0) entered disabled state
[   93.119746] device usb0 entered promiscuous mode
[   93.124556] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   93.539228] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[   96.082634] l4tbr0: port 2(usb0) entered blocking state
[   96.082642] l4tbr0: port 2(usb0) entered forwarding state
[  184.513938] l4tbr0: port 2(usb0) entered disabled state

I am concerned about these lines. They show when I connect my host laptop to jetson via the front USB C.

[ 14.930957] l4tbr0: port 2(usb0) entered blocking state
[ 14.930963] l4tbr0: port 2(usb0) entered forwarding state
[ 88.983933] l4tbr0: port 2(usb0) entered disabled state
[ 90.380393] device usb0 left promiscuous mode
[ 90.380425] l4tbr0: port 2(usb0) entered disabled state
[ 93.103511] usb0: HOST MAC 72:fd:50:0f:c0:ae
[ 93.103621] usb0: MAC 72:fd:50:0f:c0:af
[ 93.119440] l4tbr0: port 2(usb0) entered blocking state
[ 93.119446] l4tbr0: port 2(usb0) entered disabled state
[ 93.119746] device usb0 entered promiscuous mode
[ 93.124556] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[ 93.539228] IPv6: ADDRCONF(NETDEV_CHANGE): usb0: link becomes ready
[ 96.082634] l4tbr0: port 2(usb0) entered blocking state
[ 96.082642] l4tbr0: port 2(usb0) entered forwarding state
[ 184.513938] l4tbr0: port 2(usb0) entered disabled state

One thing to note is that I can flash jetson via the front USB -C. My laptop can detect jetson when connect to it via usb-c, but meanwhile, jetson cannot detect any changes in the USB connection.

The full dmesg boot log and device tree of rel32 are attached.
boot_rel32.log (1.8 MB)
devicetree_rel32.dts (359.5 KB)
dmesg_rel32.log (166.6 KB)

Thanks!

13

The real fatal error should be this one. Need to investigate. What usb device is connected on the port?

[ 1164.968688] ucsi_ccg 1-0008: port0 evt: Type-C Error Recovery
[ 1165.426230] ucsi_ccg 1-0008: port0 evt: Type-C Error Recovery
[ 1165.883840] ucsi_ccg 1-0008: port0 evt: Type-C Error Recovery
[ 1166.341487] ucsi_ccg 1-0008: port0 evt: Type-C Error Recovery
[ 1166.799218] ucsi_ccg 1-0008: port0 evt: Type-C Error Recovery
[ 1167.257013] ucsi_ccg 1-0008: port0 evt: Type-C Error Recovery
[ 1167.714503] ucsi_ccg 1-0008: port0 evt: Type-C Error Recovery

14

I was connecting Jetson to my host laptop via USB type C. It is simply the same connection as when I flash the Jetson.

15

Could you just boot up the board, connect no other usb devices and share me the dmesg?

16

dmesg_new.log (74.1 KB)
This is dmesg with no other USB C devices. There is no Wifi chip in Jetson so I have to connect a ethernet cable and a USB hub to USB A to use mouse and keyboard.

17

Ok, the type C log in this one is normal.

Could you connect any usb device to the type C port now and share me the log again? No need to connect to host machine, just connect some simple device (e.g. mouse/keyboard).

18

dmesg_mouse.log (85.0 KB)
I connect the mouse after reboot. Then I disconnect it and plug it in the USB hub connecting to USB A.

By the way, I check some power/signals of the USB C controller U513 today, powered by 19V DC Jack, without connecting to any USBs. I will write down the result in case it helps.

VDD_3V3_PD: 3V3
CCG4_RST_IN_3V3: 3V3
SWD_CLK: nothing, only 0V
SWD_IO: nothing, only 0V

One question, does usb c supports hot plugging?

19

Yes, it supports hotplug. The issue is something else and we are still doing internal check.

20

Thanks! I just heard that my colleague sometimes directly unplugs the power without entering “poweroff” command or pressing the power button to shut it down. I think I should let you know.