Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
panic & crashes with BS 11.3.1 and OCLP 0.1.5

i experience random reboots (sometimes with apples notification that my machine crashed, in different languages on reboot) and still can't pin point it down to the main reason.

I also collected some reports and try to collect more. there are no crash logs on the EFI partition.
its totally random and I think its my SSD+HDD self-made FusionDrive, but not totally sure. maybe you guys can read something

thanks in advance.


Code:
panic(cpu 1 caller 0xffffff802ea9f6b6): [data.kalloc.256]: element modified after free (off:0, val:0x0000f80000000000, sz:256, ptr:0xffffff938e6f7100, prot:zero)
    0: 0x0000f80000000000
   32: 0x0000ff0000000000
  144: 0x0000ff0000000000
  176: 0x0000ff0000000000
  184: 0x0000ff0000000000
Backtrace (CPU 1), Frame : Return Address
0xffffffa0f2323230 : 0xffffff802e28e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0f2323280 : 0xffffff802e3d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0f23232c0 : 0xffffff802e3c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa0f2323310 : 0xffffff802e232a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0f2323330 : 0xffffff802e28d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0f2323450 : 0xffffff802e28db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0f23234c0 : 0xffffff802ea9d68a mach_kernel : _panic + 0x54
0xffffffa0f2323530 : 0xffffff802ea9f6b6 mach_kernel : _kheap_temp_leak_panic + 0x1b7c
0xffffffa0f23239b0 : 0xffffff802e2ec816 mach_kernel : _work_interval_port_type_render_server + 0x4446
0xffffffa0f2323a20 : 0xffffff802e29d60c mach_kernel : _ipc_thread_port_unpin + 0x1cc
0xffffffa0f2323a70 : 0xffffff802e26998e mach_kernel : _ipc_kmsg_get_from_kernel + 0xae
0xffffffa0f2323ad0 : 0xffffff802e294767 mach_kernel : _mach_msg_send_from_kernel_proper + 0x37
0xffffffa0f2323b00 : 0xffffff802ea24320 mach_kernel : __ZN12IOUserClient18_sendAsyncResult64EPyiS0_jj + 0x280
0xffffffa0f2323c40 : 0xffffff8030fb8a6f com.apple.iokit.IOTimeSyncFamily : __ZN20IOTimeSyncUserClient21sendAsyncNotificationEjyy + 0x7f
0xffffffa0f2323ca0 : 0xffffff8030fbd48b com.apple.iokit.IOTimeSyncFamily : __ZN17IOTimeSyncService16sendNotificationEjyy + 0xb3
0xffffffa0f2323cf0 : 0xffffff7fc796c229 com.apple.plugin.IOgPTPPlugin : __ZN16IOTimeSyncDomain18receivedSyncOnPortEP14IOTimeSyncPortP20IOTimeSyncDomainSync + 0xbe1
0xffffffa0f2323de0 : 0xffffff7fc7959713 com.apple.plugin.IOgPTPPlugin : __ZN26IOTimeSyncTimeSyncTimePort14synthesizeSyncEv + 0x167
0xffffffa0f2323e90 : 0xffffff7fc796eba5 com.apple.plugin.IOgPTPPlugin : __ZN24IOTimeSyncLocalClockPort13syncTimerFireEP18IOTimerEventSource + 0x13
0xffffffa0f2323eb0 : 0xffffff802e9f54f5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffa0f2323f20 : 0xffffff802e9f4c88 mach_kernel : __ZN18IOTimerEventSource12checkForWorkEv + 0x38
0xffffffa0f2323f30 : 0xffffff802e9eeaae mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e
0xffffffa0f2323f70 : 0xffffff802e9ee096 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffffa0f2323fa0 : 0xffffff802e23213e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOTimeSyncFamily(980.4)[A5FA159E-C468-37EB-92A2-A4B6E527C671]@0xffffff8030fac000->0xffffff8030fc7fff
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[EFF68ECC-483B-3BAC-82B9-09C8F0600009]@0xffffff8030ad2000->0xffffff8030ae8fff
         com.apple.plugin.IOgPTPPlugin(980.4)[DA74055E-BAE8-30FB-86CD-0D4A6B5ABBD8]@0xffffff7fc7946000->0xffffff7fc79aafff
            dependency: com.apple.iokit.IOHIDFamily(2.0.0)[C365D2A4-769B-3399-9F8D-31DDAA238589]@0xffffff8030a0e000->0xffffff8030a6afff
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[EFF68ECC-483B-3BAC-82B9-09C8F0600009]@0xffffff8030ad2000->0xffffff8030ae8fff
            dependency: com.apple.iokit.IOSkywalkFamily(1)[8E95C676-D763-3923-BE43-E8BE08DD3C23]@0xffffff8030e2a000->0xffffff8030e4bfff
            dependency: com.apple.iokit.IOTimeSyncFamily(980.4)[A5FA159E-C468-37EB-92A2-A4B6E527C671]@0xffffff8030fac000->0xffffff8030fc7fff
            dependency: com.apple.kec.Libm(1)[526EF6DE-89A2-334E-A748-F37E33579C6F]@0xffffff803130a000->0xffffff8031317fff

Process name corresponding to current thread: kernel_task
Boot args: keepsyms=1 debug=0x100 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20E241

Kernel version:
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Kernel UUID: 068F99A3-1DB3-31C0-87D5-09942F122BB6
KernelCache slide: 0x000000002e000000
KernelCache base:  0xffffff802e200000
Kernel slide:      0x000000002e010000
Kernel text base:  0xffffff802e210000
__HIB  text base: 0xffffff802e100000
System model name: iMac12,2 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3268069509353
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000002f8e81f51aa
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000129872d1d4 0x0000000000000000

Code:
panic(cpu 6 caller 0xffffff80047c52a6): Kernel trap at 0xffffff80047a5b32, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000372106247, CR4: 0x00000000000626e0
RAX: 0x0000000000000060, RBX: 0x0000000000000000, RCX: 0x0000000000000007, RDX: 0x0000000000000001
RSP: 0xffffffa0d0443b20, RBP: 0xffffffa0d0443b90, RSI: 0x0000600002520000, RDI: 0xffffff86a5fdb300
R8:  0xffffff8021400000, R9:  0x000ffffffffff000, R10: 0xffffff801238ac90, R11: 0xffffff8013a24490
R12: 0xffffff86a5fdb300, R13: 0x000000015fa12000, R14: 0x0000600002520000, R15: 0x0000000000000000
RFL: 0x0000000000010206, RIP: 0xffffff80047a5b32, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x6, PL: 1, VF: 0

Backtrace (CPU 6), Frame : Return Address
0xffffffa0d0443540 : 0xffffff800468e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0d0443590 : 0xffffff80047d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0d04435d0 : 0xffffff80047c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa0d0443620 : 0xffffff8004632a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0d0443640 : 0xffffff800468d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0d0443760 : 0xffffff800468db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0d04437d0 : 0xffffff8004e9d68a mach_kernel : _panic + 0x54
0xffffffa0d0443840 : 0xffffff80047c52a6 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffa0d04439c0 : 0xffffff80047c4f8d mach_kernel : _kernel_trap + 0x60d
0xffffffa0d0443a10 : 0xffffff8004632a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0d0443a30 : 0xffffff80047a5b32 mach_kernel : _phys_attribute_clear + 0x1a2
0xffffffa0d0443b90 : 0xffffff80047523b7 mach_kernel : _vm_page_balance_inactive + 0x107
0xffffffa0d0443be0 : 0xffffff8004764874 mach_kernel : _vm_page_queues_remove + 0x574
0xffffffa0d0443c30 : 0xffffff8004765e17 mach_kernel : _vm_page_free_prepare_queues + 0x57
0xffffffa0d0443c70 : 0xffffff8004748c28 mach_kernel : _vm_io_reprioritize_init + 0x1998
0xffffffa0d0443ce0 : 0xffffff80047477ba mach_kernel : _vm_io_reprioritize_init + 0x52a
0xffffffa0d0443d10 : 0xffffff8004748ad5 mach_kernel : _vm_io_reprioritize_init + 0x1845
0xffffffa0d0443d40 : 0xffffff8004747ce2 mach_kernel : _vm_io_reprioritize_init + 0xa52
0xffffffa0d0443d80 : 0xffffff800473345b mach_kernel : _vm_map_remove + 0xa3b
0xffffffa0d0443ed0 : 0xffffff8004732a93 mach_kernel : _vm_map_remove + 0x73
0xffffffa0d0443f00 : 0xffffff8004c1da43 mach_kernel : _munmap + 0xb3
0xffffffa0d0443f40 : 0xffffff8004d40dae mach_kernel : _unix_syscall64 + 0x2ce
0xffffffa0d0443fa0 : 0xffffff80046331f6 mach_kernel : _hndl_unix_scall64 + 0x16

Process name corresponding to current thread: Microsoft Teams Helper (Renderer
Boot args: keepsyms=1 debug=0x100 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20E241

Kernel version:
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Kernel UUID: 068F99A3-1DB3-31C0-87D5-09942F122BB6
KernelCache slide: 0x0000000004400000
KernelCache base:  0xffffff8004600000
Kernel slide:      0x0000000004410000
Kernel text base:  0xffffff8004610000
__HIB  text base: 0xffffff8004500000
System model name: iMac12,2 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 24478866024470
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000016436e1d30d3
  Sleep   : 0x000013ddcc5bbc53 0x000000004189e2be 0x00000a1cc06cabf9
  Wake    : 0x000013dddc41c68a 0x00000000411ed62e 0x000013dddb33a1e0
The usual suspects are memory modules and other hardware components when using a 10 year old system. Can you assure these crashes are a Big Sur only phenomenon?
 
  • Like
Reactions: xanderon
I can, because the same hardware ran bullet proof in the last months. something changed around 11.3 or ~0.1.3 OCLP

i will do a memtest stress test on the 24gb
 
I can, because the same hardware ran bullet proof in the last months. something changed around 11.3 or ~0.1.3 OCLP

i will do a memtest stress test on the 24gb
Oh, we had this less than 24h ago when a user assured everything ran fine with High Sierra in the past just to detect that it does not run fine, now. Historical data is of no use when it comes to a current and new infection.

Memtest is not a 100% solution. Pull all modules and run with one or two only, change these until you reach a stable situation.
 
  • Like
Reactions: K two and xanderon
I have a Mid 2010 17" MacBook Pro 6,1 - still on High Sierra. I'm comfortable doing the OCLP, as I had good luck with my Metal-upgraded iMac.

But I've been putting off upgrading my 17" MBP. Would you say the performance and features of Big Sur outweigh the UI bugs at this point? I would mainly be using 1st party Apple apps on this machine. It's already set with an SSD and 8GB of RAM. I didn't have the best of luck with Catalina Patcher due to some weird UI glitches, so I've stuck with High Sierra so far.
I have Mojave, Catalina and Big Sur installed on an SSD; first two share single partition, Big Sur resides in its own partition. I did not notice UI problems with Catalina, but you may be using applications which do have interface requirements unique to Metal dependent programs(?)

What I would suggest is to create a test partition on your SSD and install Big Sur on that isolated volume.
You can then experiment with Big Sur without affecting the rest of your computer, and potentially being forced to reinstall OS and your data files. A partition can be created with disk utility without erasing the whole drive.
A caveat to this scenario is to make sure that a full back up of your drive is available, before creating a new partition. It's an insurance should partition process fail.
Do compare your computer's hardware with MacBook Pro 5,2 to assure that data from the latter can be extrapolated to your machine.

Hope this information may be of help.
 
  • Like
Reactions: K two
I have Mojave, Catalina and Big Sur installed on an SSD; first two share single partition, Big Sur resides in its own partition. I did not notice UI problems with Catalina, but you may be using applications which do have interface requirements unique to Metal dependent programs(?)

What I would suggest is to create a test partition on your SSD and install Big Sur on that isolated volume.
You can then experiment with Big Sur without affecting the rest of your computer, and potentially being forced to reinstall OS and your data files. A partition can be created with disk utility without erasing the whole drive.
A caveat to this scenario is to make sure that a full back up of your drive is available, before creating a new partition. It's an insurance should partition process fail.
Do compare your computer's hardware with MacBook Pro 5,2 to assure that data from the latter can be extrapolated to your machine.

Hope this information may be of help.

Thank you for your response. I might actually just pull out the existing HS SSD and build a OCLP Big Sur on a fresh drive.

On these 6,1 units, it is very easy to open up and drop in a new SSD. I will go that route, since I do have a spare.
 
  • Like
Reactions: RogueB
Crash Report spends lots of time with this crash. Patch related?
anyone else?.jpg
 
  • Like
Reactions: hvds
panic & crashes with BS 11.3.1 and OCLP 0.1.5

i experience random reboots (sometimes with apples notification that my machine crashed, in different languages on reboot) and still can't pin point it down to the main reason.

I also collected some reports and try to collect more. there are no crash logs on the EFI partition.
its totally random and I think its my SSD+HDD self-made FusionDrive, but not totally sure. maybe you guys can read something

thanks in advance.


Code:
panic(cpu 1 caller 0xffffff802ea9f6b6): [data.kalloc.256]: element modified after free (off:0, val:0x0000f80000000000, sz:256, ptr:0xffffff938e6f7100, prot:zero)
    0: 0x0000f80000000000
   32: 0x0000ff0000000000
  144: 0x0000ff0000000000
  176: 0x0000ff0000000000
  184: 0x0000ff0000000000
Backtrace (CPU 1), Frame : Return Address
0xffffffa0f2323230 : 0xffffff802e28e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0f2323280 : 0xffffff802e3d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0f23232c0 : 0xffffff802e3c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa0f2323310 : 0xffffff802e232a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0f2323330 : 0xffffff802e28d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0f2323450 : 0xffffff802e28db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0f23234c0 : 0xffffff802ea9d68a mach_kernel : _panic + 0x54
0xffffffa0f2323530 : 0xffffff802ea9f6b6 mach_kernel : _kheap_temp_leak_panic + 0x1b7c
0xffffffa0f23239b0 : 0xffffff802e2ec816 mach_kernel : _work_interval_port_type_render_server + 0x4446
0xffffffa0f2323a20 : 0xffffff802e29d60c mach_kernel : _ipc_thread_port_unpin + 0x1cc
0xffffffa0f2323a70 : 0xffffff802e26998e mach_kernel : _ipc_kmsg_get_from_kernel + 0xae
0xffffffa0f2323ad0 : 0xffffff802e294767 mach_kernel : _mach_msg_send_from_kernel_proper + 0x37
0xffffffa0f2323b00 : 0xffffff802ea24320 mach_kernel : __ZN12IOUserClient18_sendAsyncResult64EPyiS0_jj + 0x280
0xffffffa0f2323c40 : 0xffffff8030fb8a6f com.apple.iokit.IOTimeSyncFamily : __ZN20IOTimeSyncUserClient21sendAsyncNotificationEjyy + 0x7f
0xffffffa0f2323ca0 : 0xffffff8030fbd48b com.apple.iokit.IOTimeSyncFamily : __ZN17IOTimeSyncService16sendNotificationEjyy + 0xb3
0xffffffa0f2323cf0 : 0xffffff7fc796c229 com.apple.plugin.IOgPTPPlugin : __ZN16IOTimeSyncDomain18receivedSyncOnPortEP14IOTimeSyncPortP20IOTimeSyncDomainSync + 0xbe1
0xffffffa0f2323de0 : 0xffffff7fc7959713 com.apple.plugin.IOgPTPPlugin : __ZN26IOTimeSyncTimeSyncTimePort14synthesizeSyncEv + 0x167
0xffffffa0f2323e90 : 0xffffff7fc796eba5 com.apple.plugin.IOgPTPPlugin : __ZN24IOTimeSyncLocalClockPort13syncTimerFireEP18IOTimerEventSource + 0x13
0xffffffa0f2323eb0 : 0xffffff802e9f54f5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xffffffa0f2323f20 : 0xffffff802e9f4c88 mach_kernel : __ZN18IOTimerEventSource12checkForWorkEv + 0x38
0xffffffa0f2323f30 : 0xffffff802e9eeaae mach_kernel : __ZN10IOWorkLoop15runEventSourcesEv + 0x11e
0xffffffa0f2323f70 : 0xffffff802e9ee096 mach_kernel : __ZN10IOWorkLoop10threadMainEv + 0x36
0xffffffa0f2323fa0 : 0xffffff802e23213e mach_kernel : _call_continuation + 0x2e
      Kernel Extensions in backtrace:
         com.apple.iokit.IOTimeSyncFamily(980.4)[A5FA159E-C468-37EB-92A2-A4B6E527C671]@0xffffff8030fac000->0xffffff8030fc7fff
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[EFF68ECC-483B-3BAC-82B9-09C8F0600009]@0xffffff8030ad2000->0xffffff8030ae8fff
         com.apple.plugin.IOgPTPPlugin(980.4)[DA74055E-BAE8-30FB-86CD-0D4A6B5ABBD8]@0xffffff7fc7946000->0xffffff7fc79aafff
            dependency: com.apple.iokit.IOHIDFamily(2.0.0)[C365D2A4-769B-3399-9F8D-31DDAA238589]@0xffffff8030a0e000->0xffffff8030a6afff
            dependency: com.apple.iokit.IONetworkingFamily(3.4)[EFF68ECC-483B-3BAC-82B9-09C8F0600009]@0xffffff8030ad2000->0xffffff8030ae8fff
            dependency: com.apple.iokit.IOSkywalkFamily(1)[8E95C676-D763-3923-BE43-E8BE08DD3C23]@0xffffff8030e2a000->0xffffff8030e4bfff
            dependency: com.apple.iokit.IOTimeSyncFamily(980.4)[A5FA159E-C468-37EB-92A2-A4B6E527C671]@0xffffff8030fac000->0xffffff8030fc7fff
            dependency: com.apple.kec.Libm(1)[526EF6DE-89A2-334E-A748-F37E33579C6F]@0xffffff803130a000->0xffffff8031317fff

Process name corresponding to current thread: kernel_task
Boot args: keepsyms=1 debug=0x100 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20E241

Kernel version:
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Kernel UUID: 068F99A3-1DB3-31C0-87D5-09942F122BB6
KernelCache slide: 0x000000002e000000
KernelCache base:  0xffffff802e200000
Kernel slide:      0x000000002e010000
Kernel text base:  0xffffff802e210000
__HIB  text base: 0xffffff802e100000
System model name: iMac12,2 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 3268069509353
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000002f8e81f51aa
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x000000129872d1d4 0x0000000000000000

Code:
panic(cpu 6 caller 0xffffff80047c52a6): Kernel trap at 0xffffff80047a5b32, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000372106247, CR4: 0x00000000000626e0
RAX: 0x0000000000000060, RBX: 0x0000000000000000, RCX: 0x0000000000000007, RDX: 0x0000000000000001
RSP: 0xffffffa0d0443b20, RBP: 0xffffffa0d0443b90, RSI: 0x0000600002520000, RDI: 0xffffff86a5fdb300
R8:  0xffffff8021400000, R9:  0x000ffffffffff000, R10: 0xffffff801238ac90, R11: 0xffffff8013a24490
R12: 0xffffff86a5fdb300, R13: 0x000000015fa12000, R14: 0x0000600002520000, R15: 0x0000000000000000
RFL: 0x0000000000010206, RIP: 0xffffff80047a5b32, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000000, Fault CPU: 0x6, PL: 1, VF: 0

Backtrace (CPU 6), Frame : Return Address
0xffffffa0d0443540 : 0xffffff800468e02d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffa0d0443590 : 0xffffff80047d48e3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa0d04435d0 : 0xffffff80047c4eda mach_kernel : _kernel_trap + 0x55a
0xffffffa0d0443620 : 0xffffff8004632a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0d0443640 : 0xffffff800468d84d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa0d0443760 : 0xffffff800468db43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffa0d04437d0 : 0xffffff8004e9d68a mach_kernel : _panic + 0x54
0xffffffa0d0443840 : 0xffffff80047c52a6 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffa0d04439c0 : 0xffffff80047c4f8d mach_kernel : _kernel_trap + 0x60d
0xffffffa0d0443a10 : 0xffffff8004632a2f mach_kernel : _return_from_trap + 0xff
0xffffffa0d0443a30 : 0xffffff80047a5b32 mach_kernel : _phys_attribute_clear + 0x1a2
0xffffffa0d0443b90 : 0xffffff80047523b7 mach_kernel : _vm_page_balance_inactive + 0x107
0xffffffa0d0443be0 : 0xffffff8004764874 mach_kernel : _vm_page_queues_remove + 0x574
0xffffffa0d0443c30 : 0xffffff8004765e17 mach_kernel : _vm_page_free_prepare_queues + 0x57
0xffffffa0d0443c70 : 0xffffff8004748c28 mach_kernel : _vm_io_reprioritize_init + 0x1998
0xffffffa0d0443ce0 : 0xffffff80047477ba mach_kernel : _vm_io_reprioritize_init + 0x52a
0xffffffa0d0443d10 : 0xffffff8004748ad5 mach_kernel : _vm_io_reprioritize_init + 0x1845
0xffffffa0d0443d40 : 0xffffff8004747ce2 mach_kernel : _vm_io_reprioritize_init + 0xa52
0xffffffa0d0443d80 : 0xffffff800473345b mach_kernel : _vm_map_remove + 0xa3b
0xffffffa0d0443ed0 : 0xffffff8004732a93 mach_kernel : _vm_map_remove + 0x73
0xffffffa0d0443f00 : 0xffffff8004c1da43 mach_kernel : _munmap + 0xb3
0xffffffa0d0443f40 : 0xffffff8004d40dae mach_kernel : _unix_syscall64 + 0x2ce
0xffffffa0d0443fa0 : 0xffffff80046331f6 mach_kernel : _hndl_unix_scall64 + 0x16

Process name corresponding to current thread: Microsoft Teams Helper (Renderer
Boot args: keepsyms=1 debug=0x100 chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
20E241

Kernel version:
Darwin Kernel Version 20.4.0: Thu Apr 22 21:46:47 PDT 2021; root:xnu-7195.101.2~1/RELEASE_X86_64
Kernel UUID: 068F99A3-1DB3-31C0-87D5-09942F122BB6
KernelCache slide: 0x0000000004400000
KernelCache base:  0xffffff8004600000
Kernel slide:      0x0000000004410000
Kernel text base:  0xffffff8004610000
__HIB  text base: 0xffffff8004500000
System model name: iMac12,2 (Mac-7BA5B2D9E42DDD94)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 24478866024470
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x000016436e1d30d3
  Sleep   : 0x000013ddcc5bbc53 0x000000004189e2be 0x00000a1cc06cabf9
  Wake    : 0x000013dddc41c68a 0x00000000411ed62e 0x000013dddb33a1e0

experienced the same: stable config on daily load with 11.2.3 then time to time crashes with BS 11.3.1. The Update to 11.4 fixed the issue..

EDIT: it's only POV based on an holistic approach AND way to early to call it a proof as we are still gathering evidence. However if more people are facing the same issue, we could start to infer, based on the mosaic theory, this is a build story.
 
Crash Report spends lots of time with this crash. Patch related?View attachment 1780694
I assume it is the daemon belonging to dosdude1‘s Patch Updater, which made it into BS via migration at least in my case.
In the path given further up in the crash report (/usr…) I renamed patchupdaterd to xxpatchupdaterd, and it is silent now. Will remove it later. Also removed the Patch Updater from system settings.

Thanks for reporting. This way I got motivated to look at a few more crashing items, the oldest installed 2010, which I‘ve now removed.
 
  • Like
Reactions: RogueB and K two
experienced the same: stable config on daily load with 11.2.3 then time to time crashes with BS 11.3.1. The Update to 11.4 fixed the issue..

EDIT: it's only POV based on an holistic approach AND way to early to call it a proof as we are still gathering evidence. However if more people are facing the same issue, we could start to infer, based on the mosaic theory, this is a build story.
On my cMP3,1 running 11.3.1, it was the screen saver causing random reboots. Switching off screensaver solved it.
 
Last edited:
Just updated cMP 3,1 in signature to 11.4 final from 11.3.1 (using OCLP 1.2) and the Apple software update ran fine with one frozen progress bar close to end of install requiring a restart to finish the install. Kudos to OCLP team.
 
  • Like
Reactions: yezza
Did anyone else notice macOS installer became Macintosh HD in this OTA update? Once installed - so far, so good. 🧐

11.4 OTA.jpg
 
Last edited:
I assume it is the daemon belonging to dosdude1‘s Patch Updater, which made it into BS via migration at least in my case.
In the path given further up in the crash report (/usr…) I renamed patchupdaterd to xxpatchupdaterd, and it is silent now. Will remove it later. Also removed the Patch Updater from system settings.

Thanks for reporting. This way I got motivated to look at a few more crashing items, the oldest installed 2010, which I‘ve now removed.
Excellent catch, Thanks! Other previous patch items like apfshelperd can go, too? 🧐
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.