Arch Linux

aytekinar

Member

From: Stockholm

Registered: 2013-12-19

Posts: 25

[SOLVED] "Maybe the USB cable is bad?"

Hi,

I have a similar problem to that mentioned in https://bbs.archlinux.org/viewtopic.php?id=242906. Different from that topic, which is also older than 1 year old as of today, I used to have my `dmesg` free from such errors. Moreover, when I boot my system using a USB drive with Mint in it, `dmesg` does not show any such errors. I would appreciate any help.

Below are some useful output from my system (borrowing from the other topic)

~> dmesg | grep -i cable
[    8.656263] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   12.696263] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   16.743179] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   20.783218] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   24.823209] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   28.866581] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   32.909659] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   36.966308] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   41.016258] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   45.056263] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   49.096309] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   53.139590] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?
[   57.186253] usb usb2-port1: Cannot enable. Maybe the USB cable is bad?

~> lsusb -t
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
    |__ Port 1: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 2, Class=Chip/SmartCard, Driver=, 12M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 6: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 6: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
    |__ Port 7: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 8: Dev 5, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 8: Dev 5, If 0, Class=Wireless, Driver=btusb, 12M

Last edited by aytekinar (2020-02-10 20:37:50)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,232

Re: [SOLVED] "Maybe the USB cable is bad?"

On a guess i'd say some dust or dirt in the port that makes it think there's a signal where there isn't. Is there supposed to be a device attached to that port?

aytekinar

Member

From: Stockholm

Registered: 2013-12-19

Posts: 25

Re: [SOLVED] "Maybe the USB cable is bad?"

Thank you for your fast response.

No, I start receiving these messages in `dmesg` at boot-up, regardless of whether there is a device attached or not.

On a guess i'd say some dust or dirt in the port that makes it think there's a signal where there isn't.

Then, why do you think I am not seeing these messages when I boot my system with a USB stick?

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,232

Re: [SOLVED] "Maybe the USB cable is bad?"

Thank you for your fast response.

No, I start receiving these messages in `dmesg` at boot-up, regardless of whether there is a device attached or not.

Then it might be a kernel bug, when did this start? If just with the 5.5 update try a downgrade to 5.4/the LTS kernel. Could also be a harmless power surge/energy issue during early boot, if stuff works otherwise I wouldn't be too worried. You could also try and disable USB suspend: https://wiki.archlinux.org/index.php/Po … utosuspend

Then, why do you think I am not seeing these messages when I boot my system with a USB stick?

Which kernel? And I'd assume that you occupy that port with said USB stick.

Last edited by V1del (2020-02-05 12:13:23)

aytekinar

Member

From: Stockholm

Registered: 2013-12-19

Posts: 25

Re: [SOLVED] "Maybe the USB cable is bad?"

Then it might be a kernel bug, when did this start?

I cannot recall exactly, but it was a recent one.
I have tried downgrading to linux-lts (with nvidia-lts, too), and now everything seems to be working.

I had the most recent kernels all the time. How should we proceed? Do you want me to walk through a couple of steps to diagnose the problem (i.e., pinpoint what aspect of the new kernel could have resulted in this) or should I simply mark the thread as "[SOLVED]"?

Thank you very much! It's good to know that I do not have a hardware failure, at least

Oh, by the way, the USB ports seem to be working (it was not only a single port issue, so I doubt I was occupying some USB port when using the stick) even though I receive the corresponding message in the new kernel. However, my YubiKey, for instance, was working **very** slow. When trying to ssh to servers or decrypting emails, I need to access my YubiKey, and it takes around 20-30 seconds until my laptop can access/read the key