I've been running OpenZFS for years, and installed the development version for Big Sur in December - updating it as newer pkgs became available. A recurrent problem with my -otherwise stable- OSX86 build has been this kernel panic upon wake from sleep, after about 13-14 days of uptime:
- Code: Select all
panic(cpu 4 caller 0xffffff80161ee1e6): Kernel trap at 0xffffff7fb834f495, type 13=general protection, registers:
CR0: 0x0000000080010033, CR2: 0x000000010d2580f0, CR3: 0x0000000f0ce6121a, CR4: 0x00000000003626e0
RAX: 0x0100010001000100, RBX: 0x0000000000000002, RCX: 0x0000000200000000, RDX: 0x0000000000000002
RSP: 0xffffffc1f041b1d0, RBP: 0xffffffc1f041b430, RSI: 0x0000000000000000, RDI: 0x0000000000000001
R8: 0x0000000000000010, R9: 0x000000000000002c, R10: 0x0000000000000000, R11: 0x0000000000000000
R12: 0xffffffc1f041b4c0, R13: 0x0000000000000001, R14: 0x0000000000000001, R15: 0x0000000000000194
RFL: 0x0000000000010246, RIP: 0xffffff7fb834f495, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x000000010d2580f0, Error code: 0x0000000000000000, Fault CPU: 0x4, PL: 0, VF: 0
Backtrace (CPU 4), Frame : Return Address
0xffffff8015f581e0 : 0xffffff80160bab4d mach_kernel : _handle_debugger_trap + 0x3dd
0xffffff8015f58230 : 0xffffff80161fd7e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffff8015f58270 : 0xffffff80161ede1a mach_kernel : _kernel_trap + 0x55a
0xffffff8015f582c0 : 0xffffff801605fa2f mach_kernel : _return_from_trap + 0xff
0xffffff8015f582e0 : 0xffffff80160ba3ed mach_kernel : _DebuggerTrapWithState + 0xad
0xffffff8015f58400 : 0xffffff80160ba6d8 mach_kernel : _panic_trap_to_debugger + 0x268
0xffffff8015f58470 : 0xffffff80168bef9a mach_kernel : _panic + 0x54
0xffffff8015f584e0 : 0xffffff80161ee1e6 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffff8015f58660 : 0xffffff80161edecd mach_kernel : _kernel_trap + 0x60d
0xffffff8015f586b0 : 0xffffff801605fa2f mach_kernel : _return_from_trap + 0xff
0xffffff8015f586d0 : 0xffffff7fb834f495 net.lundman.zfs : _collect_a_seq + 0x375
0xffffffc1f041b430 : 0x100010001000100
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0x100010001000100
Kernel Extensions in backtrace:
net.lundman.zfs(2.0)[ECE8A16E-4291-3907-B14F-C8A732F68C6E]@0xffffff7fb820a000->0xffffff7fb8532fff
dependency: com.apple.iokit.IOStorageFamily(2.1)[B5300908-BF34-3D47-8776-FB154A6DEE4C]@0xffffff8018b3f000->0xffffff8018b50fff
Process name corresponding to current thread: ChronoSync
Boot args: keepsyms=1 darkwake=3 shikigva=80 debug=0x100 igfxonln=1 igfxfw=2 forceRenderStandby=0 alcid=11
Mac OS version:
20D91
Kernel version:
Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64
Kernel UUID: C86236B2-4976-3542-80CA-74A6B8B4BA03
KernelCache slide: 0x0000000015e00000
KernelCache base: 0xffffff8016000000
Kernel slide: 0x0000000015e10000
Kernel text base: 0xffffff8016010000
__HIB text base: 0xffffff8015f00000
System model name: iMac19,1 (Mac-AA95B1DDAB278B95)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0
System uptime in nanoseconds: 528898779578654
Last Sleep: absolute base_tsc base_nano
Uptime : 0x0001e107d7e10456
Sleep : 0x0001dfef827f92eb 0x000000012b30d3ef 0x0001df54cc4e5292
Wake : 0x0001dfef9cabe137 0x000000012b2e8c8f 0x0001dfef8bcc6890
(ChronoSync launches a scheduled, daily 2am script to backup a folder within a 2*SSD zpool, and immediately crashes the system; all prior runs had been uneventful)
Thought you mind find the info useful. Once again, many thanks!
Xen