Linux USB
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-usb@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Linux logs error `Failed to query (GET_CUR) UVC control X on unit Y: -75 (exp. 1).` (75 == EOVERFLOW?)
Date: Fri, 19 Jul 2024 08:05:35 +0200	[thread overview]
Message-ID: <2024071939-wrought-repackage-f3c5@gregkh> (raw)
In-Reply-To: <af462e20-d158-4c5c-8dae-ce48f4192087@molgen.mpg.de>

On Fri, Jul 19, 2024 at 07:22:54AM +0200, Paul Menzel wrote:
> Dear Linux folks,
> 
> 
> Today, starting the Intel Kaby Lake laptop Dell XPS 13 9360/0596KF, BIOS
> 2.21.0 06/02/2022 with
> 
>     Bus 001 Device 004: ID 0c45:670c Microdia Integrated Webcam HD
> 
> Linux “6.11-rc0” (v6.10-8070-gcb273eb7c839) logged UVC errors:

Does 6.10-final have the same issue?  If not, can you use 'git bisect'
to track down the offending commit?

There have not been any USB changes in Linus's tree yet, but there have
been a bunch of media changes, so perhaps something in the uvc driver is
causing this?

thanks,

greg k-h

  reply	other threads:[~2024-07-19  6:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-19  5:22 Linux logs error `Failed to query (GET_CUR) UVC control X on unit Y: -75 (exp. 1).` (75 == EOVERFLOW?) Paul Menzel
2024-07-19  6:05 ` Greg KH [this message]
2024-07-19  9:38   ` Laurent Pinchart
2024-07-19 11:33     ` Paul Menzel
2024-07-19 12:31       ` Paul Menzel
2024-07-22  8:01         ` Ricardo Ribalda

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=2024071939-wrought-repackage-f3c5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=pmenzel@molgen.mpg.de \
    /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