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: Mon, 20 Jan 2025 15:40:20 +0000	[thread overview]
Message-ID: <bug-219681-208809-3gQ1DT0mtn@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219681-208809@https.bugzilla.kernel.org/>

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

Mathias Nyman (mathias.nyman@linux.intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mathias.nyman@linux.intel.c
                   |                            |om

--- Comment #6 from Mathias Nyman (mathias.nyman@linux.intel.com) ---
Could you share both dynamic debug and trace of this case?
If possible remove as all extra usb devices before triggering this, as logs
gets clogged and hard to read.

mount -t debugfs none /sys/kernel/debug
echo 'module xhci_hcd =p' >/sys/kernel/debug/dynamic_debug/control
echo 'module usbcore =p' >/sys/kernel/debug/dynamic_debug/control
echo 81920 > /sys/kernel/debug/tracing/buffer_size_kb
echo 1 > /sys/kernel/debug/tracing/events/xhci-hcd/enable
echo 1 > /sys/kernel/debug/tracing/tracing_on
< Reproduce issue, connect problematic device >
Send output of dmesg
Send content of /sys/kernel/debug/tracing/trace

I'll try to find reproduce this on our local Lunar Lake one I get my hands on
some failing devices, my current USB3 ethernet adapter unfortunately has a ASIX
chip, not Realtek.

-- 
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-20 15:40 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
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 [this message]
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-3gQ1DT0mtn@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).