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: Thu, 30 Apr 2020 16:49:17 +0000 [thread overview]
Message-ID: <bug-207219-208809-bF35fzPTJj@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 #16 from Alan Stern (stern@rowland.harvard.edu) ---
There's something wrong with what you did, but I can't tell what. To start
with, before ehci-pci.ko was loaded there should have been no usbmon/3u or
usbmon/4u files, so your cat commands should have failed. Those filenames
correspond directly to the USB bus numbers, and your lsusb output shows only
buses 1 and 2.
For another, the device numbering is off. On bus 3, device 1 is the root hub
and device 2 is the integrated hub -- fine. But then the Foxconn and Ricoh
devices should have been numbers 3 and 4, not 6 and 7. Clearly something
happened before you started your monitoring.
Also, your usbmon3 trace shows the webcam working after it was initialized
using the old scheme! It's pretty hard to tell what that means, though,
especially since the actions shown in the trace probably weren't the first time
the webcam had been initialized since the last cold reboot.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-04-30 16:49 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
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 [this message]
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-bF35fzPTJj@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).