Kernel panics during scheduled tasks

Plex Media Server Desktops & Laptops
1

Server Version#: 1.30.1.6497

While running scheduled background tasks on a large group of new media, my M1 iMac was suffering nightly kernel panics. There doesn’t seem to be any useful information in the logs, but I did note that the last log in the system before the crash was always Plex running background analysis, and the crashes always happened about 45 minutes after the scheduled tasks window started.

I disabled “Perform extensive media analysis during maintenance” as a scheduled task, and that seems to have fixed the problem. No kernel panics for the last 48 hours, previously was happening every single night.

Looking through the forums, I see this has been a problem reported on Macs a few times in the past. It’s been chalked up to “a bug in MacOS.” While there might be some flaw in the MacOS software that makes the computer prone to this, the fact is that no other programs are ever causing kernel panics, only Plex. Is there any chance of a deeper look into this, or at least a workaround?

panic(cpu 5 caller 0xfffffe002ba61698): !pageList phys_addr @IOMemoryDescriptor.cpp:3310
Debugger message: panic
Memory ID: 0xff
OS release type: User
OS version: 22D5027d
Kernel version: Darwin Kernel Version 22.3.0: Sun Dec  4 18:16:43 PST 2022; root:xnu-8792.80.21.0.2~9/RELEASE_ARM64_T8103
Fileset Kernelcache UUID: DD4D00E5D7CC8626A96C5DF8AB3249F9
Kernel UUID: 34764A4D-E46A-3316-83B0-2E82A1D14958
Boot session UUID: 46926BC6-A3DE-4B5D-B1E3-3543579E56DA
iBoot version: iBoot-8419.80.3
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x0000000022f70000
KernelCache base:  0xfffffe0029f74000
Kernel slide:      0x00000000241b4000
Kernel text base:  0xfffffe002b1b8000
Kernel text exec slide: 0x000000002429c000
Kernel text exec base:  0xfffffe002b2a0000
mach_absolute_time: 0xd0c27f6b344
Epoch Time:        sec       usec
  Boot    : 0x63a7e628 0x0007cf0c
  Sleep   : 0x63a9dd99 0x0000012b
  Wake    : 0x63a9f90b 0x000bc504
  Calendar: 0x63b30f50 0x000dd19a

Zone info:
  Zone map: 0xfffffe1000150000 - 0xfffffe3000150000
  . VM    : 0xfffffe1000150000 - 0xfffffe14cce1c000
  . RO    : 0xfffffe14cce1c000 - 0xfffffe16667b4000
  . GEN0  : 0xfffffe16667b4000 - 0xfffffe1b33480000
  . GEN1  : 0xfffffe1b33480000 - 0xfffffe200014c000
  . GEN2  : 0xfffffe200014c000 - 0xfffffe24cce18000
  . GEN3  : 0xfffffe24cce18000 - 0xfffffe2999ae4000
  . DATA  : 0xfffffe2999ae4000 - 0xfffffe3000150000
  Metadata: 0xfffffe828379c000 - 0xfffffe828b79c000
  Bitmaps : 0xfffffe828b79c000 - 0xfffffe82911a8000

CORE 0 recently retired instr at 0xfffffe002b45bad4
CORE 1 recently retired instr at 0xfffffe002b45bad4
CORE 2 recently retired instr at 0xfffffe002b45bad4
CORE 3 recently retired instr at 0xfffffe002b45bad4
CORE 4 recently retired instr at 0xfffffe002b45bad4
CORE 5 recently retired instr at 0xfffffe002b45a3d4
CORE 6 recently retired instr at 0xfffffe002b45bad4
CORE 7 recently retired instr at 0xfffffe002b45bad4
TPIDRx_ELy = {1: 0xfffffe24d0e71828  0: 0x0000000000000005  0ro: 0x00000001eff8c120 }
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=0xfffffe002b33bc90, LR=0xfffffe002b33bc90, FP=0xfffffe8fff35ff00
CORE 1: PC=0x00000001ae5f8b44, LR=0x000000010f35d530, FP=0x000000016fadb820
CORE 2: PC=0xfffffe002ba2c6b0, LR=0xfffffe002ba2ae60, FP=0xfffffe8fff1afcb0
CORE 3: PC=0x0000000194a472f4, LR=0x000000019aab649c, FP=0x000000016f75c9f0
CORE 4: PC=0x0000000194acc76c, LR=0x0000000194acc804, FP=0x000000016d1081e0
CORE 5 is the one that panicked. Check the full backtrace for details.
CORE 6: PC=0xfffffe002b33bc90, LR=0xfffffe002b33bc90, FP=0xfffffe8ffedfff00
CORE 7: PC=0xfffffe002b33bc90, LR=0xfffffe002b33bc90, FP=0xfffffe8fff383f00
Compressor Info: 7% of compressed pages limit (OK) and 7% of segments limit (OK) with 2 swapfiles and OK swap space
Panicked task 0xfffffe24d5f92df0: 1795 pages, 9 threads: pid 76235: Plex Transcoder
Panicked thread: 0xfffffe24d0e71828, backtrace: 0xfffffe8fff1128a0, tid: 14265441
		  lr: 0xfffffe002b2fec68  fp: 0xfffffe8fff112910
		  lr: 0xfffffe002b2fea10  fp: 0xfffffe8fff112990
		  lr: 0xfffffe002b462560  fp: 0xfffffe8fff1129b0
		  lr: 0xfffffe002b453fc8  fp: 0xfffffe8fff112a20
		  lr: 0xfffffe002b4518cc  fp: 0xfffffe8fff112ae0
		  lr: 0xfffffe002b2a77f8  fp: 0xfffffe8fff112af0
		  lr: 0xfffffe002b2fe39c  fp: 0xfffffe8fff112ea0
		  lr: 0xfffffe002bb42bf0  fp: 0xfffffe8fff112ec0
		  lr: 0xfffffe002ba61698  fp: 0xfffffe8fff112f70
		  lr: 0xfffffe002ba60b00  fp: 0xfffffe8fff113050
		  lr: 0xfffffe002d7d86dc  fp: 0xfffffe8fff1130d0
		  lr: 0xfffffe002d7d8dd0  fp: 0xfffffe8fff113150
		  lr: 0xfffffe002d7d95f0  fp: 0xfffffe8fff1131f0
		  lr: 0xfffffe002c80e768  fp: 0xfffffe8fff113260
		  lr: 0xfffffe002c805dc0  fp: 0xfffffe8fff1132b0
		  lr: 0xfffffe002d7e3f4c  fp: 0xfffffe8fff113360
		  lr: 0xfffffe002b53f9a0  fp: 0xfffffe8fff1133e0
		  lr: 0xfffffe002b4d012c  fp: 0xfffffe8fff113490
		  lr: 0xfffffe002ded5c7c  fp: 0xfffffe8fff1135b0
		  lr: 0xfffffe002b4db544  fp: 0xfffffe8fff113750
		  lr: 0xfffffe002b4e4090  fp: 0xfffffe8fff113810
		  lr: 0xfffffe002b4e438c  fp: 0xfffffe8fff113880
		  lr: 0xfffffe002b4e17cc  fp: 0xfffffe8fff113a70
		  lr: 0xfffffe002b4e0c50  fp: 0xfffffe8fff113ad0
		  lr: 0xfffffe002def99cc  fp: 0xfffffe8fff113c00
		  lr: 0xfffffe002b524610  fp: 0xfffffe8fff113c70
		  lr: 0xfffffe002b5242a8  fp: 0xfffffe8fff113cd0
		  lr: 0xfffffe002b85812c  fp: 0xfffffe8fff113d40
		  lr: 0xfffffe002b858318  fp: 0xfffffe8fff113dc0
		  lr: 0xfffffe002b961130  fp: 0xfffffe8fff113e50
		  lr: 0xfffffe002b451ab8  fp: 0xfffffe8fff113f10
		  lr: 0xfffffe002b2a77f8  fp: 0xfffffe8fff113f20
      Kernel Extensions in backtrace:
         com.apple.iokit.IOStorageFamily(2.1)[9A37C154-B72F-3694-94B3-2E1E490FC917]@0xfffffe002d7cc0b0->0xfffffe002d7ecaef
         com.apple.filesystems.apfs(2142.80.4)[DA1738FA-BBF6-35EE-8E84-5DC5F99A2E5D]@0xfffffe002de8e8a0->0xfffffe002dfcc6bb
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[3E56558A-9A2C-3501-8A79-C1FF54C1F5EF]@0xfffffe002c2a1f20->0xfffffe002c2a6e0b
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[B05D55E3-2DB4-38F0-B646-8A67D875F915]@0xfffffe002cd5ed50->0xfffffe002cd66a7f
            dependency: com.apple.iokit.IOStorageFamily(2.1)[9A37C154-B72F-3694-94B3-2E1E490FC917]@0xfffffe002d7cc0b0->0xfffffe002d7ecaef
            dependency: com.apple.kec.corecrypto(12.0)[4C42D170-04EC-39F6-AE2B-13F2C0A42EE3]@0xfffffe002e00b0c0->0xfffffe002e053abf
            dependency: com.apple.security.AppleImage4(5.0.0)[6EFCEC47-7D5A-3C6B-8466-A5AFBCAF3B8C]@0xfffffe002c53a9c0->0xfffffe002c5536ef
         com.apple.driver.AppleRAID(5.1)[AC8E6E65-4899-3B36-A89C-C1FFD55F6F4C]@0xfffffe002c7f68a0->0xfffffe002c814f2b
            dependency: com.apple.iokit.IOStorageFamily(2.1)[9A37C154-B72F-3694-94B3-2E1E490FC917]@0xfffffe002d7cc0b0->0xfffffe002d7ecaef

panic(cpu 4 caller 0xfffffe002a175698): !pageList phys_addr @IOMemoryDescriptor.cpp:3310
Debugger message: panic
Memory ID: 0xff
OS release type: User
OS version: 22D5027d
Kernel version: Darwin Kernel Version 22.3.0: Sun Dec  4 18:16:43 PST 2022; root:xnu-8792.80.21.0.2~9/RELEASE_ARM64_T8103
Fileset Kernelcache UUID: DD4D00E5D7CC8626A96C5DF8AB3249F9
Kernel UUID: 34764A4D-E46A-3316-83B0-2E82A1D14958
Boot session UUID: 4979DB7C-124F-4D00-BCB7-E374357EFA06
iBoot version: iBoot-8419.80.3
secure boot?: YES
roots installed: 0
Paniclog version: 14
KernelCache slide: 0x0000000021684000
KernelCache base:  0xfffffe0028688000
Kernel slide:      0x00000000228c8000
Kernel text base:  0xfffffe00298cc000
Kernel text exec slide: 0x00000000229b0000
Kernel text exec base:  0xfffffe00299b4000
mach_absolute_time: 0x17ed0fb8cca
Epoch Time:        sec       usec
  Boot    : 0x63b530e2 0x0003f92c
  Sleep   : 0x63b56e58 0x00088ec3
  Wake    : 0x63b57b1c 0x00067b25
  Calendar: 0x63b68176 0x000c4bfb

Zone info:
  Zone map: 0xfffffe101cee4000 - 0xfffffe301cee4000
  . VM    : 0xfffffe101cee4000 - 0xfffffe14e9bb0000
  . RO    : 0xfffffe14e9bb0000 - 0xfffffe1683548000
  . GEN0  : 0xfffffe1683548000 - 0xfffffe1b50214000
  . GEN1  : 0xfffffe1b50214000 - 0xfffffe201cee0000
  . GEN2  : 0xfffffe201cee0000 - 0xfffffe24e9bac000
  . GEN3  : 0xfffffe24e9bac000 - 0xfffffe29b6878000
  . DATA  : 0xfffffe29b6878000 - 0xfffffe301cee4000
  Metadata: 0xfffffe4cb6630000 - 0xfffffe4cbe630000
  Bitmaps : 0xfffffe4cbe630000 - 0xfffffe4cc4030000

CORE 0 recently retired instr at 0xfffffe0029b6fad4
CORE 1 recently retired instr at 0xfffffe0029b6fad4
CORE 2 recently retired instr at 0xfffffe0029b6fad4
CORE 3 recently retired instr at 0xfffffe0029b6fad4
CORE 4 recently retired instr at 0xfffffe0029b6e3d4
CORE 5 recently retired instr at 0xfffffe0029b6fad4
CORE 6 recently retired instr at 0xfffffe0029b6fad4
CORE 7 recently retired instr at 0xfffffe0029b6fad4
TPIDRx_ELy = {1: 0xfffffe24ede9b808  0: 0x0000000000000004  0ro: 0x00000001f2908120 }
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=0xfffffe0029b6b080, LR=0xfffffe0029b6b07c, FP=0xfffffe8ff8dffe90
CORE 1: PC=0xfffffe0029a4fc90, LR=0xfffffe0029a4fc90, FP=0xfffffe8ff9833f00
CORE 2: PC=0xfffffe0029b6b080, LR=0xfffffe0029b6b07c, FP=0xfffffe8ff927fe90
CORE 3: PC=0xfffffe0029a4fc90, LR=0xfffffe0029a4fc90, FP=0xfffffe8ff9aeff00
CORE 4 is the one that panicked. Check the full backtrace for details.
CORE 5: PC=0xfffffe002c60c1a8, LR=0xfffffe002c60bc84, FP=0xfffffe8ff8ebbb10
CORE 6: PC=0xfffffe0029a4fc94, LR=0xfffffe0029a4fc90, FP=0xfffffe8ff8f73f00
CORE 7: PC=0xfffffe0029a4fc94, LR=0xfffffe0029a4fc90, FP=0xfffffe8ff92dbf00
Compressor Info: 2% of compressed pages limit (OK) and 3% of segments limit (OK) with 0 swapfiles and OK swap space
Panicked task 0xfffffe201af5f9b8: 2188 pages, 7 threads: pid 6051: Plex Media Scann
Panicked thread: 0xfffffe24ede9b808, backtrace: 0xfffffe8ff9b4e9d0, tid: 1739642
		  lr: 0xfffffe0029a12c68  fp: 0xfffffe8ff9b4ea40
		  lr: 0xfffffe0029a12a10  fp: 0xfffffe8ff9b4eac0
		  lr: 0xfffffe0029b76560  fp: 0xfffffe8ff9b4eae0
		  lr: 0xfffffe0029b67fc8  fp: 0xfffffe8ff9b4eb50
		  lr: 0xfffffe0029b658cc  fp: 0xfffffe8ff9b4ec10
		  lr: 0xfffffe00299bb7f8  fp: 0xfffffe8ff9b4ec20
		  lr: 0xfffffe0029a1239c  fp: 0xfffffe8ff9b4efd0
		  lr: 0xfffffe002a256bf0  fp: 0xfffffe8ff9b4eff0
		  lr: 0xfffffe002a175698  fp: 0xfffffe8ff9b4f0a0
		  lr: 0xfffffe002a174b00  fp: 0xfffffe8ff9b4f180
		  lr: 0xfffffe002beec6dc  fp: 0xfffffe8ff9b4f200
		  lr: 0xfffffe002beecdd0  fp: 0xfffffe8ff9b4f280
		  lr: 0xfffffe002beed5f0  fp: 0xfffffe8ff9b4f320
		  lr: 0xfffffe002af22768  fp: 0xfffffe8ff9b4f390
		  lr: 0xfffffe002af19dc0  fp: 0xfffffe8ff9b4f3e0
		  lr: 0xfffffe002bef7f4c  fp: 0xfffffe8ff9b4f490
		  lr: 0xfffffe0029c539a0  fp: 0xfffffe8ff9b4f510
		  lr: 0xfffffe0029be412c  fp: 0xfffffe8ff9b4f5c0
		  lr: 0xfffffe002c5e9c7c  fp: 0xfffffe8ff9b4f6e0
		  lr: 0xfffffe0029bef544  fp: 0xfffffe8ff9b4f880
		  lr: 0xfffffe0029bf5a70  fp: 0xfffffe8ff9b4fa70
		  lr: 0xfffffe0029bf4c50  fp: 0xfffffe8ff9b4fad0
		  lr: 0xfffffe002c60d9cc  fp: 0xfffffe8ff9b4fc00
		  lr: 0xfffffe0029c38610  fp: 0xfffffe8ff9b4fc70
		  lr: 0xfffffe0029c382a8  fp: 0xfffffe8ff9b4fcd0
		  lr: 0xfffffe0029f6c12c  fp: 0xfffffe8ff9b4fd40
		  lr: 0xfffffe0029f6c318  fp: 0xfffffe8ff9b4fdc0
		  lr: 0xfffffe002a075130  fp: 0xfffffe8ff9b4fe50
		  lr: 0xfffffe0029b65ab8  fp: 0xfffffe8ff9b4ff10
		  lr: 0xfffffe00299bb7f8  fp: 0xfffffe8ff9b4ff20
      Kernel Extensions in backtrace:
         com.apple.iokit.IOStorageFamily(2.1)[9A37C154-B72F-3694-94B3-2E1E490FC917]@0xfffffe002bee00b0->0xfffffe002bf00aef
         com.apple.filesystems.apfs(2142.80.4)[DA1738FA-BBF6-35EE-8E84-5DC5F99A2E5D]@0xfffffe002c5a28a0->0xfffffe002c6e06bb
            dependency: com.apple.driver.AppleEffaceableStorage(1.0)[3E56558A-9A2C-3501-8A79-C1FF54C1F5EF]@0xfffffe002a9b5f20->0xfffffe002a9bae0b
            dependency: com.apple.iokit.CoreAnalyticsFamily(1)[B05D55E3-2DB4-38F0-B646-8A67D875F915]@0xfffffe002b472d50->0xfffffe002b47aa7f
            dependency: com.apple.iokit.IOStorageFamily(2.1)[9A37C154-B72F-3694-94B3-2E1E490FC917]@0xfffffe002bee00b0->0xfffffe002bf00aef
            dependency: com.apple.kec.corecrypto(12.0)[4C42D170-04EC-39F6-AE2B-13F2C0A42EE3]@0xfffffe002c71f0c0->0xfffffe002c767abf
            dependency: com.apple.security.AppleImage4(5.0.0)[6EFCEC47-7D5A-3C6B-8466-A5AFBCAF3B8C]@0xfffffe002ac4e9c0->0xfffffe002ac676ef
         com.apple.driver.AppleRAID(5.1)[AC8E6E65-4899-3B36-A89C-C1FFD55F6F4C]@0xfffffe002af0a8a0->0xfffffe002af28f2b
            dependency: com.apple.iokit.IOStorageFamily(2.1)[9A37C154-B72F-3694-94B3-2E1E490FC917]@0xfffffe002bee00b0->0xfffffe002bf00aef
2

A kernel panic is the fault of the OS or the hardware, FULL STOP. The primary responsibility of an OS is to prevent one application from interfering with another and a kernel panic is an horrendous failure of this responsibility. An application should never ever ever be capable of causing a kernel panic no matter what it does and any case where one does is the fault of the OS or hardware screwing up.

That aside, one of the more common causes is hardware decoding because these drivers and hardware appear to be less robust than they should be. You may want to try disabling hardware decoding to see if it makes a difference.

3

I certainly understand that, but again: only one program on my computer has ever caused this, and it’s Plex. All other programs that use hardware acceleration do not have any problems. That’s why I’m asking if there might be a workaround that could prevent issues, even if the fault ultimately lies with MacOS itself.

My system has remained stable since disabling “Extensive media analysis,” even with hardware acceleration enabled. I can stream to multiple computers, both local and remote, with hardware acceleration enabled. It seems to be something with the scheduled media analysis process.

4

You are still mislaying the blame. The problem is still the OS or hardware.

I gave you one possibility. Another could be filesystem corruption, bad sectors in the drive, or general issues with the drive since your panics mention the APFS file system.

5

You have disk corruption or pending disk failure.

Move the PMS data directory to a different drive and re-test.

If you encounter issues moving the files (which is highly likely) you’ll know this is the problem.

If not report back here.

6

You are still mislaying the blame. The problem is still the OS or hardware.

I’m sorry, that was not my intent. To rephrase: I’m trying to find out if there’s any way Plex can work around the MacOS software or hardware failures to maintain functionality without having to turn Plex features off.

You have disk corruption or pending disk failure. Move the PMS data directory to a different drive and re-test.

While trying to diagnose this problem I performed a full database restore from a backup, and moved the files onto a different drive for good measure. The problem persisted every single night during scheduled tasks. Since turning off the “Extensive media analysis” background task, however, there have been no further crashes.

7

This is telling me somewhere on your drive that stores all your media there may be data corruption or pending disk failure.

Is the PMS data directory on the same drive as your media?

Can you access the S.M.A.R.T drive diagnostic data and paste your results here. This will tell us what the drive is saying about itself.

8

Data directory and media are usually stored on separate drives, though during my testing I had them both on the same drive (internal) and was still getting kernel panics.

Internal disk0 shows:

SMART Status:              Verified

The external HD is USB and I’m not sure how to get S.M.A.R.T. status from it. It’s actually two separate drives in a mirrored RAID array that shows good health in system diagnostics. However, the problem was also occurring when all files were stored on the internal drive.

9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.