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 14:50:12 +0000 [thread overview]
Message-ID: <bug-219681-208809-0Plbeipg2Z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219681-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219681
Michał Pecio (michal.pecio@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michal.pecio@gmail.com
--- Comment #1 from Michał Pecio (michal.pecio@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?
You can see the mapping between USB buses and PCI controllers with
ls -l /sys/bus/usb/devices/usb*
udisks2 collects SMART data and this is known to cause problems with some
combinations of USB controllers and disk enclosures in UAS mode. It usually
recovers after the reset, so not sure why
[ 131.357007] sd 0:0:0:0: Device offlined - not ready after error recovery
The network issue is possibly unrelated, because in this case the hub simply
reports complete disconnection of the device and it comes back a moment later
for unclear reasons.
I wonder if any of that is preceded by low level USB errors? Maybe try again
with some dynamic debug:
echo 'func handle_tx_event +p' >/proc/dynamic_debug/control
echo 'func handle_transferless_tx_event +p' >/proc/dynamic_debug/control
I presume this is not a regression and there are no kernel versions where it
works correctly?
--
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:[~2025-01-15 14:50 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 ` bugzilla-daemon [this message]
2025-01-15 15:16 ` [Bug 219681] " bugzilla-daemon
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-0Plbeipg2Z@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).