I am getting the same bug. 21' System76 Gazelle (gaze16), Ubuntu 20.04LTS.
I am getting this bug with the new INC-004 Belkin CONNECT 11-in-1 USB-C
Multiport Hub. Ethernet and HDMI display output are working but USB throws
errors.
-uname -a
5.11.0-7620-generic
Hello.
I have this bug too.
[ 944.504716] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
When I had 5.4.0-74 core this bug was unconditional, i.e. it was when even no
one usb devices was plugged.
Know I have 5.8.0-55 and this bug occurs only when second usb monitor is
plugged (it
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable. Maybe the USB
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable. Maybe the USB
Hello,
I am also affected by this bug.
no device plugged in but have the message flooding my log.
would be happy to provide further info if it helps
(ubuntu server 20.04LTS)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@dannf: Yes, this bug sure is a tricky one.
Most of these reports will be due to failing / faulty / non-spec
complaint USB devices or cables, like the original reason for this bug
being opened. Although, there have been some reports where user's
systems do go back to working when they install my
@mruffell: Is there any specific info you'd like people to continue to
capture if they see this symptom? If so, maybe we put those steps in the
Description.
I also wonder if this bug has become too unwieldly due to the number of
reports w/ likely different underlying causes, that we can never
I'm also seeing this issue when connecting an android device via usb
adb.
[ +0.996452] usb 2-2.4-port2: Cannot enable. Maybe the USB cable is
bad?
I am unsure how to proceed, I tried changing cables and ports but this
error message does not go away.
--
You received this bug notification
** Changed in: linux (Ubuntu Focal)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable. Maybe the USB
I'm also affected by this bug. I just did a fresh install of Xubuntu
20.04.1 and see the issue.
In my case it's "usb usb2-port1: Cannot enable. Maybe the USB cable is
bad?".
There are no USB devices connected at all, so I get the bug with only
the motherboard root hub present. I can make the log
Sorry, that was not the kernel. It was (is?) a bad usb socket. I plugged
the monitor to a different usb-c port and it works without complaints on
all tried kernels (5.6, 5.8, 5.9).
Device: "20NYS8QG0B (LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s)"
--
You received this bug notification because you
I have an identical error message on Debian Bullseye after kernel
upgrade:
- 5.8.0-3-amd64: works well "enough"
- 5.9.0-1-amd64: experiencing similar symptoms when Dell S2719DC monitor is
connected.
By "similar symptoms", I mean:
- everything that is plugged to USB in the monitor works well.
-
@mruffell
> Reproduced on the test kernel? The one that I built in the ppa?
Yes 100% sure, took the laptop out of suspend on both kernels.
> We need to know what device is plugged into "port 2" of that hub, i.e.
"usb 4-2". Can you try determine what the device is?
Believe me I've tried. Have
Pau, please try "usbcore.quirks=" described here:
https://www.kernel.org/doc/html/latest/admin-guide/kernel-parameters.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression]
For issues that happens on xHCI instead of EHCI, please try the following
commit:
https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git/commit/?h=for-usb-linus=513696247d734d74f835fc4dce6307c72a5c58d1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi @pau-capdevila
Your USB problem is unrelated to the issue in this bug, since your USB
device fails to do the initial handshake and enumeration.
> usb 1-1.2.1: device descriptor read/64, error -32
>From /usr/include/asm-generic/errno-base.h, Error -32 is:
#define EPIPE 32 /*
Facing the same on a recently upgraded 20.04. The device is an HP
printer.
[ 1459.458363] usb 1-1.2.1: new full-speed USB device number 12 using ehci-pci
[ 1459.538367] usb 1-1.2.1: device descriptor read/64, error -32
[ 1459.726396] usb 1-1.2.1: device descriptor read/64, error -32
[
Hi @jeremyn54
> the error can be consistently reproduced on both signed and testing
kernels.
Reproduced on the test kernel? The one that I built in the ppa? If
that's the case, then "usb: handle warm-reset port requests on hub
resume" might not be to blame after all.
I had a look at your kernel
Ok I have found the trigger for the usb error on my system. I did not
have to insert/remove any device as such, but simply put the laptop into
suspend mode. At the moment it resumes from suspend, the error can be
consistently reproduced on both signed and testing kernels.
There are a number of
@jeremyn54
Thanks for testing the test kernel. I suppose this means that "usb:
handle warm-reset port requests on hub resume" is still causing us
trouble.
@everyone
Can you please unplug all USB devices from your computer, and connect
them one by one until you find the device which causes the
@mruffell
I had the aforementioned USB error almost constantly spamming my syslog.
Since I have installed your kernel, it is gone completely. It was not
affecting USB hub function in my case, however was quite annoying.
jeremy@730U3E:~$ uname -rv
5.4.0-42-generic
@bamoqi, @speedym, @david-sinnott-morgan:
I have prepared a test kernel based on 5.4.0-42-generic, for Ubuntu 20.04 in
the following ppa.
It hasn't finished building yet, Launchpad is taking a long time. Please make
sure it has finished building before installing.
@Milan: I don't doubt that there maybe also be a driver issue, but that
wasn't the root cause of this issue.
@All: It might be helpful to know, for each of these cases, if what you are
seeing is also correlated with the patch we reverted (and are planning to
reintroduce) in older releases. To
I can also confirm that upgrading to kernel 5.8.0 didn't fix the
problem.
@dannf: I have tried three different USB cables with exactly the same
results. I'm pretty sure the problem is in the USB kernel drivers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
fyi, the system for which I originally filed this bug was conclusively
determined to have an out-of-spec USB cable, for which the manufacturer
is providing replacements.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can also confirm that the bug is not fixed, and I can also confirm two
Bamoqi's posts - I'm testing it on various mobile phones and it's
messing up my development workflow as phones sometimes do not connect
when attached to USB cable.
I have tried three different USB-A -> USB-C cables from
To add to above:
When the error is on, running `sudo lshw` causes the program to hang:
fox:~% sudo lshw
USB<-- program hang like this
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
I can confirm this issue in 20.04 linux-image-5.4.0-42. This message
only appear for my usb3.1 gen1 type-c hub when it is connected on boot.
If I re-plug the hub after boot, the message stops. It doesn't appear
for another connected usb3 type-a hub.
In /var/log/syslog, it prints every 4 seconds:
Also appears in focal, generating a syslog warning about every 5
seconds, which makes using a tty console quite difficult:
$ uname -r
5.4.0-33-generic
$ tail /var/log/syslog
Jun 4 21:48:16 alpe kernel: [ 1350.631168] usb usb4-port1: Cannot enable.
Maybe the USB cable is bad?
Jun 4 21:48:20
I can confirm this issue still being present in 20.04, kernel
5.4.0-31-generic
[ +4.459108] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
[ +4.469264] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
[ +4.421456] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
I don't know if this is the right place but I don't think this is fixed
in 20.04 (focal).
[517928.746183] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[517929.718230] usb usb3-port1: Cannot enable. Maybe the USB cable is bad?
[517929.718327] usb usb3-port1: attempt power cycle
This bug was fixed in the package linux - 4.15.0-76.86
---
linux (4.15.0-76.86) bionic; urgency=medium
* bionic/linux: 4.15.0-76.86 -proposed tracker (LP: #1860123)
* Integrate Intel SGX driver into linux-azure (LP: #1844245)
- [Packaging] Add systemd service to load
This bug was fixed in the package linux - 5.3.0-29.31
---
linux (5.3.0-29.31) eoan; urgency=medium
* eoan/linux: 5.3.0-29.31 -proposed tracker (LP: #1860119)
* Integrate Intel SGX driver into linux-azure (LP: #1844245)
- [Packaging] Add systemd service to load intel_sgx
This bug was fixed in the package linux - 5.0.0-40.44
---
linux (5.0.0-40.44) disco; urgency=medium
* disco/linux: 5.0.0-40.44 -proposed tracker (LP: #1859724)
* use-after-free in i915_ppgtt_close (LP: #1859522) // CVE-2020-7053
- SAUCE: drm/i915: Fix use-after-free when
Verification for the revert:
lab@hostname:~$ uname -a
Linux hostname 4.15.0-75-generic #85-Ubuntu SMP Wed Jan 15 00:31:23 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
lab@hostname:~$ dmesg | grep "Cannot enable"
lab@hostname:~$ dmesg | grep "Maybe"
lab@hostname:~$
Booting the bionic kernel
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag
We reverted the offending patch while we continue to work towards root
causing the failure. The revert will cause this bug to be resolved, so
I've opened bug 1859873 to track fixing and reapplying the patch (+ any
fixes). I suggest we move further technical discussion there.
** Description
** Changed in: linux (Ubuntu Bionic)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable. Maybe the USB
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
disco' to 'verification-done-disco'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
eoan' to 'verification-done-eoan'. If the problem still exists, change
the tag
I happened to notice these same errors on an arm64 server in our lab,
running the 4.15.0-73-generic kernel. (A Cavium crb2s system named
'recht'). While this could be unrelated - perhaps an actual bad USB
cable - it isn't an error I'd noticed before on this system, and it
happened to be running a
** Changed in: linux (Ubuntu Disco)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable. Maybe the USB
** Changed in: linux (Ubuntu Eoan)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable. Maybe the USB
** Attachment added: "'dmesg | grep -e usb -e xhci -e hub' w/ usbcore.dyndbg=+p"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+attachment/5318666/+files/dmesg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@kaihengfeng - sorry for the delay over the US holidays. I don't have
physical access to the system myself, but I've made the request to a
user who does.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Can you please attach dmesg with kernel parameter `usbcore.dyndbg=+p`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856608
Title:
[Regression] usb usb2-port2: Cannot enable. Maybe the USB cable
Running upstream 5.5-rc2 mainline build:
$ dmesg | grep -e usb -e xhci -e hub
[ 13.482690] usbcore: registered new interface driver usbfs
[ 13.486685] usbcore: registered new interface driver hub
[ 13.490894] usbcore: registered new device driver usb
[ 20.767117] xhci_hcd :00:14.0:
** Description changed:
This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81.
[Impact]
USB port unusable and boot time takes ~5 minutes longer to complete.
+
+ Kernel emits messages like:
+ usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
[Test Case]
git bisect reports:
0b6a70743beacb15516ef9572b40c93b8b3892d3 is the first bad commit
commit 0b6a70743beacb15516ef9572b40c93b8b3892d3
Author: Jan-Marek Glogowski
Date: Fri Feb 1 13:52:31 2019 +0100
usb: handle warm-reset port requests on hub resume
--
You received this bug notification because
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status:
50 matches
Mail list logo
