# Issue when FX3 (USB 2.0) is connected to a USB 3.0 port (on the iMX8MP SolidRun board) Kirkstone OS

**URL:** <https://community.solid-run.com/t/issue-when-fx3-usb-2-0-is-connected-to-a-usb-3-0-port-on-the-imx8mp-solidrun-board-kirkstone-os/949>\
**Category:** Uncategorized\
**Created:** [January 1, 2025, 12:36pm UTC](https://community.solid-run.com/t/issue-when-fx3-usb-2-0-is-connected-to-a-usb-3-0-port-on-the-imx8mp-solidrun-board-kirkstone-os/949 "2025-01-01T12:36:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![tushar](https://avatars.discourse-cdn.com/v4/letter/t/5fc32e/32.png) [@tushar](https://community.solid-run.com/u/tushar)\
**Post date:** [January 1, 2025, 12:36pm UTC](https://community.solid-run.com/t/issue-when-fx3-usb-2-0-is-connected-to-a-usb-3-0-port-on-the-imx8mp-solidrun-board-kirkstone-os/949/1 "2025-01-01T12:36:18Z")

</div>

Dear All,

I have connected the FX3 (USB 2.0) to a USB 3.0 port on the iMX8MP SolidRun board and I am using the Kirkstone OS . It throws the following error:  
[6.046271] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller  
[6.058085] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1  
[6.075380] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe6d hci version 0x110 quirks 0x0000002001010010  
[6.092648] xhci-hcd xhci-hcd.1.auto: irq 77, io mem 0x38100000  
[6.106831] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller  
[6.125269] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2  
[6.132941] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed  
[6.166902] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller  
[6.172430] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 3  
[6.180489] xhci-hcd xhci-hcd.2.auto: hcc params 0x0220fe6d hci version 0x110 quirks 0x0000002001010010  
[6.189931] xhci-hcd xhci-hcd.2.auto: irq 78, io mem 0x38200000  
[6.195981] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller  
[6.201483] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 4  
[6.209152] xhci-hcd xhci-hcd.2.auto: Host supports USB 3.0 SuperSpeed  
[114.594847] usb 3-1: new high-speed USB device number 2 using xhci-hcd  
[124.774856] xhci-hcd xhci-hcd.2.auto: Abort failed to stop command ring: -110  
[124.790080] xhci-hcd xhci-hcd.2.auto: xHCI host controller not responding, assume dead  
[124.798011] xhci-hcd xhci-hcd.2.auto: HC died; cleaning up  
[124.803569] xhci-hcd xhci-hcd.2.auto: Timeout while waiting for configure endpoint command

But when I am using Hardknott OS, it gets connected

[4.477145] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller  
[4.477167] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 1  
[4.477509] xhci-hcd xhci-hcd.1.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000002021810010  
[4.477553] xhci-hcd xhci-hcd.1.auto: irq 76, io mem 0x38100000  
[4.477679] xhci-hcd xhci-hcd.1.auto: xHCI Host Controller  
[4.477692] xhci-hcd xhci-hcd.1.auto: new USB bus registered, assigned bus number 2  
[4.477754] xhci-hcd xhci-hcd.1.auto: Host supports USB 3.0 SuperSpeed  
[4.480643] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller  
[4.480662] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 3  
[4.481006] xhci-hcd xhci-hcd.2.auto: hcc params 0x0220fe6c hci version 0x110 quirks 0x0000002021810010  
[4.481053] xhci-hcd xhci-hcd.2.auto: irq 77, io mem 0x38200000  
[4.481174] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller  
[4.481184] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 4  
[4.481196] xhci-hcd xhci-hcd.2.auto: Host supports USB 3.0 SuperSpeed  
[76.746062] usb 1-1: new high-speed USB device number 2 using xhci-hcd  
[76.964508] input: FX3: FX3 as /devices/platform/soc@0/32f10100.usb/38100000.dwc3/xhci-hcd.1.auto/usb1/1-1/1-1:1.0/input/input1

Any reason?

I have checked the configs related to the xHCI driver, and it is enabled in both OS versions. There have not been significant changes in the device tree

---

<div class="post-metadata">

**Author:** ![jnettlet](https://dub1.discourse-cdn.com/flex005/user_avatar/community.solid-run.com/jnettlet/32/62_2.png) [@jnettlet](https://community.solid-run.com/u/jnettlet)\
**Post date:** [January 2, 2025, 7:29am UTC](https://community.solid-run.com/t/issue-when-fx3-usb-2-0-is-connected-to-a-usb-3-0-port-on-the-imx8mp-solidrun-board-kirkstone-os/949/2 "2025-01-02T07:29:33Z")

</div>

> [@tushar](#):
>
> Abort failed to stop command ring: -110

Try adding `usbcore.autosuspend=-1` to your kernel command-line. There have been quite a few changes to the usb subsystem in the newer kernel of kirkstone and some devices are still problematic with auto-suspend.

---

<div class="post-metadata">

**Author:** ![tushar](https://avatars.discourse-cdn.com/v4/letter/t/5fc32e/32.png) [@tushar](https://community.solid-run.com/u/tushar)\
**Post date:** [January 6, 2025, 4:47am UTC](https://community.solid-run.com/t/issue-when-fx3-usb-2-0-is-connected-to-a-usb-3-0-port-on-the-imx8mp-solidrun-board-kirkstone-os/949/3 "2025-01-06T04:47:00Z")

</div>

Dear Jnettlet,

i have added usbcore.autosuspend=-1 in the kernel command line but still USB Disconnect shows

root=/dev/mmcblk1p2 rootwait rw rootwait rw usbcore.autosuspend=-1 console=ttymxc1,115200

cat /sys/module/usbcore/parameters/autosuspend  
-1