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 219681] ASUS Zenbook S 14 UX5406SA: Unstable USB connection on USB-A port under certain condition
Date: Wed, 15 Jan 2025 15:16:35 +0000	[thread overview]
Message-ID: <bug-219681-208809-gHOO5l4VWd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219681-208809@https.bugzilla.kernel.org/>

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

--- Comment #2 from dantmnf2@gmail.com ---
> Are the working and not working ports on the same USB bus, or on different
> ones? Perhaps two different types of USB controllers?

They are on different controllers:
    # readlink /sys/bus/usb/devices/usb*
    ../../../devices/pci0000:00/0000:00:0d.0/usb1
    ../../../devices/pci0000:00/0000:00:0d.0/usb2
    ../../../devices/pci0000:00/0000:00:14.0/usb3
    ../../../devices/pci0000:00/0000:00:14.0/usb4
    # lspci
    ...
    00:0d.0 USB controller: Intel Corporation Lunar Lake-M Thunderbolt 4 USB
Controller (rev 10)
    ...
    00:14.0 USB controller: Intel Corporation Lunar Lake-M USB 3.2 Gen 2x1 xHCI
Host Controller (rev 10)
    ...

> I wonder if any of that is preceded by low level USB errors? Maybe try again
> with some dynamic debug:

It do have some messages like "Stopped on Transfer TRB for slot 4 ep 6" and
"Transfer error for slot 9 ep 0 on endpoint"

> I presume this is not a regression and there are no kernel versions where it
> works correctly?

This is a relatively new platform and kernels before 6.12 cannot give a usable
system.

-- 
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:[~2025-01-15 15:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-11  7:19 [Bug 219681] New: ASUS Zenbook S 14 UX5406SA: Unstable USB connection on USB-A port under certain condition bugzilla-daemon
2025-01-15 14:50 ` [Bug 219681] " bugzilla-daemon
2025-01-15 15:16 ` bugzilla-daemon [this message]
2025-01-15 15:17 ` bugzilla-daemon
2025-01-15 17:24 ` bugzilla-daemon
2025-01-15 17:52 ` bugzilla-daemon
2025-01-20 15:40 ` bugzilla-daemon
2025-01-20 17:13 ` bugzilla-daemon
2025-01-20 17:13 ` bugzilla-daemon
2025-01-21 12:06 ` bugzilla-daemon
2025-01-22 15:36 ` bugzilla-daemon
2025-01-23 15:27 ` bugzilla-daemon
2025-01-23 17:45 ` bugzilla-daemon
2025-01-24  1:29 ` bugzilla-daemon
2025-01-27  9:05 ` bugzilla-daemon
2025-01-27  9:14 ` 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-219681-208809-gHOO5l4VWd@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).