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-next>] [day] [month] [year] [list]
Message-ID: <af462e20-d158-4c5c-8dae-ce48f4192087@molgen.mpg.de>
Date: Fri, 19 Jul 2024 07:22:54 +0200
From: Paul Menzel <pmenzel@...gen.mpg.de>
To: Laurent Pinchart <laurent.pinchart@...asonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@...nel.org>, linux-media@...r.kernel.org,
 linux-usb@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Linux logs error `Failed to query (GET_CUR) UVC control X on unit Y:
 -75 (exp. 1).` (75 == EOVERFLOW?)

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:

     $ sudo dmesg | grep "usb 1-5"
     [    6.530358] usb 1-5: new high-speed USB device number 4 using 
xhci_hcd
     [    6.739200] usb 1-5: New USB device found, idVendor=0c45, 
idProduct=670c, bcdDevice=56.26
     [    6.739224] usb 1-5: New USB device strings: Mfr=2, Product=1, 
SerialNumber=0
     [    6.739234] usb 1-5: Product: Integrated_Webcam_HD
     [    6.739242] usb 1-5: Manufacturer: CN09GTFMLOG008C8B7FWA01
     [   13.138324] usb 1-5: Found UVC 1.00 device Integrated_Webcam_HD 
(0c45:670c)
     [   13.139881] usb 1-5: Failed to query (GET_CUR) UVC control 2 on 
unit 2: -75 (exp. 1).
     [   13.141689] usb 1-5: Failed to query (GET_CUR) UVC control 3 on 
unit 2: -75 (exp. 1).
     [   13.146931] usb 1-5: Failed to query (GET_CUR) UVC control 6 on 
unit 2: -75 (exp. 1).
     [   13.149257] usb 1-5: Failed to query (GET_CUR) UVC control 7 on 
unit 2: -75 (exp. 1).
     [   13.162456] usb 1-5: Failed to query (GET_CUR) UVC control 8 on 
unit 2: -75 (exp. 1).
     [   13.176789] usb 1-5: Failed to query (GET_CUR) UVC control 9 on 
unit 2: -75 (exp. 1).
     [   13.178409] usb 1-5: Failed to query (GET_CUR) UVC control 10 on 
unit 2: -75 (exp. 1).
     [   13.180053] usb 1-5: Failed to query (GET_CUR) UVC control 1 on 
unit 2: -75 (exp. 1).
     [   13.182754] usb 1-5: Failed to query (GET_CUR) UVC control 4 on 
unit 2: -75 (exp. 1).
     [   13.333317] usb 1-5: Failed to query (GET_CUR) UVC control 4 on 
unit 1: -75 (exp. 1).

According to the archived logs, it’s the first time they are logged. 
It’s from `uvc_query_ctrl()` in `drivers/media/usb/uvc/uvc_video.c`:

     int uvc_query_ctrl(struct uvc_device *dev, u8 query, u8 unit,
                         u8 intfnum, u8 cs, void *data, u16 size)
     {
         int ret;
         u8 error;
         u8 tmp;

         ret = __uvc_query_ctrl(dev, query, unit, intfnum, cs, data, size,
                                 UVC_CTRL_CONTROL_TIMEOUT);
         if (likely(ret == size))
                 return 0;

         if (ret != -EPIPE) {
                 dev_err(&dev->udev->dev,
                         "Failed to query (%s) UVC control %u on unit 
%u: %d (exp. %u).\n",
                         uvc_query_name(query), cs, unit, ret, size);
                 return ret < 0 ? ret : -EPIPE;
         }

That function has not been changed recently. Does error number 75 mean

     #define EOVERFLOW       75      /* Value too large for defined data 
type */


from `include/uapi/asm-generic/errno.h`?

Is my hardware failing, or did something change?


Kind regards,

Paul
View attachment "20240719--linux-6.10+.txt" of type "text/plain" (82632 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ