Kernel panic on M1 MacBook Pro after upgrade to Sequoia 15.4

I'm having kernel panics on M1 MacBook Pro afer upgrade to Sequoia 15.4 when connected to VPN with openfortivpn. Do you happen to know how to troubleshoot or fix this? Details below, thanks 👋


Crash report looks like that:

panic(cpu 1 caller 0xfffffe0019b6e2a8): Break 0x5519 instruction exception from kernel. Panic (by design) at pc 0xfffffe0019851b80, lr 0xfffffe001c2d34c8 (saved state: 0xfffffea83561bad0)
	  x0:  0xfffffe1e5108a600 x1:  0xfffffe241da337f8  x2:  0x0000000000000000  x3:  0x000000000000002d
	  x4:  0x00000015e437be96 x5:  0x000000000003a980  x6:  0x0000000000000000  x7:  0x00000015e437bb2e
	  x8:  0xfffffe1e5108a4e0 x9:  0xfffffe1e5108a600  x10: 0xfffffea83561be61  x11: 0x00000015e43b6816
	  x12: 0x00000015e43b6816 x13: 0x00000015e43b6816  x14: 0xfffffea83561badc  x15: 0x0000000000000001
	  x16: 0x4f8bfe0019426cd8 x17: 0x00000000000073d8  x18: 0x0000000000000000  x19: 0x0000000000000001
	  x20: 0xfffffe241d510000 x21: 0xfffffe241d5100e8  x22: 0xfffffe2528800880  x23: 0xfffffe0018567480
	  x24: 0xfffffe1e5108a400 x25: 0xfffffe001cf64000  x26: 0xfffffe001cf64000  x27: 0xfffffe001cf64000
	  x28: 0xfffffe001cf64e40 fp:  0xfffffea83561bec0  lr:  0xfffffe001c2d34c8  sp:  0xfffffea83561be20
	  pc:  0xfffffe0019851b80 cpsr: 0x00400208         esr: 0x00000000f2005519  far: 0x00000005263a0000

Debugger message: panic
Memory ID: 0x1
OS release type: User
OS version: 24E248
Kernel version: Darwin Kernel Version 24.4.0: Wed Mar 19 21:16:34 PDT 2025; root:xnu-11417.101.15~1/RELEASE_ARM64_T6000
Fileset Kernelcache UUID: 64910CF20FBC3B619F5B9FEDE3E907C5
Kernel UUID: 0DBF4FC4-B7A0-303C-9143-63308FC1EA62
Boot session UUID: DE88A578-70C4-4D72-AEB4-FF036F4F6895
iBoot version: iBoot-11881.101.1
iBoot Stage 2 version: iBoot-11881.101.1
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x0000000010ac8000
KernelCache base:  0xfffffe0017acc000
Kernel slide:      0x0000000010ad0000
Kernel text base:  0xfffffe0017ad4000
Kernel text exec slide: 0x0000000012260000
Kernel text exec base:  0xfffffe0019264000
mach_absolute_time: 0x15e44150c1
Epoch Time:        sec       usec
  Boot    : 0x67f66ad2 0x0006e9a9
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x67f67a19 0x00098846

Zone info:
  Zone map: 0xfffffe1120000000 - 0xfffffe3720000000
  . VM    : 0xfffffe1120000000 - 0xfffffe16ec000000
  . RO    : 0xfffffe16ec000000 - 0xfffffe1986000000
  . GEN0  : 0xfffffe1986000000 - 0xfffffe1f52000000
  . GEN1  : 0xfffffe1f52000000 - 0xfffffe251e000000
  . GEN2  : 0xfffffe251e000000 - 0xfffffe2aea000000
  . GEN3  : 0xfffffe2aea000000 - 0xfffffe30b6000000
  . DATA  : 0xfffffe30b6000000 - 0xfffffe3720000000
  Metadata: 0xfffffe4eb0010000 - 0xfffffe4eb9810000
  Bitmaps : 0xfffffe4eb9810000 - 0xfffffe4ebc5c0000
  Extra   : 0 - 0

TPIDRx_ELy = {1: 0xfffffe241da337f8  0: 0x0000000000000001  0ro: 0x0000000000000000 }
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 8 PVH locks held: None
CORE 9 PVH locks held: None
CORE 0: PC=0x00000001a00e760c, LR=0x00000001a00e760c, FP=0x000000017a8eaea0
CORE 1 is the one that panicked. Check the full backtrace for details.
CORE 2: PC=0xfffffe00194198c8, LR=0xfffffe001942842c, FP=0xfffffea8360cbe40
CORE 3: PC=0xfffffe0019300f28, LR=0xfffffe0019300f28, FP=0xfffffea836023ed0
CORE 4: PC=0xfffffe00194198c8, LR=0xfffffe001942842c, FP=0xfffffea836017e40
CORE 5: PC=0xfffffe0019300f28, LR=0xfffffe0019300f28, FP=0xfffffea8360efed0
CORE 6: PC=0xfffffe0019300f28, LR=0xfffffe0019300f28, FP=0xfffffea8361bfed0
CORE 7: PC=0xfffffe0019300f28, LR=0xfffffe0019300f28, FP=0xfffffea835af7ed0
CORE 8: PC=0xfffffe0019300f28, LR=0xfffffe0019300f28, FP=0xfffffea834007ed0
CORE 9: PC=0xfffffe0019300f28, LR=0xfffffe0019300f28, FP=0xfffffea835b27ed0
Compressor Info: 20% of compressed pages limit (OK) and 22% of segments limit (OK) with 3 swapfiles and OK swap space
Panicked task 0xfffffe1e51fc1618: 0 pages, 609 threads: pid 0: kernel_task
Panicked thread: 0xfffffe241da337f8, backtrace: 0xfffffea83561b220, tid: 1706
		  lr: 0xfffffe00192c32c8  fp: 0xfffffea83561b2b0
		  lr: 0xfffffe00194245fc  fp: 0xfffffea83561b320
		  lr: 0xfffffe0019422858  fp: 0xfffffea83561b3e0
		  lr: 0xfffffe001926bb98  fp: 0xfffffea83561b3f0
		  lr: 0xfffffe00192c2bac  fp: 0xfffffea83561b7c0
		  lr: 0xfffffe0019b62cd4  fp: 0xfffffea83561b7e0
		  lr: 0xfffffe0019b6e2a8  fp: 0xfffffea83561b9f0
		  lr: 0xfffffe0019422fc0  fp: 0xfffffea83561bab0
		  lr: 0xfffffe001926bb98  fp: 0xfffffea83561bac0
		  lr: 0xfffffe001c2d34c8  fp: 0xfffffea83561bec0
		  lr: 0xfffffe001c2d3160  fp: 0xfffffea83561bf20
		  lr: 0xfffffe0019274f04  fp: 0x0000000000000000
      Kernel Extensions in backtrace:
         com.apple.nke.ppp(1.9)[6C3AAA7D-9DC6-3D91-8BCE-6B7E216F69DB]@0xfffffe001c2cf140->0xfffffe001c2d6683


MacBook Pro 14″, macOS 15.4

Posted on Apr 14, 2025 6:55 AM

Reply
5 replies
Sort By: 

Apr 15, 2025 7:58 AM in response to KarolRe

KarolRe wrote:

I don't get the kernel crashes when not on the VPN. The question is how to diagnose/fix the situation.


You already diagnosed and fixed the issue.


A true VPN tunnel, for example between you and your job or a Bank server would be of value, otherwise might be time to re-think the usage. 


 If your work mandates the use of a  point to point VPN— contact your work IT network admin, and verify if they block or not access to the Internet which is common practice on a work network.




see: Public VPN's are anything but private or safe


https://krebsonsecurity.com/2024/05/why-your-vpn-may-not-be-as-secure-as-it-claims/


https://gist.github.com/joepie91/5a9909939e6ce7d09e29


https://www.eccu.edu/blog/cybersecurity/5-reasons-why-you-should-not-use-free-vpns/


https://krebsonsecurity.com/2024/05/is-your-computer-part-of-the-largest-botnet-ever/


https://www.pcmag.com/news/the-feds-have-some-advice-for-highly-targeted-individuals-dont-use-a-vpn




Reply

Apr 14, 2025 9:52 AM in response to KarolRe

KarolRe wrote:

I'm having kernel panics on M1 MacBook Pro afer upgrade to Sequoia 15.4 when connected to VPN with openfortivpn. Do you happen to know how to troubleshoot or fix this? Details below, thanks 👋



Disable or remove your VPN and compare your results...

Reply

Apr 21, 2025 4:11 AM in response to KarolRe

Same issue on M3 Macbook Pro. Started with MacOS 15.4.x when tried to upload the 5GB file.

Retried with Fortinet SSL VPN (https://www.fortinet.com/support/product-downloads#vpn) and everything worked fine. For now on will use Fortinet SSL until the thing with openfortivpn will not get fixed.

Reply

Kernel panic on M1 MacBook Pro after upgrade to Sequoia 15.4

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.