From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217744] Resume: "usb usb2-port3: Cannot enable. Maybe the USB cable is bad?" Tiger Lake-LP Thunderbolt 4 [8086:9a13]
Date: Tue, 01 Aug 2023 14:03:20 +0000 [thread overview]
Message-ID: <bug-217744-208809-2MEohKLaCy@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217744-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217744
--- Comment #4 from TJ (linux@iam.tj) ---
(In reply to Bagas Sanjaya from comment #3)
> Does v6.0 not have this issue? Or is it hardware issue too?
Cannot say. The system when presented has Debian 12 amd64 which uses v6.1
kernel; Trying latest mainline was to test if the issue has been fixed since.
I've asked the owner to update the PC to the most recent firmware in case there
is some issue there but I do not see anything in the firmware changelog to
indicate it.
It seems to be the Lenovo Thinkpad USB3.x dock - I have seen other people
mention something like this in support chat channels but never focused on those
issues myself so no idea if this is a systemic problem.
Hopefully the owner can contribute more precise detail here with the precise
make/model/ID of the external dock.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2023-08-01 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 10:28 [Bug 217744] New: "usb usb2-port3: Cannot enable. Maybe the USB cable is bad?" Tiger Lake-LP Thunderbolt 4 [8086:9a13] bugzilla-daemon
2023-08-01 10:29 ` [Bug 217744] " bugzilla-daemon
2023-08-01 10:29 ` bugzilla-daemon
2023-08-01 10:55 ` [Bug 217744] Resume: " bugzilla-daemon
2023-08-01 14:03 ` bugzilla-daemon [this message]
2023-08-01 20:58 ` bugzilla-daemon
2023-08-02 5:02 ` 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-217744-208809-2MEohKLaCy@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).