FS#59175 - [linux] uvcvideo: Failed to query (GET_INFO) UVC control 11 on unit 1: -32 (exp. 1).

Attached to Project: Arch Linux
Opened by Deactivated account (TechnicalTotoro) - Thursday, 28 June 2018, 19:49 GMT
Last edited by Toolybird (Toolybird) - Sunday, 28 May 2023, 06:38 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

After upgrading to linux-hardened version 4.17 (I think) on startup I am is starting to see the following messages:

Jun 28 10:18:40 <computer-name> kernel: uvcvideo: Found UVC 1.00 device Integrated Camera (5986:0295)
Jun 28 10:18:40 <computer-name> kernel: uvcvideo: Failed to query (GET_INFO) UVC control 11 on unit 1: -32 (exp. 1).
Jun 28 10:18:40 <computer-name> kernel: uvcvideo: Failed to query (GET_INFO) UVC control 13 on unit 1: -32 (exp. 1).
Jun 28 10:18:40 <computer-name> kernel: uvcvideo 3-1.5:1.0: Entity type for entity Processing 2 was not initialized!
Jun 28 10:18:40 <computer-name> kernel: uvcvideo 3-1.5:1.0: Entity type for entity Camera 1 was not initialized!
Jun 28 10:18:40 <computer-name> kernel: uvcvideo 3-1.5:1.0: Entity type for entity Extension 4 was not initialized!
Jun 28 10:18:40 <computer-name> kernel: input: Integrated Camera: Integrated C as /devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.0/input/input9
Jun 28 10:18:40 <computer-name> kernel: usbcore: registered new interface driver uvcvideo
Jun 28 10:18:40 <computer-name> kernel: USB Video Class driver (1.1.1)


Although the above is from the system log.
This task depends upon

Closed by  Toolybird (Toolybird)
Sunday, 28 May 2023, 06:38 GMT
Reason for closing:  No response
Additional comments about closing:  Plus it's old and stale. If still an issue, please report upstream.
Comment by loqs (loqs) - Thursday, 28 June 2018, 20:38 GMT
With what package version of linux-hardened? If 4.17.3.a-1 please confirm the issue is not present on linux 4.17.3-1.
Comment by Deactivated account (TechnicalTotoro) - Thursday, 28 June 2018, 20:58 GMT
It is present there as well. I remember that it started with the last upgrade before that. I think it was from 4.16 to 4.17, but I could be mistaken, sorry not to be able to be more specific.
Comment by loqs (loqs) - Thursday, 28 June 2018, 21:03 GMT
If it is present in both linux and linux-hardened it is not a linux-hardened issue. Please bisect between 4.16 and 4.17 to locate the commit that caused the issue or try 4.18-rc2 to see if it is already fixed.
If it is not already fixed then please work with upstream to fix the issue.
Comment by mattia (nTia89) - Monday, 28 February 2022, 16:41 GMT
I have had this issue in the past and it was purely cosmetic.

Anyway it was fixed some time ago. Is it still valid for you?

Loading...