M1 Mac Kernel Crash

tim_hilde

Recently, I have regular kernel crashes on my MB Air M1 that relate to Zotero.

Here is the error report:

panic(cpu 6 caller 0xfffffe001155fd5c): Kernel data abort. at pc 0xfffffe0010d2f0b4, lr 0x4ca77e0010dd003c (saved state: 0xfffffe8f1410b400)
x0: 0x0000000000000008 x1: 0x0000000000004000 x2: 0x000000003006816f x3: 0x0000000000000000
x4: 0x0000000000000000 x5: 0xfffffe8f1410b89c x6: 0xfffffe8f1410b8a8 x7: 0xfffffe8f1410b8a0
x8: 0x0000000000000010 x9: 0x00000000ffdfffff x10: 0x00000000ffcfffff x11: 0x0000000000000000
x12: 0x0000000000420000 x13: 0x00000000004a0000 x14: 0x00000000ffdfffff x15: 0x00000000ffffffff
x16: 0x00000200316501d4 x17: 0x000000000003466d x18: 0x0000000000000000 x19: 0x0000000000000008
x20: 0xfffffe14cce25200 x21: 0xfffffe14cce25200 x22: 0x0000000000004000 x23: 0xfffffe14cccfa5c0
x24: 0xfffffe001894a380 x25: 0x0000000000000000 x26: 0x0000000000001000 x27: 0xfffffe8f1410b898
x28: 0xfffffe8f1410b830 fp: 0xfffffe8f1410b7a0 lr: 0x4ca77e0010dd003c sp: 0xfffffe8f1410b750
pc: 0xfffffe0010d2f0b4 cpsr: 0x60401208 esr: 0x96000005 far: 0x0000000000000010

Debugger message: panic
Memory ID: 0x6
OS release type: User
OS version: 22D49
Kernel version: Darwin Kernel Version 22.3.0: Thu Jan 5 20:49:43 PST 2023; root:xnu-8792.81.2~2/RELEASE_ARM64_T8103
Fileset Kernelcache UUID: 177F4EF1CE4EF944F62B51622AC037FD
Kernel UUID: 33DF0F44-C903-3ED1-9441-739C180D999A
Boot session UUID: 87C52D0D-C50D-46C1-BDF9-FBE69F7E2C7A
iBoot version: iBoot-8419.80.7
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x0000000008978000
KernelCache base: 0xfffffe000f97c000
Kernel slide: 0x0000000009bc8000
Kernel text base: 0xfffffe0010bcc000
Kernel text exec slide: 0x0000000009cb0000
Kernel text exec base: 0xfffffe0010cb4000
mach_absolute_time: 0xf0e7dabc2d
Epoch Time: sec usec
Boot : 0x63f5f2ba 0x0009fa29
Sleep : 0x63f86c4a 0x0008ee61
Wake : 0x63f86cfe 0x000f1e17
Calendar: 0x63f88fa0 0x00010986

Zone info:
Zone map: 0xfffffe10004d0000 - 0xfffffe30004d0000
. VM : 0xfffffe10004d0000 - 0xfffffe14cd19c000
. RO : 0xfffffe14cd19c000 - 0xfffffe1666b34000
. GEN0 : 0xfffffe1666b34000 - 0xfffffe1b33800000
. GEN1 : 0xfffffe1b33800000 - 0xfffffe20004cc000
. GEN2 : 0xfffffe20004cc000 - 0xfffffe24cd198000
. GEN3 : 0xfffffe24cd198000 - 0xfffffe2999e64000
. DATA : 0xfffffe2999e64000 - 0xfffffe30004d0000
Metadata: 0xfffffe3ee964c000 - 0xfffffe3ef164c000
Bitmaps : 0xfffffe3ef164c000 - 0xfffffe3ef4248000

CORE 0 recently retired instr at 0xfffffe0010e6f7c0
CORE 1 recently retired instr at 0xfffffe0010e6f7c0
CORE 2 recently retired instr at 0xfffffe0010e6f7c0
CORE 3 recently retired instr at 0xfffffe0010e6f7c0
CORE 4 recently retired instr at 0xfffffe0010e6f7c0
CORE 5 recently retired instr at 0xfffffe0010e6f7c0
CORE 6 recently retired instr at 0xfffffe0010e6e0c0
CORE 7 recently retired instr at 0xfffffe0010e6f7c0
TPIDRx_ELy = {1: 0xfffffe24cf849030 0: 0x0000000000000006 0ro: 0x000000020026d3a0 }
CORE 0 PVH locks held: None
CORE 1 PVH locks held: None
CORE 2 PVH locks held: None
CORE 3 PVH locks held: None
CORE 4 PVH locks held: None
CORE 5 PVH locks held: None
CORE 6 PVH locks held: None
CORE 7 PVH locks held: None
CORE 0: PC=0xfffffe0010d4f8cc, LR=0xfffffe0010d4f8cc, FP=0xfffffe8f1437bf00
CORE 1: PC=0xfffffe0010d4f8cc, LR=0xfffffe0010d4f8cc, FP=0xfffffe8f14303f00
CORE 2: PC=0xfffffe0010d4f8cc, LR=0xfffffe0010d4f8cc, FP=0xfffffe8f14b5bf00
CORE 3: PC=0xfffffe0010d4f8cc, LR=0xfffffe0010d4f8cc, FP=0xfffffe8f151bbf00
CORE 4: PC=0xfffffe0010d4f8cc, LR=0xfffffe0010d4f8cc, FP=0xfffffe8f140c3f00
CORE 5: PC=0xfffffe001120e394, LR=0xfffffe0010cc4e98, FP=0x0000000000000000
CORE 6 is the one that panicked. Check the full backtrace for details.
CORE 7: PC=0xfffffe0010d4f8cc, LR=0xfffffe0010d4f8cc, FP=0xfffffe8f13ddbf00
Compressor Info: 24% of compressed pages limit (OK) and 10% of segments limit (OK) with 3 swapfiles and OK swap space
Panicked task 0xfffffe1b35d52df0: 307672 pages, 72 threads: pid 7857: zotero
Panicked thread: 0xfffffe24cf849030, backtrace: 0xfffffe8f1410ab10, tid: 364366
lr: 0xfffffe0010d12810 fp: 0xfffffe8f1410ab80
lr: 0xfffffe0010d125b8 fp: 0xfffffe8f1410ac00
lr: 0xfffffe0010e7624c fp: 0xfffffe8f1410ac20
lr: 0xfffffe0010e67cb4 fp: 0xfffffe8f1410ac90
lr: 0xfffffe0010e655b8 fp: 0xfffffe8f1410ad50
lr: 0xfffffe0010cbb7f8 fp: 0xfffffe8f1410ad60
lr: 0xfffffe0010d11f44 fp: 0xfffffe8f1410b110
lr: 0xfffffe0011556968 fp: 0xfffffe8f1410b130
lr: 0xfffffe001155fd5c fp: 0xfffffe8f1410b2b0
lr: 0xfffffe0010e67b28 fp: 0xfffffe8f1410b320
lr: 0xfffffe0010e65910 fp: 0xfffffe8f1410b3e0
lr: 0xfffffe0010cbb7f8 fp: 0xfffffe8f1410b3f0
lr: 0xfffffe0010dd003c fp: 0xfffffe8f1410b7a0
lr: 0xfffffe0010dd003c fp: 0xfffffe8f1410b920
lr: 0xfffffe0010de6d48 fp: 0xfffffe8f1410ba70
lr: 0xfffffe0010e2e0f4 fp: 0xfffffe8f1410bac0
lr: 0xfffffe0010d9fa7c fp: 0xfffffe8f1410baf0
lr: 0xfffffe0010d18f6c fp: 0xfffffe8f1410bb90
lr: 0xfffffe0010ce8c08 fp: 0xfffffe8f1410bbf0
lr: 0xfffffe0010d03db8 fp: 0xfffffe8f1410bc90
lr: 0xfffffe0010d04258 fp: 0xfffffe8f1410bd80
lr: 0xfffffe0010e5b510 fp: 0xfffffe8f1410be50
lr: 0xfffffe0010e65964 fp: 0xfffffe8f1410bf10
lr: 0xfffffe0010cbb7f8 fp: 0xfffffe8f1410bf20

last started kext at 784796746: com.apple.filesystems.autofs 3.0 (addr 0xfffffe0010150360, size 5904)
loaded kexts:
[...]

dstillman

Start by updating to 13.2.1. A kernel panic is by definition an OS problem or a hardware problem, not a problem in a regular app.

TFly3

I came here to say that I too am experiencing kernel panics on my M1 Pro MBP that are associated with Zotero. Here are the summary details of one of the most recent events from EtreCheck:

panic(cpu 2 caller 0xfffffe0020922bec): Kernel data abort. at pc 0xfffffe00201b89cc, lr 0x598c7e00202443a8 (saved state: 0xfffffe8e194db440)
Panicked task 0xfffffe1ffca90bb8: 414946 pages, 75 threads: pid 68506: zotero

@dstillman, I understand your argument that kernel panics are usually caused by a "deeper" problem than software like Zotero, but wouldn't you say that multiple users experiencing the same issue with strong correlation to use of Zotero deserves more investigation?

dstillman

@TFly3: There's no "usually" about it — an app like Zotero literally cannot cause or fix a kernel panic. It is by definition a problem in the OS/hardware that only Apple can fix.

TFly3

Understood - do we have any idea as to why this flaw within macOS seems to be aggravated or precipitated more reliably while using Zotero?

dstillman

An app can interact with some part of the system that would cause a kernel panic, but the actual bug that needs to be fixed is still in the OS or hardware.

As I say above, if you're not running the latest version of macOS, upgrading would be your first step.

TFly3

Ok, I appreciate your prompt replies. Also, I should have specified: Ventura 13.3.1, Zotero 6.0.23. I'd been avoiding using Zotero (which is heartbreaking), but I'll start again and cross my fingers that I can't replicate the problem. If it happens again, I'll share any logs in case they're helpful.

TFly3

Hey @dstillman, as promised, letting you know if it happened again. Was using PDF reader in zotero and boom, pink screen and a restart. EtreCheck says "panic(cpu 3 caller 0xfffffe002a3febec): Kernel data abort. at pc 0xfffffe0029c949cc, lr 0xa5af7e0029d203a8 (saved state: 0xfffffe53bb477440)
Panicked task 0xfffffe24cc1734f8: 492439 pages, 74 threads: pid 48342: zotero"
Is there anyone who'd be interested in the full panic report to try and fix this issue?

dstillman

As I say, a kernel panic is a problem with the OS or hardware. It's not something we or any app developer can fix.

TFly3

There are multiple people reporting kernel panics that are associated with using zotero on Apple Silicon macbooks. I agree with you that correlation isn't causation, just saying there appears to be quite a correlation here. Again, EtreCheck is pointing at a zotero task specifically. I understand that the ultimate fault is with MacOS, just wondering if anything is being done on zotero's end to avoid aggravating that fault? None of my other apps precipitate this fault in MacOS, and zotero does it reliably...

TFly3

Would also appreciate any guidance, for example would uninstalling add-ins, or uninstalling and re-installing zotero offer any benefit?

dstillman

The point is just that we literally can't fix it. Only Apple can fix it.

Also, to be clear, we've only had about four reports of this among the entire Zotero userbase, so it's not a general problem that all Mac users are seeing. And since we can't reproduce it ourselves, we can't even make changes to Zotero to avoid triggering it.

Deleting Zotero from Applications and reinstalling probably won't help, but it's not inconceivable that it could fix it if this is due to a bug in Rosetta.

Beyond that, generally if you're seeing this you would just need to report it to Apple, but the Zotero 7 beta will be out very soon, so I'd suggest just waiting for that and seeing if that happens to avoid triggering the macOS bug here. Zotero 7 will have a native Apple Silicon version and also use different graphics technologies, so it will avoid huge swathes of macOS code that Zotero 6 uses.

TFly3

@dstillman Any estimate on when the Zotero 7 beta will be out? Happened again:

panic(cpu 3 caller 0xfffffe001156abec): Kernel data abort. at pc 0xfffffe0010e009cc, lr 0xa7b0fe0010e8c3a8 (saved state: 0xfffffe79d8763440)
Panicked task 0xfffffe2998aa82b8: 371793 pages, 80 threads: pid 28407: zotero

andrewbjaeger

I'm also very interested in a beta 7 estimate...