From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working.
Date: Thu, 08 Oct 2020 14:35:56 +0000 [thread overview]
Message-ID: <bug-209137-208809-50R6LR7DlY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209137-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209137
--- Comment #11 from Alan Stern (stern@rowland.harvard.edu) ---
Did you run lsusb as root? I ask because the report descriptors are missing
from the output, and this is typically what happens when lsusb is run as a
normal user, not root.
Also, the dmesg logs indicate that you weren't running the -stable kernel
versions. It's possible that this problem has already been fixed in those
versions. For the same reason, you might try running a 5.8 kernel.
If none of those work, you can always try running git-bisect to find the
particular commit which caused the problem to appear somewhere between 5.0 and
5.4.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-10-08 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-209137-208809@https.bugzilla.kernel.org/>
2020-09-28 9:09 ` [Bug 209137] USB is not working since update from 5.0 to 5.3.0-26. And with 5.4 still not working bugzilla-daemon
2020-09-28 18:22 ` bugzilla-daemon
2020-09-28 20:30 ` bugzilla-daemon
2020-10-07 7:29 ` bugzilla-daemon
2020-10-07 20:29 ` bugzilla-daemon
2020-10-07 20:37 ` bugzilla-daemon
2020-10-08 14:35 ` Alan Stern
2020-10-09 8:31 ` Benjamin Tissoires
2020-10-08 14:35 ` bugzilla-daemon [this message]
2020-10-08 16:44 ` bugzilla-daemon
2020-10-09 8:37 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-209137-208809-50R6LR7DlY@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.