Daniel M. Zimmerman

Another one: ``` panic(cpu 2 caller 0xfffffe00159a9ab0): Kernel data abort. at pc 0xfffffe0016d4ef54, lr 0xfffffe0016d4ef3c (saved state: 0xfffffe686beef510) x0: 0x0000000000000000 x1: 0x0000000000300000 x2: 0x0000000000000000 x3: 0xfffffe1000542ca0 x4: 0x0000000000000000 x5: 0x0000000000300000...

Another one (different process panicking this time): ``` panic(cpu 1 caller 0xfffffe00299a9ab0): Kernel data abort. at pc 0xfffffe00292ad71c, lr 0x6293fe00292ad6c0 (saved state: 0xfffffe7fde02f080) x0: 0x0000000000000000 x1: 0xfffffe166d5daae0 x2: 0xfffffe7fdbc84000 x3:...

The new version doesn't help.

Awesome! I will try that right now and see what happens; do let me know if I can otherwise help with testing in any way. Now if we can just...

I can use `sysctl` to set the tunable manually, but apparently `/usr/local/zfs/bin/zsysctl` is _not_ running automatically on reboot, because on reboot the tunable is back to 0 (and the machine...

Unfortunately, I have to report that it still panics for me, even with a 16GiB arc_max. It takes a lot longer, though, and I was pushing it pretty hard. ```...

> zconfigd should be running > > ``` > /usr/local/zfs/sbin/zsysctl -f /etc/zfs/zsysctl.conf > ``` Well, I think I found the problem: - first, `zsysctl` is in `/usr/local/zfs/bin` on my machine,...

@rottegift: I think you may have misread my comment (or I don't understand what you're saying in response). My `zsysctl` is in `/usr/local/zfs/bin`, not `/usr/local/zfs/sbin` (as you expected), and definitely...

Fair enough. My `zsysctl` dates from September 8 (in the most recent package lundman built), and is definitely a universal binary. And I did verify that the crashes occurred with...

I'm having a similar problem on with OpenZFS 2.1 and macOS 12.5 on my M1 Ultra; I did find a bunch of sandbox messages, and gave both Photos and `photoanalysisd`...