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:~#