What on earth is this message about?
usb usb2-port8: Cannot enable. Maybe the USB cable is bad?
earlier in dmesg it says:
usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.05 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: xHCI Host Controller usb usb2: Manufacturer: Linux 5.5.15-200.fc31.x86_64 xhci-hcd usb usb2: SerialNumber: 0000:00:14.0
On the internet I can lookup the vendor and product and it says:
USB 1D6B Linux Foundation 0003 3.0 root hub
Which makes it sound as if usb2 is some kind of virtual hardware in the kernel, so how do I check this virtual cable that may be bad?
DMESG shows this cable bad message once every 5 seconds, which is a bit annoying.
On Sat, 11 Apr 2020 18:37:28 -0400 Tom Horsley wrote:
DMESG shows this cable bad message once every 5 seconds, which is a bit annoying.
OK, I pulled every USB device one at a time till dmesg stopped printing this error. The device that finally made it stop was a USB 3 backup drive. I plugged it back in to the exact same usb port, and the messages did not start back up.
On 4/11/20 3:57 PM, Tom Horsley wrote:
On Sat, 11 Apr 2020 18:37:28 -0400 Tom Horsley wrote:
DMESG shows this cable bad message once every 5 seconds, which is a bit annoying.
OK, I pulled every USB device one at a time till dmesg stopped printing this error. The device that finally made it stop was a USB 3 backup drive. I plugged it back in to the exact same usb port, and the messages did not start back up.
I was just about to suggest that procedure as well as some other debugging options. Check out "lsusb -t".
On Sat, Apr 11, 2020 at 06:57:10PM -0400, Tom Horsley wrote:
On Sat, 11 Apr 2020 18:37:28 -0400 Tom Horsley wrote:
DMESG shows this cable bad message once every 5 seconds, which is a bit annoying.
OK, I pulled every USB device one at a time till dmesg stopped printing this error. The device that finally made it stop was a USB 3 backup drive. I plugged it back in to the exact same usb port, and the messages did not start back up.
computers and their hardware being fickle, it may well start up again once you actually try using it for backup. :(
On Sat, 11 Apr 2020 19:58:33 -0400 Fred Smith wrote:
computers and their hardware being fickle, it may well start up again once you actually try using it for backup. :(
Weirdly, the backups seem to have been working fine, so I'm very confused by what it might have been complaining about.
On 4/11/20 5:08 PM, Tom Horsley wrote:
On Sat, 11 Apr 2020 19:58:33 -0400 Fred Smith wrote:
computers and their hardware being fickle, it may well start up again once you actually try using it for backup. :(
Weirdly, the backups seem to have been working fine, so I'm very confused by what it might have been complaining about.
"lsusb -t" will show you what ports things are plugged into. The backups might have been working but was it running at USB3 speeds or just USB2? The cable might be perfectly fine for USB2, but it sounds like the system thought it should be a USB3 device, but it wasn't working.
On Sat, 11 Apr 2020 17:12:55 -0700 Samuel Sieb wrote:
"lsusb -t" will show you what ports things are plugged into. The backups might have been working but was it running at USB3 speeds or just USB2? The cable might be perfectly fine for USB2, but it sounds like the system thought it should be a USB3 device, but it wasn't working.
Maybe it is just USB drive weirdness. Each drive I have apparently includes a hub, not just a direct drive connection (some sort of nonsense related to the Windows encryption stuff I utterly ignore). Usb 2 port 8 is apparently the hub, not the drive:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 5: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 8: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 5000M
I swear the next time I get a new backup drive it is simply going to be one of those devices you can plug a sata disk into to talk over USB. Protect me from all the "helpful" features :-).
On Sat, 2020-04-11 at 20:27 -0400, Tom Horsley wrote:
On Sat, 11 Apr 2020 17:12:55 -0700 Samuel Sieb wrote:
"lsusb -t" will show you what ports things are plugged into. The backups might have been working but was it running at USB3 speeds or just USB2? The cable might be perfectly fine for USB2, but it sounds like the system thought it should be a USB3 device, but it wasn't working.
Maybe it is just USB drive weirdness. Each drive I have apparently includes a hub, not just a direct drive connection (some sort of nonsense related to the Windows encryption stuff I utterly ignore). Usb 2 port 8 is apparently the hub, not the drive:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 10000M |__ Port 3: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 5: Dev 3, If 0, Class=Mass Storage, Driver=usb-storage, 5000M |__ Port 8: Dev 4, If 0, Class=Hub, Driver=hub/4p, 5000M |__ Port 1: Dev 5, If 0, Class=Hub, Driver=hub/4p, 5000M
I swear the next time I get a new backup drive it is simply going to be one of those devices you can plug a sata disk into to talk over USB. Protect me from all the "helpful" features :-).
Good luck with that. I just returned one of those because Linux didn't even recognise it when I plugged it in (nothing in the journal, nothing in dmesg).
poc
On Sat, 2020-04-11 at 18:57 -0400, Tom Horsley wrote:
OK, I pulled every USB device one at a time till dmesg stopped printing this error. The device that finally made it stop was a USB 3 backup drive. I plugged it back in to the exact same usb port, and the messages did not start back up.
It could have had a grotty plug & socket connection on that one, and scraping it out and in cleared it.
-
Fred Smith -
Patrick O'Callaghan -
Samuel Sieb -
Tim -
Tom Horsley