From: Jean Delvare <jdelvare@suse.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-usb@vger.kernel.org
Subject: Re: Logitech C270 webcam floods the log
Date: Thu, 7 Nov 2019 14:39:41 +0100 [thread overview]
Message-ID: <20191107143941.1649db47@endymion> (raw)
In-Reply-To: <20191023142016.GA1904@pendragon.ideasonboard.com>
Hi Laurent,
Thank you very much for your quick reply and sorry for getting back to
you only today, your message got moved to a different folder by a
filter rule I did not remember of.
On Wed, 23 Oct 2019 17:20:16 +0300, Laurent Pinchart wrote:
> On Wed, Oct 23, 2019 at 03:18:59PM +0200, Jean Delvare wrote:
> > When my Logitech C270 webcam is plugged in, my kernel log gets filled
> > with this message:
> >
> > usb 3-4.1: reset high-speed USB device number 4 using xhci_hcd
> >
> > every 5 seconds. I have the same problem on 3 different Intel-based
> > computers (different generations), using 2 different webcams, same
> > brand "same model".
> >
> > Is Logitech doing crappy hardware these days, or are we doing something
> > wrong? Is there any way to know the reason that triggers the reset?
>
> Is this before or after the uvcvideo driver gets involved ? One easy way
> to check is to move the uvcvideo.ko module out of the way so that it
> doesn't get loaded automatically (or just blacklist it in
> /etc/modprobe.d/) and then plug the camera.
I did as you suggested and it turns out that the "reset high-speed USB
device" messages are not printed originally, they start being printed
right after the uvcvideo kernel driver gets loaded. So that would be a
problem with the uvcvideo driver?
When unloading the uvcvideo driver, there's one more "reset high-speed
USB device" message and then no more.
For what it's worth, 2 things worth noting in the kernel log when the
device is being detected:
usb 3-12: set resolution quirk: cval->res = 384
(...)
uvcvideo: Found UVC 1.00 device <unnamed> (046d:0825)
"<unnamed>" seems weird. On the other hand lsusb properly lists it as:
Bus 003 Device 004: ID 046d:0825 Logitech, Inc. Webcam C270
I an older C270 webcam (3 year old, different package) connected to
another machine, USB device ID is the same, I compared the verbose
output of lsusb and one difference stands out:
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 14 Video
bInterfaceSubClass 2 Video Streaming
bInterfaceProtocol 0
iInterface 0
VideoStreaming Interface Descriptor:
(...)
- bmaControls( 0) 27
- bmaControls( 1) 27
- bmaControls( 2) 27
+ bmaControls( 0) 0
+ bmaControls( 1) 4
+ bmaControls( 2) 4
(- is the new webcam, + is the old one)
I don't know if this tells anything useful though.
Thanks,
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2019-11-07 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 13:18 Logitech C270 webcam floods the log Jean Delvare
2019-10-23 14:20 ` Laurent Pinchart
2019-11-07 13:39 ` Jean Delvare [this message]
2019-11-07 13:52 ` Jean Delvare
2019-11-07 14:56 ` Oliver Neukum
2019-11-07 17:49 ` Jean Delvare
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=20191107143941.1649db47@endymion \
--to=jdelvare@suse.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mchehab@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.