Linux USB
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221963] uvcvideo: Realtek Integrated_Webcam_HD (0bda:5696) RGB sensor never delivers frame data after STREAMON
Date: Fri, 04 Sep 2026 09:04:07 +0000	[thread overview]
Message-ID: <bug-221963-208809-bifchbEWyz@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221963-208809@https.bugzilla.kernel.org/>

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

Michał Pecio (michal.pecio@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |michal.pecio@gmail.com

--- Comment #2 from Michał Pecio (michal.pecio@gmail.com) ---
(In reply to Chandra Joshi from comment #0)
> Created attachment 310780 [details]
> Open the file I made (uvcvideo_bug_report.md), copy everything from "##
> Summary" onward, and paste it into the description box.
I would rather not do that :)

(In reply to Chandra Joshi from comment #1)
> Isochronous transfers on Ii:1:004:1 complete successfully (status 0),
> confirming USB-level data transfer genuinely occurs — this is not a
> transport/bandwidth failure.
> However, every single isochronous packet returned across the entire
> 10-second capture has payload length exactly 12 bytes — i.e. only the bare
> UVC payload header, with zero pixel data ever included:
> C Zi:1:004:1 0:1:5224:0 32 0:0:12 0:2814:12 0:5628:12 ... = 0c8c0000
> 0000eab5 86008a02 00000000...
> 
> (0c = header length 12; 8c = bmHeaderInfo, decodes to EOH=1, SCR=1, PTS=1,
> FID=0, EOF=0 — both FID and EOF remain constant/unset for the entire
> capture, consistent with zero frame boundaries ever being signaled)
Do these 12 byte packets keep flowing forever until user application is turned
off, or do they stop unexpectedly at some earlier time?

If this is truly a problem with the camera or UVC driver, not with USB itself,
then you have reported it in the wrong place. Follow instructions here

https://docs.kernel.org/admin-guide/reporting-issues.html

and email uvcvideo maintainers with linux-media in Cc.

-- 
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:[~2026-09-04  9:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04  6:45 [Bug 221963] New: uvcvideo: Realtek Integrated_Webcam_HD (0bda:5696) RGB sensor never delivers frame data after STREAMON bugzilla-daemon
2026-09-04  7:03 ` [Bug 221963] " bugzilla-daemon
2026-09-04  9:04 ` bugzilla-daemon [this message]

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-221963-208809-bifchbEWyz@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