AnsweredAssumed Answered

USB host controller goes down with "fsl-ehci fsl-ehci.0: HC died; cleaning up" in log

Question asked by ma qicheng on Jul 18, 2018
Latest reply on Jul 19, 2018 by igorpadykov

Hardware :IMX6Q

Software: Fsl Android 4.4.2

Devices connection :   USB 1(OTG port) set to host only for U disk .    USB2(host only port) connect with hup chip  + 4G  module sets + GPS

 

In our project , we have experienced a fatal usb error that occurs on our customed board, using a modified mainline Android 4.4.2 .and 3.0.35 Linux kernel .(We didn't modified any USB related Part)

And this issue happens Accidentally, Sometime it occurs every 4-5 hours Sometimes it doesn't produce for several weeks.

 

Is it already a known issue by NXP that we can have a patch to fix it. or are there any similar issuese ?

 

 

The kernel key Log(details in attachment, including  usb host registers dumping when it is produced(usb_register.csv) ):
<6>[10687.516530] usb 2-1:   oldspeed 0 udev->speed 3
<6>[10687.516543] usb 2-1: new high speed USB device number 38 using fsl-ehci
<6>[10687.667062] hub 2-0:1.0: perform initial device setup (usbcore-internal)
<3>[10687.667906] usb 2-1: device v2a45 p0c02 is not supported
<6>[10687.667917] usb 2-1: udev 38, busnum 2, minor = 165
<6>[10687.672229] hub 2-0:1.0: status: 0
<6>[10687.675561] hub 2-0:1.0: port 1, status 0100, change 0003, 12 Mb/s
<6>[10687.675573] usb 2-1: USB disconnect, device number 38
<3>[10687.677397] fsl-ehci fsl-ehci.0: fatal error
<3>[10687.678288] fsl-ehci fsl-ehci.0: HC died; cleaning up
<3>[10687.716525] hub 2-0:1.0: hub_port_status failed (err = -19)
<3>[10687.716539] hub 2-0:1.0: connect-debounce failed, port 1 disabled

 

 

 

Thanks in advance

Outcomes