https://bugzilla.kernel.org/show_bug.cgi?id=218416 --- Comment #33 from Paul Menzel (pmenzel+bugzilla.kernel.org@xxxxxxxxxxxxx) --- (In reply to Nickolas Gupton from comment #32) > this issue has been reported starting in 5.16 on the original bug linked that > they closed and asked for someone to make a new issue if it was still > present. Bug 215167 [1] reports a regression in Linux 5.14, and the referenced openSUSE report says at the end it should be fixed in 5.16.1. Nickolas, thank you for attaching the full Linux logs. As the error from the bug title is not present in the log, I recommend to close this issue, and create a new one for your problem with a descriptive title like *Bluetooth only starts working after reloading btusb and btintel*, attaching all the files there. If you could bisect [3] the commit, that would even get you there faster. The Bluetooth device can even be passed to a virtual machine, and if the problem is reproducible there, bisection is quite fast [4][5]. I am sorry about this, but unfortunately, the comments by others on probably different issues, make it very hard and time consuming to understanding the actual issue. It looks like the maintainers are overworked and the subsystem has not enough resources. Still if you buy a device with Intel hardware (and even better a device with official GNU/Linux support), it’s valid to expect that Intel hardware works also on GNU/Linux. [1]: https://bugzilla.kernel.org/show_bug.cgi?id=215167 [2]: https://bugzilla.opensuse.org/show_bug.cgi?id=1193124 [3]: https://www.kernel.org/doc/html/latest/admin-guide/verify-bugs-and-bisect-regressions.html [4]: https://lore.kernel.org/linux-bluetooth/5891f0d5-8d51-9da5-7663-718f301490b1@xxxxxxxxxxxxx/ [5]: https://lore.kernel.org/lkml/d7206e12-1b99-c3be-84f4-df22af427ef5@xxxxxxxxxxxxx/ -- You may reply to this email to add a comment. You are receiving this mail because: You are the assignee for the bug.
