New: regression 5.10.49→5.10.52: Direct firmware load for renesas_usb_fw.mem failed with error -2

https://bugzilla.kernel.org/show_bug.cgi?id=214155

            Bug ID: 214155
           Summary: regression 5.10.49→5.10.52: Direct firmware load for
                    renesas_usb_fw.mem failed with error -2
           Product: Drivers
           Version: 2.5
    Kernel Version: 5.10.52
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: USB
          Assignee: [email protected]
          Reporter: [email protected]
        Regression: No

My laptop's internal webcam stopped being detected at some point in the last weeks. I do not use that webcam often and various things happened in that period, such as minor kernel updates and a BIOS update, so it was not immediately clear where the cause lay. After some investigation, I found the following in my logs:

xhci_hcd 0000:06:00.0: Direct firmware load for renesas_usb_fw.mem failed with error -2
xhci_hcd 0000:06:00.0: request_firmware failed: -2
xhci_hcd: probe of 0000:06:00.0 failed with error -2

Reverting to an earlier kernel version (5.10.52→5.10.49), this message disappears and the webcam is detected again. This makes me suspect there is some kind of regression after 5.10.49.

A related report can be found at

https://forums.lenovo.com/t5/Other-Linux-Discussions/Possible-1-34-BIOS-bug-on-P14s-AMD/m-p/5089865

There, the assumption is that this is related to the BIOS update. Given my tests, there certainly is a kernel component to the issue.

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

This should already be resolved on the latest 5.10.y kernel release. Please upgrade and let us know if that does not solve the issue.

thanks,

greg k-h

https://bugzilla.kernel.org/show_bug.cgi?id=214155

--- Comment #1 from Greg Kroah-Hartman ([email protected]) ---

This should already be resolved on the latest 5.10.y kernel release. Please upgrade and let us know if that does not solve the issue.

thanks,

greg k-h

You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.