linux-kernel - Re: Linux logs error `Failed to query (GET_CUR) UVC control X on unit Y: -75 (exp. 1).` (75 == EOVERFLOW?)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240719093819.GE12656@pendragon.ideasonboard.com>
Date: Fri, 19 Jul 2024 12:38:19 +0300
From: Laurent Pinchart <laurent.pinchart@...asonboard.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Paul Menzel <pmenzel@...gen.mpg.de>,
	Mauro Carvalho Chehab <mchehab@...nel.org>,
	linux-media@...r.kernel.org, linux-usb@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Ricardo Ribalda <ribalda@...omium.org>
Subject: Re: Linux logs error `Failed to query (GET_CUR) UVC control X on
 unit Y: -75 (exp. 1).` (75 == EOVERFLOW?)

(CC'ing Ricardo)

On Fri, Jul 19, 2024 at 08:05:35AM +0200, Greg KH wrote:
> 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?

We've merged quite a few changes for the uvcvideo driver recently.
Bisecting the problem would help greatly. It could also be helpful to
set the uvcvideo module 'trace' parameter to 0xffff (e.g. add
`uvcvideo.trace=0xffff` to the kernel command line, or unload and reload
the uvcvideo module with the parameter set to 0xffff) and give us the
additional messages printed to the kernel log.

Could you also provide the output of `lsusb -v -d 0c45:670c` (running as
root if possible) ?

-- 
Regards,

Laurent Pinchart