linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 207219] [BISECTED] Sony Vaio laptop built-in ricoh webcam no longer found on Fedora 31 with 5.4.11 kernel
Date: Tue, 14 Apr 2020 15:19:46 +0000	[thread overview]
Message-ID: <bug-207219-208809-baqN7jZtII@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207219-208809@https.bugzilla.kernel.org/>

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

--- Comment #4 from Alan Stern (stern@rowland.harvard.edu) ---
In fact, I think your problem isn't caused by commit 7cbdf96cda1f at all.  It's
caused by commit bd0e6c9614b9 ("usb: hub: try old enumeration scheme first for
high speed devices").  The bisection settled on 7cbdf96cda1f because the bug it
fixed was hiding your real problem.

Try starting with a vanilla (bad) kernel and reverting commit bd0e6c9614b9;
let's see if that fixes the camera problem.

Incidentally, the usbmon traces didn't help very much.  The trace under the bad
kernel showed that the camera had already gotten messed up before the trace
began, probably when the camera was probed during boot.  The camera bug (and it
is a bug in the camera, not in the kernel) showed up in the trace in two ways:
The camera connected to the USB bus at full speed instead of high speed, and
when it was connected it didn't respond to any requests.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-04-14 15:19 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-12 23:35 [Bug 207219] New: [BISECTED] Sony Vaio laptop built-in ricoh webcam no longer found on Fedora 31 with 5.4.11 kernel bugzilla-daemon
2020-04-13 17:16 ` [Bug 207219] " bugzilla-daemon
2020-04-13 17:54 ` bugzilla-daemon
2020-04-13 17:54 ` bugzilla-daemon
2020-04-14 15:19 ` bugzilla-daemon [this message]
2020-04-14 21:59 ` bugzilla-daemon
2020-04-15  1:26   ` Alan Stern
2020-04-15  1:26 ` bugzilla-daemon
2020-04-16 23:22 ` bugzilla-daemon
2020-04-17 15:24 ` bugzilla-daemon
2020-04-25 21:51 ` bugzilla-daemon
2020-04-26 14:25 ` bugzilla-daemon
2020-04-26 17:55 ` bugzilla-daemon
2020-04-26 21:07 ` bugzilla-daemon
2020-04-27 17:26 ` bugzilla-daemon
2020-04-28 18:44 ` bugzilla-daemon
2020-04-28 22:17 ` bugzilla-daemon
2020-04-30 16:49 ` bugzilla-daemon
2020-04-30 23:26 ` bugzilla-daemon
2020-05-01 19:21 ` bugzilla-daemon
2020-05-01 21:55 ` bugzilla-daemon
2020-05-02  1:52 ` bugzilla-daemon
2020-05-02  2:57 ` 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-207219-208809-baqN7jZtII@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.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).