July 2021 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1188485] Kernel 5.13.2-1 sees but does not see devices on Renesas PCIe 4-port USB controller
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188485 https://bugzilla.suse.com/show_bug.cgi?id=1188485#c16 --- Comment #16 from Takashi Iwai <tiwai(a)suse.com> --- At best check the kernel package change log. You can use the kernel in OBS Kernel:stable repo, but this is again an unofficial one, and won't work easily with Secure Boot. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188485] Kernel 5.13.2-1 sees but does not see devices on Renesas PCIe 4-port USB controller
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188485 https://bugzilla.suse.com/show_bug.cgi?id=1188485#c15 --- Comment #15 from Rick Kunath <rskunath(a)gmail.com> --- Great :) Thanks so much for your help and work on this problem. So the .4 kernel (that is the next release I think from what you wrote) won't get the revert, but the following one at .5 will? I'll be looking for that one. Thanks again. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186672] 1wire modules not built
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1186672 https://bugzilla.suse.com/show_bug.cgi?id=1186672#c29 --- Comment #29 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:2426-1: An update that solves 9 vulnerabilities, contains 8 features and has 101 fixes is now available. Category: security (important) Bug References: 1152489,1153274,1154353,1155518,1164648,1174978,1176771,1179610,1182470,1183712,1184212,1184685,1185195,1185486,1185589,1185675,1185677,1185701,1186206,1186463,1186666,1186672,1186752,1186949,1186950,1186951,1186952,1186953,1186954,1186955,1186956,1186957,1186958,1186959,1186960,1186961,1186962,1186963,1186964,1186965,1186966,1186967,1186968,1186969,1186970,1186971,1186972,1186973,1186974,1186976,1186977,1186978,1186979,1186980,1186981,1186982,1186983,1186984,1186985,1186986,1186987,1186988,1186989,1186990,1186991,1186992,1186993,1186994,1186995,1186996,1186997,1186998,1186999,1187000,1187001,1187002,1187003,1187038,1187050,1187067,1187068,1187069,1187072,1187143,1187144,1187171,1187263,1187356,1187402,1187403,1187404,1187407,1187408,1187409,1187410,1187411,1187412,1187413,1187452,1187554,1187595,1187601,1187795,1187834,1187867,1187883,1187886,1187927,1187972,1187980 CVE References: CVE-2020-26558,CVE-2020-36385,CVE-2020-36386,CVE-2021-0129,CVE-2021-0512,CVE-2021-0605,CVE-2021-33624,CVE-2021-34693,CVE-2021-3573 JIRA References: ECO-3691,SLE-11493,SLE-11796,SLE-17882,SLE-7926,SLE-8371,SLE-8389,SLE-8464 Sources used: SUSE Linux Enterprise Module for Realtime 15-SP2 (src): kernel-rt-5.3.18-42.2, kernel-rt_debug-5.3.18-42.2, kernel-source-rt-5.3.18-42.1, kernel-syms-rt-5.3.18-42.1, lttng-modules-2.10.10-1.5.1, oracleasm-2.0.8-1.3.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188394] Unable to use any USB port on Rock64
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188394 https://bugzilla.suse.com/show_bug.cgi?id=1188394#c3 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(jonasdcdm@mailbox | |.org) --- Comment #3 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- In the initial comment I see rk3399-pinebook-pro.dtb is this what you try to use as DTB? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188394] Unable to use any USB port on Rock64
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188394 https://bugzilla.suse.com/show_bug.cgi?id=1188394#c2 Jonas del Campo <jonasdcdm(a)mailbox.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jonasdcdm@mailbox | |.org) | --- Comment #2 from Jonas del Campo <jonasdcdm(a)mailbox.org> --- It's the SBC from Pine64, based on Rockchip RK3328, their wiki page has more details: https://wiki.pine64.org/wiki/ROCK64. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187874] Kernel hwmon modules nct6775 no longer fully recognises chip
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187874 https://bugzilla.suse.com/show_bug.cgi?id=1187874#c9 --- Comment #9 from Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> --- (In reply to Jean Delvare from comment #7) > Bob, do you have any kernel command line difference between 15.2 and 15.3? > Specifically, were you passing acpi_enforce_resources=lax before maybe? Nope, just what Suse supplies with the exception that I always change to splash=native and remove "quiet". I think saying kernel devs don't care is quite near the truth. The RH dev asked for comments about a possible solution that he was willing to develop and seems to have receives a sum total of zero responses. I think it is safe to assume this is not going to go anywhere in either the short on medium term and should therefore be closed as "unable to fix"... which does not exist... -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187874] Kernel hwmon modules nct6775 no longer fully recognises chip
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187874 https://bugzilla.suse.com/show_bug.cgi?id=1187874#c8 --- Comment #8 from Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> --- > Damn, then it's rather a "feature"... The upstream devs are interested in > hardening, but not interested in supporting minor chip functionality, > unfortunately. Well, I would argue the toss about that. The sensor chips are just one of others. It just so happens that this is the one being complained about. If the devs started hardening their kernel, I'm sure we would hear about this and others and fixes would come. y2start, numlockbios & X all complain about it. > > And why the heck is the man page kernel_lockdown.7 not supplied? opensuse > > has been complaining about this for a while. > > Which upstream project provides this man page? > > I had thought it was being complained about for years, but it has only been part of man-pages since 2020-10-16. Seems to have been published in 5.09 on 2020-11-01. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187874] Kernel hwmon modules nct6775 no longer fully recognises chip
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187874 https://bugzilla.suse.com/show_bug.cgi?id=1187874#c7 --- Comment #7 from Jean Delvare <jdelvare(a)suse.com> --- Bob, do you have any kernel command line difference between 15.2 and 15.3? Specifically, were you passing acpi_enforce_resources=lax before maybe? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187874] Kernel hwmon modules nct6775 no longer fully recognises chip
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187874 https://bugzilla.suse.com/show_bug.cgi?id=1187874#c6 --- Comment #6 from Jean Delvare <jdelvare(a)suse.com> --- sensors-detect has always been kind of a hack, and we all knew that accessing random I/O ports from user-space for probing purposes wouldn't fly forever. To be honest, I'm surprised it worked for so long. We would definitely need an in-kernel equivalent to probe for known Super-I/O devices and load their drivers automatically. I don't think it's fair to say that kernel developers don't care. The problem is that it's a major design change, and one which moves responsibility from lm-sensors developers (not that there's really anyone there at the moment, but that's a different issue) to kernel developers. What makes things even worse is that ACPI has been conflicting with native hwmon drivers on most x86 systems for the past decade, with apparently little interest from the industry. This may explain why kernel developers aren't thrilled to dive into this. That being said, the lockdown easily explains why sensors-detect no longer works, but that should have no impact on kernel drivers themselves. As you report that loading the nct6775 kernel driver no longer works, there must be a second problem. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187874] Kernel hwmon modules nct6775 no longer fully recognises chip
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187874 https://bugzilla.suse.com/show_bug.cgi?id=1187874#c5 --- Comment #5 from Takashi Iwai <tiwai(a)suse.com> --- (In reply to Bob Goddard from comment #4) > It's due to a locked down kernel. > > https://www.spinics.net/lists/linux-hwmon/msg08330.html > > Seems none of the kernel developers are interested as I assume they do not > harden the kernel. Damn, then it's rather a "feature"... The upstream devs are interested in hardening, but not interested in supporting minor chip functionality, unfortunately. The choice for now is simply to disable the secure boot -- at least for Leap 15.3. > And why the heck is the man page kernel_lockdown.7 not supplied? opensuse > has been complaining about this for a while. Which upstream project provides this man page? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188394] Unable to use any USB port on Rock64
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188394 https://bugzilla.suse.com/show_bug.cgi?id=1188394#c1 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jonasdcdm(a)mailbox.org Flags| |needinfo?(jonasdcdm@mailbox | |.org) --- Comment #1 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Please, could you clarify, which device this is: Rock64 or Pinebook-Pro-RK3399? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188327] kernel 5.13.1 is crashing on boot on armv7 due to 'Unhandled fault: alignment exception' in ecdsa_set_pub_key
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188327 https://bugzilla.suse.com/show_bug.cgi?id=1188327#c20 --- Comment #20 from Andreas F�rber <afaerber(a)suse.com> --- (In reply to Guillaume GARDET from comment #19) > (In reply to Dirk Mueller from comment #18) > > (In reply to Mian Yousaf Kaukab from comment #17) > > > > > > Did you send it to stable as well? I think this would need to be backported > > > > to stable releases. > I meant stable trees from kernel.org. The patch has a Fixes header, stable maintainers will pick it up automatically. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187874] Kernel hwmon modules nct6775 no longer fully recognises chip
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187874 https://bugzilla.suse.com/show_bug.cgi?id=1187874#c4 --- Comment #4 from Bob Goddard <opensuse(a)1.opensuse.bgcomp.co.uk> --- It's due to a locked down kernel. https://www.spinics.net/lists/linux-hwmon/msg08330.html Seems none of the kernel developers are interested as I assume they do not harden the kernel. And why the heck is the man page kernel_lockdown.7 not supplied? opensuse has been complaining about this for a while. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188327] kernel 5.13.1 is crashing on boot on armv7 due to 'Unhandled fault: alignment exception' in ecdsa_set_pub_key
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188327 https://bugzilla.suse.com/show_bug.cgi?id=1188327#c19 --- Comment #19 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Dirk Mueller from comment #18) > (In reply to Mian Yousaf Kaukab from comment #17) > > > > Did you send it to stable as well? I think this would need to be backported > > > to stable releases. > > No, but I can send it once it is accepted. > > In case this is about factory stable branch not kernel.org stable trees: > there is no need to do it for factory, the relevant code path has been > disabled from compilation, as long as it enters 5.14 we're fine. I meant stable trees from kernel.org. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188327] kernel 5.13.1 is crashing on boot on armv7 due to 'Unhandled fault: alignment exception' in ecdsa_set_pub_key
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188327 https://bugzilla.suse.com/show_bug.cgi?id=1188327#c18 --- Comment #18 from Dirk Mueller <dmueller(a)suse.com> --- (In reply to Mian Yousaf Kaukab from comment #17) > > Did you send it to stable as well? I think this would need to be backported > > to stable releases. > No, but I can send it once it is accepted. In case this is about factory stable branch not kernel.org stable trees: there is no need to do it for factory, the relevant code path has been disabled from compilation, as long as it enters 5.14 we're fine. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187514] File conflict with kernel-pae-devel-5.12.10-1.1.i686
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187514 https://bugzilla.suse.com/show_bug.cgi?id=1187514#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- I suppose the issue is gone with the recent update. Feel free to reopen if the problem persists. Thanks. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1187874] Kernel hwmon modules nct6775 no longer fully recognises chip
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1187874 https://bugzilla.suse.com/show_bug.cgi?id=1187874#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |opensuse(a)1.opensuse.bgcomp. | |co.uk Flags| |needinfo?(opensuse(a)1.opensu | |se.bgcomp.co.uk) --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- When you install and boot with openSUSE Leap 15.2 kernel on top of the current Leap 15.3 system, does the sensor start working again? Just to make sure. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188515] Renesas Technology Corp. uPD720201 USB 3.0 controller is broken
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188515 https://bugzilla.suse.com/show_bug.cgi?id=1188515#c3 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #3 from Takashi Iwai <tiwai(a)suse.com> --- The fix is merged to stable branch. It might miss the next update, but it'll be included after that. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188485] Kernel 5.13.2-1 sees but does not see devices on Renesas PCIe 4-port USB controller
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188485 https://bugzilla.suse.com/show_bug.cgi?id=1188485#c14 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #14 from Takashi Iwai <tiwai(a)suse.com> --- The fix is merged to stable branch. It might miss the next update, but it'll be included after that. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188485] Kernel 5.13.2-1 sees but does not see devices on Renesas PCIe 4-port USB controller
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188485 https://bugzilla.suse.com/show_bug.cgi?id=1188485#c13 Takashi Iwai <tiwai(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(rskunath(a)gmail.co | |m) | --- Comment #13 from Takashi Iwai <tiwai(a)suse.com> --- Thanks for the confirmation. I reported to the upstream, and the revert patch was already sent, and now gets merged to the upstream subsystem tree. So I pushed the revert patch to git stable branch for TW. It'll be included in the next update (although the upcoming 5.13.4 missed it). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188485] Kernel 5.13.2-1 sees but does not see devices on Renesas PCIe 4-port USB controller
by bugzilla_noreply＠suse.com 21 Jul '21

21 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188485 https://bugzilla.suse.com/show_bug.cgi?id=1188485#c12 --- Comment #12 from Rick Kunath <rskunath(a)gmail.com> --- I set the BIOS to disable secure boot and booted your test kernel. Everything came up, KDE and all. I tested the USB devices here that I use connected to the 4 Renesas USB ports and they all worked perfectly with your test kernel. One of these devices is a software defined radio and it makes heavy use of the USB bandwidth. It ran flawlessly on your test kernel, chugging right along without missing a beat. I went back to the previous kernel (.2) and the Renesas USB ports don't work. I hope that helps and thanks for your work on this :) -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188485] New: Kernel 5.13.2-1 sees but does not see deviceson Renesas PCIe 4-port USB controller
by bugzilla_noreply＠suse.com 20 Jul '21

20 Jul '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188485 Bug ID: 1188485 Summary: Kernel 5.13.2-1 sees but does not see deviceson Renesas PCIe 4-port USB controller Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: rskunath(a)gmail.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Kernel 5.13.2-1 sees the hardware but does not see devices on Renesas PCIe 4-port USB 3.0 controller. This worked prior to the last update. Motherboard USB ports operate as expected but the PCIe card that has the Renesas USB controllers is seen but cannot see devices that are plugged into it. Let me know if I can get additional information that will help with this please. Rick Kunath Below is additional info: <Output from lsusb -v, and this is one of the 4 controllers on the PCIe card> (YAST lists the device identifier as 65557 and the Device as uPD720202 Vendor ID is 71954 and the drivers are listed as xhci_pci) Bus 009 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Couldn't open device, some information will be missing Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 3.00 bDeviceClass 9 Hub bDeviceSubClass 0 bDeviceProtocol 3 bMaxPacketSize0 9 idVendor 0x1d6b Linux Foundation idProduct 0x0003 3.0 root hub bcdDevice 5.13 iManufacturer 3 Linux 5.13.2-1-default xhci-hcd iProduct 2 xHCI Host Controller iSerial 1 0000:11:00.0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 0x001f bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 0mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 9 Hub bInterfaceSubClass 0 bInterfaceProtocol 0 Full speed (or root) hub iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0004 1x 4 bytes bInterval 12 bMaxBurst 0 -- You are receiving this mail because: You are the assignee for the bug.

1 5

[Bug 1188485] Kernel 5.13.2-1 sees but does not see devices on Renesas PCIe 4-port USB controller
by bugzilla_noreply＠suse.com 20 Jul '21

20 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188485 https://bugzilla.suse.com/show_bug.cgi?id=1188485#c8 --- Comment #8 from Rick Kunath <rskunath(a)gmail.com> --- How do I get around the SHIM failure on boot? Likely secure boot doesn't like the signature or something? I'm secure booting using the BIOS to select the EFI partition on one of 2 hard disks, dual booting Tumbleweed and W10. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1184804] move kernel out of /boot
by bugzilla_noreply＠suse.com 20 Jul '21

20 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1184804 https://bugzilla.suse.com/show_bug.cgi?id=1184804#c41 --- Comment #41 from Swamp Workflow Management <swamp(a)suse.de> --- SUSE-SU-2021:2408-1: An update that solves 5 vulnerabilities and has 18 fixes is now available. Category: security (important) Bug References: 1065729,1085224,1094840,1152472,1152489,1170511,1179243,1183871,1184114,1184804,1185308,1185791,1187215,1187585,1188036,1188062,1188080,1188116,1188121,1188176,1188267,1188268,1188269 CVE References: CVE-2021-22555,CVE-2021-33909,CVE-2021-35039,CVE-2021-3609,CVE-2021-3612 JIRA References: Sources used: SUSE Linux Enterprise Module for Public Cloud 15-SP2 (src): kernel-azure-5.3.18-18.58.1, kernel-source-azure-5.3.18-18.58.1, kernel-syms-azure-5.3.18-18.58.1 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.

1 0

[Bug 1188485] Kernel 5.13.2-1 sees but does not see devices on Renesas PCIe 4-port USB controller
by bugzilla_noreply＠suse.com 20 Jul '21

20 Jul '21

https://bugzilla.suse.com/show_bug.cgi?id=1188485 https://bugzilla.suse.com/show_bug.cgi?id=1188485#c6 --- Comment #6 from Rick Kunath <rskunath(a)gmail.com> --- From the Journal entries log, found this repeated many times with the non-working kernel. I saw a few lines of failed firmware messages on boot with the non -working kernel, these don't appear with the working kernel. I'll test your test kernel as soon as it's ready. Thanks again :) <Pasted> Downloaded new firmware list. 39 entries found. xhci_hcd 0000:07:00.0: Direct firmware load for renesas_usb_fw.mem failed with error -2 xhci_hcd 0000:07:00.0: request_firmware failed: -2 [drm] Found VCE firmware/feedback version 50.0.1 / 17! -- You are receiving this mail because: You are the assignee for the bug.

1 0