I am trying to debug a kernel panic in our kext. I can attach to the target Mac over ethernet if I: cause an NMI using add an IOPanic call to my kext and cause it to be executed use Dtrace to invoke a panic However if I reproduce the kernel panic which I am investigating, the Mac just restarts. How can I make the Mac wait for me to attach with lldb rather than restarting? My target configuration is: Mac is 2021 M1 Pro 14" MacBook Pro macOS 14.2 (23C64) Network: Apple Thunderbolt 3 <-> Thunderbolt 3 adapter + Apple Thunderbolt 2 to ethernet adapters Boot-args = "debug=0x44 wdt=-1 kdp_match_name=en8" (I have also tried debug=0x104C0C)

The KDK file for the latest beta of macOS 11.3 does not actually contain a KDK. The file is: "Kernel_Debug_Kit_11.3_Build_20E5224a.dmg" which contains a volume called: "/Volumes/InstallAssistantMAS". The installer on this volume does not actually contain a KDK. I'm just posting here in the hopes that someone at Apple will notice and repost the correct KDK file. Thanks - Tim

We use a custom Mac app and Mac minis in our factories to initialize disks and copy files to them. It would make this process easier, if the person in manufacturing did not have to dismiss the dialog which says "The disk you inserted was not readable by this computer" for each disk. Is there a Finder or system preference I can set to prevent this dialog from being displayed? I know that I can grab the disk using DADiskPeek but one of our tools is a Python script so calling DADiskPeek is not an option. Thanks in advance for your help. Tim

One of the main reasons customers contact our support center is because the wrong version of the driver is loading. This is a direct result of Secure Boot being enabled. How can I detect if Secure Boot is enabled so we can warn users that they will encounter aberrant behavior until they disable it?

I would like to know if my kext is responsible for saving / restoring vector registers if I use SIMD instructions in my Kext or will the scheduler do this for me. The SIMD instructions would be running on a pool of dedicated threads which are created at driver load time. (The threads obviously block when there is no work to be done.) Does this behavior differ between the x86_64 and arm64e kernels?

Where can I download the source code for the Network Benchmark Utility used in the session "Port your Mac app to Apple Silicon?" I want to look at the sources for the TLSPlugin it uses.

Does anyone have some pointers on how to collect a kernel coredump using macOS 10.15 for both the debug Mac and the Mac running the kernel coredump daemon (kdumpd)?I can collect a kernel coredump using Mac OS 10.11 for the kernel coredump daemon from a kernel panic on macOS 10.15 but have been unable to run the daemon on macOS 10.15.One of the setup steps for setting up the daemon is to create a directory at /PanicDumps. This is obviously not possible unless you temporarily boot using another startup volume or boot into Recovery Mode. Even if you do manage to create a directory at /PanicDumps, it is part of a read only file system so the kdumpd daemon will not be able to write to it.If I instead create the directory on the " - Data" volume of the volume group, it does not appear when I boot back into 10.15.Is there a new location for the PanicDumps directory?Thanks so much for your help,Tim StandingOther World Computing, Inc.