linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 10:55:50 +0000	[thread overview]
Message-ID: <bug-217744-208809-HtgdJEQK18@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217744-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217744

Bagas Sanjaya (bagasdotme@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bagasdotme@gmail.com

--- Comment #3 from Bagas Sanjaya (bagasdotme@gmail.com) ---
(In reply to TJ from comment #0)
> Created attachment 304746 [details]
> kernel log v6.5-rc4
> 
> On resume from suspend, since at least v6.1 and including v6.5-rc4 - an
> external USB Ethernet device fails to resume due to:
> 
> usb usb2-port3: Cannot enable. Maybe the USB cable is bad?
> 
> Linux version 6.5.0-rc4+debian+tj (root@linux-builder) (gcc (Debian
> 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #67 SMP
> PREEMPT_DYNAMIC Mon Jul 31 22:25:03 BST 2023
> 
> DMI: LENOVO 20W6001WUS/20W6001WUS, BIOS N34ET53W (1.53 ) 08/31/2022
> 
> The affected owner (nickname 'Chosen_') and myself worked in Matrix Linux
> room to narrow down the cause by building and testing v6.5-rc4 when the
> Debian distro v6.1 showed the problem. There is no difference in the
> symptoms or the kernel messages between the versions.
> 
> Attached is the kernel log, `lspci -nnk` and `lsusb -vt`. The device is:
> 
> /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
>     ID 1d6b:0003 Linux Foundation 3.0 root hub
>     |__ Port 3: Dev 5, If 0, Class=Hub, Driver=hub/4p, 10000M
>         ID 17ef:30ab Lenovo 
>         |__ Port 1: Dev 6, If 0, Class=Vendor Specific Class, Driver=r8152,
> 5000M
>             ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit
> Ethernet Adapter
>         |__ Port 3: Dev 7, If 0, Class=Hub, Driver=hub/4p, 10000M
>             ID 17ef:30ad Lenovo 
> 
> Which seems to be connected via the host controller on
> 
> 00:0d.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4
> USB Controller [8086:9a13] (rev 01)
>         Subsystem: Lenovo Tiger Lake-LP Thunderbolt 4 USB Controller
> [17aa:22c9]
>         Kernel driver in use: xhci_hcd

Does v6.0 not have this issue? Or is it hardware issue too?

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-08-01 11:02 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 ` bugzilla-daemon [this message]
2023-08-01 14:03 ` [Bug 217744] Resume: " bugzilla-daemon
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-HtgdJEQK18@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).