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, 6 Aug 2026 00:23:36 +0200 [thread overview]
Message-ID: <20260806002336.6f968841.michal.pecio@gmail.com> (raw)
In-Reply-To: <anOiUYwnfuXC0lSY@spiral>
On Wed, 5 Aug 2026 14:11:20 -0700, Bart Nagel wrote:
> OK. Attached are the first ~700 lines of the trace file.
>
> That whole thing is 17M, and is here for 48 hours from now in case it
> is more illuminating: https://tmpfiles.org/wAwAIQxuuahs/trace.txt
It seems that Missed Service Error pointers are about equally likely to
be 0x10 or 0x20 after the previous event.
And the events are usually Success, Short Packet is less common.
Considering that also roughly half of TDs are 0x20 long, we can choose
to be optimists and assume that (when it chooses not to report zero),
your HC actually reports correct addresses, except for the known narrow
problem case of MSE after Short Packet on an early TRB.
Or we can choose to be pessimists and say that 0x20 can be bogus too,
and then we wrongly skip two TDs instead of one, but three are always
missed at a time (for some reason) so no worry, until something will
change and suddenly only one TD is missed.
Not sure if I have any answer which option is true without another test
patch and compilation cycle. Maybe let's be optimistic if it works and
no errors are logged, only dynamic debug noise.
Regards,
Michal
next prev parent reply other threads:[~2026-08-05 22:23 UTC|newest]
Thread overview: 21+ 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
2026-07-30 22:16 ` Bart Nagel
2026-08-05 19:01 ` Bart Nagel
2026-08-05 20:36 ` Michal Pecio
2026-08-05 21:11 ` Bart Nagel
2026-08-05 22:23 ` Michal Pecio [this message]
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=20260806002336.6f968841.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox