Florian Fainelli (2022-05-11): > How about we get a chance to fix this? Where, when and how was this even > reported? I started downstream: https://bugs.debian.org/1010365 did some more debugging and moved upstream (the link is mentioned in each commit message) roughly 10 days ago: https://bugzilla.kernel.org/show_bug.cgi?id=215925 As I wrote in response to Thorsten Leemhuis (regressions@), who looped in a bunch of people: I had spent so much time bisecting that issue that I concentrated on trying to summarize it properly in Bugzilla, failing to check reporting guidelines and best practices (I even missed the Regression: yes flag in my initial submission). Again, sorry for failing to notify everyone in the first place, I tried to have the contents of the report squared away. That being said, as mentioned on regressions@ & linux-pci@, I'm happy to test any attempts at fixing the issue, instead of a full-on revert. I'll also try to track mainline more closely, so that such obvious issues don't go unnoticed for ~1.5 release cycles. Cheers, -- Cyril Brulebois (kibi@debian.org) D-I release manager -- Release team member -- Freelance Consultant