A new set of symbol files must be generated each time a kernel extension is loaded because the load addresses of the KEXT or its dependencies are likely to be different each time. The Design and Implementation of the 4.4BSD Operating System, McKusick et al., Addison-Wesley, 1996. After an hour or so, the internet crashed again, and his PC hard-froze up again, and dished out another kernel panic report. To understand why, recall that the backtrace is a listing of the return addresses saved prior to executing a function call. Programming Environments Manual For 32-Bit Implementations of the PowerPC Architecture, Freescale Semiconductor document MPCFPE32B, revision 3, 9/2005. In this case, you can attach to the panicked machine with GDB and use the paniclog kernel debugging macro to retrieve the log. The format of the error code for a page fault (exception vector 14) is different from that for other exceptions. Kernel Debug Kits contain symbol-rich versions of the kernel and many I/O Kit families. However, it looks like the issue has been pushed to the source but has not been complied into a kext yet. With the same configuration Catalina works perfectly. Dump of assembler code for function panic: Dump of assembler code for function kernel_trap: Dump of assembler code for function trap_from_kernel: Dump of assembler code for function _ZN32com_apple_dts_driver_PanicDriver5startEP9IOService: Dump of assembler code for function _ZN9IOService14startCandidateEPS_: Dump of assembler code for function _ZN9IOService15probeCandidatesEP12OSOrderedSet: Dump of assembler code for function _ZN9IOService14doServiceMatchEm: Dump of assembler code for function _ZN15_IOConfigThread4mainEPS_: Dump of assembler code for function call_continuation: Then locate the function containing the instruction pointed to by the instruction pointer. Listing 8 Disassembling from the instruction pointer. For more details on remote kernel debugging, please refer to Kernel Extension Programming Topics.
I initially thought the issue was related to a Dell DisplayLink docking station I had connected to, but I have uninstalled the driver and I have also experienced crashes without any peripherals attached. This diagnosis is consistent with the earlier result from disassembling the single instruction located at the instruction pointer.
because I can't seem to find any useable step by step guides online) or the EFI drivers and KEXTs are just set up the wrong way. This might have changed, though, in Catalina: Console there no longer lists log folders as such, but lists them by type. Furthermore: if I disconnect TS3+ from MacBook Pro when TS3+ USB bus going down, I'd get Kernel Panic after 10 seconds.
You can find crash and kernel panic logs Mac OS creates for the entire system (not just the current logged in user) in the following location: /Library/Logs/DiagnosticReports. Fortunately they sent you the panic log like the ones shown earlier. Common error code values for exception vector 14 are 0x00000000 indicating a read from a non-present page, and 0x00000002 indicating a write to a non-present page. Contents of registers EFLAGS, EIP, CS, and DS from the exception handler.