From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 216543] kernel NULL pointer dereference usb_hcd_alloc_bandwidth
Date: Mon, 17 Oct 2022 17:59:48 +0000 [thread overview]
Message-ID: <bug-216543-208809-AR52CPrAl3@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216543-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216543
--- Comment #7 from Nazar Mokrynskyi (nazar@mokrynskyi.com) ---
Created attachment 303022
--> https://bugzilla.kernel.org/attachment.cgi?id=303022&action=edit
Kernel log with uvc-trace patch applied
I'm on 6.0.2 and seemingly get this even more frequently with good cable and no
extra adapters. So I patched 6.0.2 with uvc-trace above and reproduced it
within a few minutes.
USB seems to reset, often camera stops or freezes in the browser, but the light
on the camera itself remains on. Sometimes I can enable/disable/enable camera
for it to reboot, but the last time I did that in the log I got null pointer
de-reference again.
Please let me know if there is any other information I can provide and what
could be the root cause of this annoying behavior.
--
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:[~2022-10-17 17:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 18:53 [Bug 216543] New: kernel NULL pointer dereference usb_hcd_alloc_bandwidth bugzilla-daemon
2022-09-30 8:53 ` Greg KH
2022-09-30 8:53 ` [Bug 216543] " bugzilla-daemon
2022-09-30 11:32 ` bugzilla-daemon
2022-09-30 11:32 ` bugzilla-daemon
2022-09-30 11:38 ` bugzilla-daemon
2022-09-30 12:32 ` Greg KH
2022-09-30 12:32 ` bugzilla-daemon
2022-09-30 14:28 ` bugzilla-daemon
2022-10-17 17:59 ` bugzilla-daemon [this message]
2022-10-17 21:25 ` Alan Stern
2022-10-18 5:40 ` Ricardo Ribalda
2022-10-18 5:42 ` Ricardo Ribalda
2022-10-18 14:46 ` Alan Stern
2022-10-18 15:02 ` Laurent Pinchart
2022-10-19 1:35 ` Ricardo Ribalda
2022-10-19 1:44 ` Laurent Pinchart
2022-10-19 4:22 ` Ricardo Ribalda
2022-10-19 15:08 ` Alan Stern
2022-10-20 0:57 ` Ricardo Ribalda
2022-10-20 14:25 ` Alan Stern
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-216543-208809-AR52CPrAl3@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).