Hi, Pascal Hambourg <pas...@plouf.fr.eu.org> (2025-05-11): > The log confirms that the issue is caused by check-missing-firmware > when unloading and reloading the xhci-pci-renesas module.
Thanks for looking/confirming. > I was able to reproduce it on my laptop by unloading and reloading > ehci-pci. I naively assumed that a mounted partition on the USB drive > would mark all drivers in the path as used and prohibit unloading > them, but it seems I was wrong. Lots of fun can be had with USB… :( > The Renesas USB controller seems to work fine without it, and > according to the kernel log, a default firmware is loaded from > non-volatile memory: > > xhci-pci-renesas 0000:a3:00.0: failed to load firmware renesas_usb_fw.mem, > *fallback to ROM* > > So I think this is the way to go. The fix is trivial, do you wish to > take care of it or shall I prepare a MR ? That might leave other users on the side of the road, since the ROM might not be available or might not have been equipped with firmware data. Seeing how that particular system would (presumably) work fine without the check+reload plus how bad the side effects are, it might be prudent to just ignore renesas_usb_fw.mem / xhci-pci-renesas as a first step. I'm not sure if the iwl-debug-yoyo.bin code is the best way to do that, but feel free to look into proposing an MR (based or not on that code path, as you see fit). For users that would actually miss the firmware (file and/or ROM) and need it, meaning they would be missing devices, it's important that we are able to put the finger on the issue. As long as we have the “failed to load […]” log line on the kernel, and/or whatever “let's ignore this particular case” in check-missing-firmware, I would consider this topic covered. Cheers, -- Cyril Brulebois (k...@debian.org) <https://debamax.com/> D-I release manager -- Release team member -- Freelance Consultant
signature.asc
Description: PGP signature
