From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 220460] Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110`
Date: Sun, 17 Aug 2025 22:15:57 +0000 [thread overview]
Message-ID: <bug-220460-208809-bYN8FNUVkp@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220460-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220460
--- Comment #2 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
> 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
I wanted to attach the contents of `/sys/kernel/debug/tracing/trace`, but
Bugzilla (Nginx) aborts with error 413 Request Entity Too Large for the 4 MB
file despite listing 5 MB as limit. So, I uploaded it [1], until Bugzilla setup
is fixed.
[1]:
https://owww.molgen.mpg.de/~pmenzel/20250817--dell-xps-13-9370--linux-6.16.1-messages--tracing-trace.txt
--
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-08-17 22:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-17 8:09 [Bug 220460] New: Plugging USB-C adapter into one port results in `Failed to set U2 timeout to 0x3f,error code -110` bugzilla-daemon
2025-08-17 17:18 ` [Bug 220460] " bugzilla-daemon
2025-08-17 22:15 ` bugzilla-daemon [this message]
2025-08-18 8:13 ` bugzilla-daemon
2025-08-18 8:26 ` bugzilla-daemon
2025-08-21 14:57 ` bugzilla-daemon
2025-08-21 15:05 ` bugzilla-daemon
2025-08-21 15:26 ` bugzilla-daemon
2025-08-22 12:12 ` bugzilla-daemon
2025-08-22 12:14 ` bugzilla-daemon
2025-08-22 13:20 ` bugzilla-daemon
2025-08-25 9:16 ` bugzilla-daemon
2025-08-25 9:16 ` 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-220460-208809-bYN8FNUVkp@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