Post

Replies

Boosts

Views

Activity

Reply to Instructions for debugging recent macos kernel versions?
Hi everyone. Thank you so much for your support on this. I had to take a bit of a break from the subject to see if I could work on it from a clean slate. I was able to get an IPS with the Mac going into recovery mode with PanicMedic as the reason. @elowe, I'll post this as a bug, but I assume that it might be redundant if someone already reported it. I would also suggest adding some additional debug flag combinations to the README, based on this https://developer.apple.com/library/archive/technotes/tn2004/tn2118.html#SECDEBUGFLAGS which I took from the blog post in my last reply. There's a table with useful flag combinations, which I think could be helpful for further troubleshooting. Thanks again! :)
Topic: App & System Services SubTopic: Core OS Tags:
1w
Reply to Instructions for debugging recent macos kernel versions?
Hi to both, thanks for your responses. I've been trying multiple permutations to see what would work. I still haven't managed much that I could consider helpful. With the commands to create the .kc files, I made two from the release kernel with suffixes for development and debug, and the same for the development kernel. In the end I had files for release.kc.development, release.kc.debug, dev.kc.development, dev.kc.debug. Both release versions booted no prob, the dev ones showed the same issue, where the mac sound gets played, then it connects to the network (either DCHP or a manually set one), but it doesn't take any input from external devices and displays nothing. From there it seems to reboot itself a bunch of time, as the network connection stops working multiple times until it eventually "breaks" and forces me into a window with "The version of macOS on the selected disk needs to be reinstalled" and the option to go to recovery. In addition to what Kevin noted in the reply, what is the output of uname -v on that host and what is the KDK build that you downloaded for it? Also, what is the name of the kernel binary file (the one from the downloaded KDK, which contains the model name) you used to generate the kext collection? uname -v Darwin Kernel Version 27.0.0: Tue Aug 11 21:06:15 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8152 sw_vers ProductName: macOS ProductVersion: 27.0.1 BuildVersion: 26A434 I'm using KDK_27.0.1_26A434.kdk, which matches the product and build versions. Ever since you guys' responses I've been trying to generate reports to see if I could report a bug with some substance. Debugging hasn't really worked as well as I hoped, but since I don't have a working system I can try, I don't know if maybe I'm missing something. Basically I didn't manage to do a network debug, neither connecting two computers directly via ethernet and setting static addresses nor connecting them to a switch with DHCP worked. I thought it might be the fact that I couldn't use USB ethernet adapters, but then I borrowed another mac mini again to try it out with both ethernet ports and nothing worked anyways. I looked into some older articles online about debugging where I could use the power button to trigger an NMI to dump the file directly into the device, without needing a second one. That also didn't work. I think I was looking for the files in the "wrong" directory (/var/tmp/kernel_panics). I was later able to find some stuff under /Library/Logs/DiagnosticReports. At some point after the message about macOS being broken, I could open recovery and the terminal to see an .ips file. After rebooting with the high security mode in order to boot normally, the file wasn't there anymore. This is one of the refs I used the most and that seemed the most complete but nothing from there really worked: https://karol-mazurek.medium.com/kernel-debugging-setup-on-macos-07dd8c86cdb6 I replicated the steps I took to recreate and copy the .ips file to another place where it would persist, but I couldn't get it to appear anymore. Otherwise I was able to see some .shutdownStall files. I made the latest one readable, but based on the "Posting a crash report" post don't know if it's a relevant file since it's neither a crash nor an ips. It's got stuff about pci errors and drivers. Any advice on how to proceed would be appreciated. I'm kind of at my wit's end. Many thanks!
Topic: App & System Services SubTopic: Core OS Tags:
2w
Reply to Instructions for debugging recent macos kernel versions?
Hi hi, I'm having issues with this as well. I found this forum post through @jaikiran's blog post, which has been of massive help. I just tried this method on a mac mini M2 Pro (macOS 15.7.3 build 24G419 and T6020) and it worked absolutely fine on the first try. When I tried it on a new mac mini M6 (27.0.1 build 26A434, T8152), macOS can't boot and at some point it just panics into recovery mode. Did something change within the last year that I have to look out for? Many thanks in advance and best, Andres
Topic: App & System Services SubTopic: Core OS Tags:
3w
Reply to Instructions for debugging recent macos kernel versions?
Hi everyone. Thank you so much for your support on this. I had to take a bit of a break from the subject to see if I could work on it from a clean slate. I was able to get an IPS with the Mac going into recovery mode with PanicMedic as the reason. @elowe, I'll post this as a bug, but I assume that it might be redundant if someone already reported it. I would also suggest adding some additional debug flag combinations to the README, based on this https://developer.apple.com/library/archive/technotes/tn2004/tn2118.html#SECDEBUGFLAGS which I took from the blog post in my last reply. There's a table with useful flag combinations, which I think could be helpful for further troubleshooting. Thanks again! :)
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
1w
Reply to Instructions for debugging recent macos kernel versions?
Hi to both, thanks for your responses. I've been trying multiple permutations to see what would work. I still haven't managed much that I could consider helpful. With the commands to create the .kc files, I made two from the release kernel with suffixes for development and debug, and the same for the development kernel. In the end I had files for release.kc.development, release.kc.debug, dev.kc.development, dev.kc.debug. Both release versions booted no prob, the dev ones showed the same issue, where the mac sound gets played, then it connects to the network (either DCHP or a manually set one), but it doesn't take any input from external devices and displays nothing. From there it seems to reboot itself a bunch of time, as the network connection stops working multiple times until it eventually "breaks" and forces me into a window with "The version of macOS on the selected disk needs to be reinstalled" and the option to go to recovery. In addition to what Kevin noted in the reply, what is the output of uname -v on that host and what is the KDK build that you downloaded for it? Also, what is the name of the kernel binary file (the one from the downloaded KDK, which contains the model name) you used to generate the kext collection? uname -v Darwin Kernel Version 27.0.0: Tue Aug 11 21:06:15 PDT 2026; root:xnu-13432.1.9~1/RELEASE_ARM64_T8152 sw_vers ProductName: macOS ProductVersion: 27.0.1 BuildVersion: 26A434 I'm using KDK_27.0.1_26A434.kdk, which matches the product and build versions. Ever since you guys' responses I've been trying to generate reports to see if I could report a bug with some substance. Debugging hasn't really worked as well as I hoped, but since I don't have a working system I can try, I don't know if maybe I'm missing something. Basically I didn't manage to do a network debug, neither connecting two computers directly via ethernet and setting static addresses nor connecting them to a switch with DHCP worked. I thought it might be the fact that I couldn't use USB ethernet adapters, but then I borrowed another mac mini again to try it out with both ethernet ports and nothing worked anyways. I looked into some older articles online about debugging where I could use the power button to trigger an NMI to dump the file directly into the device, without needing a second one. That also didn't work. I think I was looking for the files in the "wrong" directory (/var/tmp/kernel_panics). I was later able to find some stuff under /Library/Logs/DiagnosticReports. At some point after the message about macOS being broken, I could open recovery and the terminal to see an .ips file. After rebooting with the high security mode in order to boot normally, the file wasn't there anymore. This is one of the refs I used the most and that seemed the most complete but nothing from there really worked: https://karol-mazurek.medium.com/kernel-debugging-setup-on-macos-07dd8c86cdb6 I replicated the steps I took to recreate and copy the .ips file to another place where it would persist, but I couldn't get it to appear anymore. Otherwise I was able to see some .shutdownStall files. I made the latest one readable, but based on the "Posting a crash report" post don't know if it's a relevant file since it's neither a crash nor an ips. It's got stuff about pci errors and drivers. Any advice on how to proceed would be appreciated. I'm kind of at my wit's end. Many thanks!
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
2w
Reply to Instructions for debugging recent macos kernel versions?
Hi hi, I'm having issues with this as well. I found this forum post through @jaikiran's blog post, which has been of massive help. I just tried this method on a mac mini M2 Pro (macOS 15.7.3 build 24G419 and T6020) and it worked absolutely fine on the first try. When I tried it on a new mac mini M6 (27.0.1 build 26A434, T8152), macOS can't boot and at some point it just panics into recovery mode. Did something change within the last year that I have to look out for? Many thanks in advance and best, Andres
Topic: App & System Services SubTopic: Core OS Tags:
Replies
Boosts
Views
Activity
3w