All of lore.kernel.org
 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: Fri, 01 May 2020 19:21:41 +0000	[thread overview]
Message-ID: <bug-207219-208809-zFHl5370YJ@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 #18 from Alan Stern (stern@rowland.harvard.edu) ---
Okay.  You need to start the usbmon data collection _before_ you do the insmod,
so that the trace can capture _all_ of the USB traffic.  And since the
usbmon/4u file doesn't exist before you do the insmod, you will have to capture
the trace from the usbmon/0u file instead (that file reports all the USB
traffic on all the buses).

Also, it wouldn't hurt to get a copy of the system log showing what happens
when you run the test.  Before running insmod, do:

   dmesg -C >/dev/null

After you run insmod, wait a little while (something like 10 seconds), then
stop the usbmon trace, and do:

  dmesg >logfile.txt

You don't even need to do the writes to the bConfigurationValue file.  Let's
see what the usbmon trace and the logfile show.

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

  parent reply	other threads:[~2020-05-01 19:21 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
2020-04-30 23:26 ` bugzilla-daemon
2020-05-01 19:21 ` bugzilla-daemon [this message]
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-zFHl5370YJ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.