This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

USB3.0 might no response when runtime in K2E labeled by v1.0.2.1 with the latest MCSDK.

Hi experts,

My tester has spotted an issue about USB 3.0 on the K2E board when runtime, and it said " xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command", is that a hardware issue? Cause I just noticed there is a note in Release 3.1.3 notes , here is the quota:

"EVM Issue XTIEVMK2X Rev 2.0: NAND flash and USB occasionally fails"

Are they saying the same thing?

Please refer to P.S. for more error information, it's really weird because ltp test, posix test, mass data copy are all passed.

Cheers,

Zumeng

root@128:~# xhci-hcd xhci-hcd.0.auto: xHCI host not responding to stop endpoint command.
xhci-hcd xhci-hcd.0.auto: Assuming host is dying, halting host.
xhci-hcd xhci-hcd.0.auto: HC died; cleaning up
usb 1-1: USB disconnect, device number 2
EXT4-fs error (device sda1): __ext4_get_inode_loc:3940: inode #158747: block 526049: comm systemd: unable to read itable block
EXT4-fs error (device sda1): ext4_find_entry:1302: inode #340: comm systemd-udevd: reading directory lblock 0
EXT4-fs error (device sda1): ext4_find_entry:1302: inode #131073: comm systemd-udevd: reading directory lblock 0
EXT4-fs error (device sda1): ext4_find_entry:1302: inode #19: comm systemd-udevd: reading directory lblock 0
EXT4-fs error (device sda1): ext4_find_entry:1302: inode #19: comm crond: reading directory lblock 0
EXT4-fs error (device sda1): ext4_find_entry:1302: inode #19369: comm crond: reading directory lblock 0
EXT4-fs error (device sda1): ext4_find_entry:1302: inode #19: comm crond: reading directory lblock 0
EXT4-fs error (device sda1): ext4_find_entry:1302: inode #19: comm crond: reading directory lblock 0
Aborting journal on device sda1-8.
Buffer I/O error on device sda1, logical block 491520
lost page write due to I/O error on sda1
JBD2: Error -5 detected when updating journal superblock for sda1-8.
EXT4-fs error (device sda1): ext4_find_entry:1302: inode #8193: comm dhclient: reading directory lblock 0
EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
EXT4-fs (sda1): Remounting filesystem read-only


EXT4-fs error (device sda1): ext4_find_entry:1302: inode #19369: comm sh: reading directory lblock 0
root@128:~#
root@128:~#

  • Hi Zumeng Chen,

    At What stage you are getting this problem?...Being in root prompt what you tried to do and we got these errors?

    Are you getting this error always or occassionally? Able to reproduce the issue?

    Please provide the steps to reproduce the issue.

    zumeng Chen says said:
    Cause I just noticed there is a note in Release 3.1.3 notes , here is the quota: "EVM Issue XTIEVMK2X Rev 2.0: NAND flash and USB occasionally fails"

    We will try to reproduce the error first from our end. However, I will get more details about this "Known issue" from the factory team as well.

    Regards,

    Shankari

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    --------------------------------------------------------------------------------------------------------

  • Hi Shankari,

    1. Yes, this issue can be reproduced when system is in idle, no operations needed, and just waiting.
    2. I'm looking into this issue by myself, I'll let you know if any.
    3. Can you explain the note from TI Release 3.1.3 notes in page 12 and section '9.1.2 Known Issues', here is the quota:

    "EVM Issue XTIEVMK2X Rev 2.0: NAND flash and USB occasionally fails"

    Cheers,
    Zumeng
  • Hi Zumeng,

    We have tried on K2E and not able to see this error and not able to reproduce this issue.

    zumeng Chen says said:
    Cause I just noticed there is a note in Release 3.1.3 notes , here is the quota: "EVM Issue XTIEVMK2X Rev 2.0: NAND flash and USB occasionally fails"

    Forwarded to factory team. Yet to get answers from them.

    Thanks for your patience.

    Regards,

    Shankari

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    --------------------------------------------------------------------------------------------------------

  • Hi Zumeng,

    Got a reply from the factory team.

    For more details on K2E known issues, please refer to

    Regards,

    Shankari

    -------------------------------------------------------------------------------------------------------

    Please click the Verify Answer button on this post if it answers your question.

    --------------------------------------------------------------------------------------------------------

  • Thanks, really for your patience

    Cheers,
    Zumeng
  • Hi zumen,

    You are welcome.
    Get back to us for anytype of questions in future too.

    Regards,
    Shankari