[Critical Regression] KPatch 0.13.6 causes immediate kernel panic on boot, 0.13.5 works #33
Description
Problem Description
On a Redmi K60 device, installing KPatch-Next-Module version 0.13.6 causes an immediate kernel panic during boot, resulting in an unrecoverable bootloop. Version 0.13.5 of the same module works correctly in the exact same environment.
Important Note: The exact same Magisk configuration (same modules and settings) works perfectly with version 0.13.5, so the issue is specific to changes in version 0.13.6, not a general environment conflict.
Environment Details
- Device: Redmi K60
- Kernel:
5.10.246-SoraYumeKernel-android12-9-g7649975a1c07-dirty - Android Version: ColorOS 15 (Unofficial ported ROM, based on Android 12 kernel)
- Architecture: aarch64
- Root Solution: Magisk Alpha v30600 (Kitsune Mask)
- Zygisk: Enabled
- Problem Version: KPatch-Next-Module 0.13.6
- Working Version: KPatch-Next-Module 0.13.5
Steps to Reproduce
- Install KPatch-Next-Module 0.13.6 on the specified environment.
- Reboot the device.
- Observe boot sequence.
Actual Results
- Boot animation (MIUI logo) appears for approximately 1 second.
- Screen turns black, device reboots immediately.
- Enters a continuous bootloop.
- Cannot enter any recovery mode (TWRP, etc.).
- The only recovery method is to flash the stock firmware via bootloader/EDL mode.
Expected Results
The device should boot into the operating system normally, as it does with version 0.13.5.
Additional Context
- The crash occurs at a very early stage of kernel initialization.
- The issue is 100% reproducible. Reverting to version 0.13.5 immediately resolves the problem.
- No other Magisk modules or configuration changes were made between testing 0.13.5 and 0.13.6, confirming this is a regression in the module itself.
- The incident occurred several days ago, and any potential kernel crash logs have likely been overwritten by the system.
- The ColorOS 15 ROM is an unofficial port, not the stock ROM for Redmi K60.
Note: This issue report was written with AI assistance. There may be inaccuracies in technical language translation, and as a new contributor, I may have omitted some necessary details. I'm happy to provide any additional information or perform requested tests to help resolve this problem. Please let me know.