linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:52:38 +0100	[thread overview]
Message-ID: <20191107145238.0e7c9388@endymion> (raw)
In-Reply-To: <20191107143941.1649db47@endymion>

On Thu, 7 Nov 2019 14:39:41 +0100, Jean Delvare wrote:
> On Wed, 23 Oct 2019 17:20:16 +0300, Laurent Pinchart wrote:
> > 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.

One more data point: the log flood happens when the uvcvideo driver is
loaded but the webcam is unused. If I start e.g. cheese, it takes a
long time to start but once started, the log flood stops. As soon as I
stop cheese, the log flood starts again.

-- 
Jean Delvare
SUSE L3 Support

  reply	other threads:[~2019-11-07 13:52 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
2019-11-07 13:52     ` Jean Delvare [this message]
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=20191107145238.0e7c9388@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 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).