On 28.05.24 22:54, Mike wrote: > On 29.04.24 20:46, Linux regression tracking (Thorsten Leemhuis) wrote:> >> Well, did you try what I suggested earlier (see above) and check if a >> revert of 6083089ab00631617f9eac678df3ab050a9d837a ontop of latest 6.1.y >> helps? > > I hope you don't mind if I jump into the conversation trying to help. On the contrary, thx for providing the needed information! > I tried reverting 6083089ab00631617f9eac678df3ab050a9d837a > on top of6.1.91 and it looks much better: it's been 10 days, and the BT > and the system are stable. > Previously, I encountered the mentioned "kernel BUG" at each boot, Might be a good idea to share it, the developers might want to confirm it's really the same bug. > and I was unable to stop/kill the bluetoothd process. > Let me know if/how I can help further. Jeremy Lainé already confirmed that 6.9-rc5[1] worked fine and that another fix for the culprit did not help[2]. Therefore we just have three options left: 1. test another fix for the culprit I found on lore -- but note, this is just a shot in the dark https://lore.kernel.org/all/20240411151929.403263-1-kovalev@xxxxxxxxxxxx/ 2. revert 6083089ab00631617f9eac678df3ab050a9d837a in 6.1.y if that is still possible, does not create a even bigger regression, or leads to some security vulnerability 3. motivate the BT developers to look into this (some other patch the culprit depends on might be missing), even if this strictly speaking is a problem they are free to ignore. Maybe give "1." a try; then we'll ask Greg for "2.", unless this discussion or something else leads to "3." Ciao, Thorsten [1] https://lore.kernel.org/all/CADRbXaA2yFjMo=_8_ZTubPbrrmWH9yx+aG5pUadnk395koonXg@xxxxxxxxxxxxxx/ [2] https://lore.kernel.org/all/CADRbXaBkkGmqnibGvcAF2YH5CjLRJ2bnnix1xKozKdw_Hv3qNg@xxxxxxxxxxxxxx/
