From: Michal Pecio <michal.pecio@gmail.com>
To: Bart Nagel <bart@tremby.net>
Cc: linux-usb@vger.kernel.org, mathias.nyman@intel.com
Subject: Re: Regression: webcam freezing since Linux 6.15
Date: Thu, 30 Jul 2026 23:59:53 +0200 [thread overview]
Message-ID: <20260730235953.2d51e0cc.michal.pecio@gmail.com> (raw)
In-Reply-To: <amuTKengDzr0IL6b@spiral>
On Thu, 30 Jul 2026 11:13:59 -0700, Bart Nagel wrote:
> At 2026-07-30 13:08:14 +0200, Michal Pecio wrote:
> > I'm slightly curious what exactly happens there (probably MSE after
> > Short Packet on a single-TRB TD), and whether Missed Service Error
> > may point at a Link TRB, because the current fix wouldn't handle
> > that and the stream could still hang. So your failure rate may
> > actually be reduced to 1/255 of what it was, but still not zero.
> >
> > If possible, please boot the patched kernel again and run it for
> > a little longer. If it fails, post dmesg starting from the "Miss
> > service interval error" line which is followed by "All TDs skipped".
> >
> > And while that is running, also collect another log:
> >
> > cd /sys/kernel/tracing/
> > echo 1 > events/xhci-hcd/xhci_handle_event/enable
> > echo 1 > tracing_on
> > grep -B5 Missed trace_pipe | tee /tmp/trace
> >
> > This is supposed to log 6 lines for every Missed Service Error, so
> > it will grow, but not terribly fast.
>
> Before I make a bad assumption and collect a useless log, please
> confirm for me exactly which debugging I should enable. Just the two
> you gave above, or also one or both of the ones I was using before:
>
> echo "func handle_tx_event +p" >/proc/dynamic_debug/control
> echo 0xff >/sys/module/uvcvideo/parameters/trace
Yes, please keep handle_tx_event, otherwise xhci_hcd debug messages
won't show up. UVC trace is not that important.
next prev parent reply other threads:[~2026-07-30 21:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 22:10 Regression: webcam freezing since Linux 6.15 Bart Nagel
2026-07-22 22:22 ` Michal Pecio
2026-07-22 23:23 ` Bart Nagel
2026-07-23 6:14 ` Michal Pecio
2026-07-23 6:19 ` Michal Pecio
2026-07-23 21:02 ` Bart Nagel
2026-07-23 22:45 ` Bart Nagel
2026-07-25 9:59 ` Michal Pecio
2026-07-27 20:23 ` Bart Nagel
2026-07-27 22:31 ` Michal Pecio
2026-07-29 19:37 ` Bart Nagel
2026-07-30 11:08 ` Michal Pecio
2026-07-30 14:46 ` Mathias Nyman
2026-07-30 18:13 ` Bart Nagel
2026-07-30 21:59 ` Michal Pecio [this message]
2026-07-30 22:16 ` Bart Nagel
2026-07-22 23:30 ` Bart Nagel
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=20260730235953.2d51e0cc.michal.pecio@gmail.com \
--to=michal.pecio@gmail.com \
--cc=bart@tremby.net \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.