Maximilian Luz
Maximilian Luz
The patchset was removed in 6.2.11 on Fedora and 6.2.12 on Debian and Arch. So if the issue still happens it's very likely unrelated.
Interesting. I still have no clue though what could cause this.
So based on the logs it looks like the panic occurs here: https://elixir.bootlin.com/linux/v6.2.15/source/kernel/exit.c#L837. The `WARN_ON(irqs_disabled())` above also gets triggered, leading to the two stack traces.
@mojyack Could you send a PR with those changes to our kernel repo?
Thanks! This is something you should submit to https://github.com/linux-surface/intel-precise-touch though. The kernel code is based on that.
The typecover on those devices should be connected via USB. SO maybe it's something related to USB runtime suspend?
@jonas2515 Would it make sense to add this to our wifi/bt patches?
This seems to be solved (https://github.com/linux-surface/linux-surface/issues/839#issuecomment-1140287888), so I'm closing this. I can't really speak to any initram-generator-specific hooks for including the modules. Having something like that would be nice, but...
Closing this as the steps are described in #605 and the wiki has been updated to be a bit clearer on the secure-boot/MOK topic. Please feel free to open a...
Any chance this could be related to https://github.com/linux-surface/linux-surface/issues/1059? I.e. can you try adding `usbcore.quirks=045e:09b5:g` to the kernel command line (replace `045e:09b5` with your respective device IDs) and see if that...