Big Sur 11.7.4 Activity Monitor causes kernel panic?

[steve123]

Since the recent update to 11.7.4 I've had a couple instances where my MP has experienced a kernel panic. The panic in both cases appears to involve Activity Monitor. I've attached the panic info below. I noticed that the list of load kexts appears to be somewhat corrupted though you can still sort of make out which kext's it is referring to.

I do not have any third party kexts installed:

kmutil showloaded | grep -v com.apple

returns an empty list:

Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>

I generally leave Activity Monitor running all the time to keep an eye on things. As I recall I have not encountered this kind of kernel panic in the past. Etrecheck identifies the kernel panics but otherwise there doesn't appear to be anything that stands out. Etrecheck does show some extensions that kmutil does not though none of them look problematic:

    /Applications/Tunnelblick.app
        tap-notarized.kext - net.tunnelblick.tap (Jonathan Bullard, 20141104 (Tunnelblick build 5300))
        tun-notarized.kext - net.tunnelblick.tun (Jonathan Bullard, 20141104 (Tunnelblick build 5300))

    /Applications/VMware Fusion.app
        vmioplug.kext - com.vmware.kext.vmioplug.20.5.0 (VMware, Inc., 20.5.0)
        vmnet.kext - com.vmware.kext.vmnet (VMware, Inc., 12.2.4)
        vmmon.kext - com.vmware.kext.vmx86 (VMware, Inc., 12.2.4)

    /Library/Extensions
        hp_io_printerclassdriver_enabler.kext - com.hp.hpio.hp-io-printerclassdriver-enabler (HP Inc., 19.31.0 - SDK 10.14)
        hp_fax_io.kext - com.hp.kext.hp-fax-io (HP Inc., 5.31.0 - SDK 10.13)
        hp_io_enabler_compound.kext - com.hp.kext.io.enabler.compound (HP Inc., 3.4.0)
        JMicronATA.kext - com.jmicron.JMicronATA (1.1.6)

    /Volumes/L**********2/D*********s/ROMTool.app
        DirectHW.kext - com.doresystems.driver.DirectHW (1.3 - SDK 10.12)

I am wondering of anyone else has experienced an increase in the number of kernel panics recently using 11.7.4?

panic(cpu 2 caller 0xffffff801b69f2fe): "No more room to grow table: 0x0xffffff801c675a60 size:262142, used:262124, requested elem:35"@/System/Volumes/Data/SWE/macOS/BuildRoots/90c5b03f75/Library/Caches/com.apple.xbs/Sources/xnu/xnu-7195.141.49/osfmk/kern/ltable.c:494
Backtrace (CPU 2), Frame : Return Address
0xffffffc13c8db930 : 0xffffff801b68822d mach_kernel : _handle_debugger_trap + 0x3fd
0xffffffc13c8db980 : 0xffffff801b7d0be3 mach_kernel : _kdp_i386_trap + 0x143
0xffffffc13c8db9c0 : 0xffffff801b7c11da mach_kernel : _kernel_trap + 0x55a
0xffffffc13c8dba10 : 0xffffff801b62ca2f mach_kernel : _return_from_trap + 0xff
0xffffffc13c8dba30 : 0xffffff801b687a4d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffc13c8dbb50 : 0xffffff801b687d43 mach_kernel : _panic_trap_to_debugger + 0x273
0xffffffc13c8dbbc0 : 0xffffff801be9bcea mach_kernel : _panic + 0x54
0xffffffc13c8dbc30 : 0xffffff801b69f2fe mach_kernel : _ltable_alloc_elem + 0x3ce
0xffffffc13c8dbc90 : 0xffffff801b6e0e65 mach_kernel : _waitq_prepost_reserve + 0x2c5
0xffffffc13c8dbcf0 : 0xffffff801b6e0cb6 mach_kernel : _waitq_prepost_reserve + 0x116
0xffffffc13c8dbd50 : 0xffffff801b668c26 mach_kernel : _ipc_mqueue_post + 0x36
0xffffffc13c8dbda0 : 0xffffff801b6689c1 mach_kernel : _ipc_mqueue_send + 0x41
0xffffffc13c8dbe00 : 0xffffff801b663f81 mach_kernel : _ipc_kmsg_send + 0x381
0xffffffc13c8dbe60 : 0xffffff801b67b372 mach_kernel : _mach_msg_overwrite_trap + 0x2d2
0xffffffc13c8dbef0 : 0xffffff801b7a52ad mach_kernel : _mach_call_munger64 + 0x29d
0xffffffc13c8dbfa0 : 0xffffff801b62d216 mach_kernel : _hndl_mach_scall64 + 0x16

Process name corresponding to current thread: Activity Monitor
Boot args: keepsyms=1 debug=0x100 -lilubetaall latebloom=100, lb_range=1, lb_debug=1 amfi_get_out_of_my_way=1

Mac OS version:
20G1120

Kernel version:
Darwin Kernel Version 20.6.0: Fri Dec 16 00:35:00 PST 2022; root:xnu-7195.141.49~1/RELEASE_X86_64
Kernel UUID: xxx
KernelCache slide: 0x000000001b400000
KernelCache base:  0xffffff801b600000
Kernel slide:      0x000000001b410000
Kernel text base:  0xffffff801b610000
__HIB  text base: 0xffffff801b500000
System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)
System shutdown begun: NO
Panic diags file available: YES (0x0)
Hibernation exit count: 0

System uptime in nanoseconds: 368078518665597
Last Sleep:           absolute           base_tsc          base_nano
  Uptime  : 0x00014ec3f55ad0e4
  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000
  Wake    : 0x0000000000000000 0x001abb9cf938ee1f 0x0000000000000000
last started kext at 373505370766: @filesystems.smbfs    3.6.2 (addr 0xffffff7fb6f4a000, size 491520)
last stopped kext at 227954855780: >IOPlatformPluginLegacy    1.0.0 (addr 0xffffff7fb65a8000, size 36864)
loaded kexts:
@filesystems.smbfs    3.6.2
>!ATopCaseHIDEventDriver    4050.1
>AudioAUUC    1.70
>!APlatformEnabler    2.7.0d0
>AGPM    122.1
>X86PlatformShim    1.0.0
@filesystems.autofs    3.0
@fileutil    20.036.15
>!AUpstreamUserClient    3.6.8
>!AMCCSControl    1.14
@kext.AMDFramebuffer    4.0.6
@kext.AMDRadeonX4000    4.0.6
@kext.AMDRadeonServiceManager    4.0.6
>!AGraphicsDevicePolicy    6.3.6
@AGDCPluginDisplayMetrics    6.3.6
>pmtelemetry    1
|IOUserEthernet    1.0.1
>usb.!UUserHCI    1
|IO!BSerialManager    8.0.5d7
>!AHDA    283.15
>!A!IMCEReporter    115
@Dont_Steal_Mac_OS_X    7.0.0
>!AHV    1
>!ADiskImages2    1
@kext.AMD7000!C    4.0.6
>!AFWOHCI    5.7.4
>eficheck    1
>!AThunderboltIP    4.0.3
>!ALPC    3.1
>!AMGPUPowerControl    6.3.6
>!A!ISlowAdaptiveClocking    4.0.0
>!UDisplays    380
|IO!BUSBDFU    8.0.5d7
|SCSITaskUserClient    436.140.1
>!ARAID    5.1.0
>!AFileSystemDriver    3.0.1
@filesystems.tmpfs    1
@filesystems.hfs.kext    556.100.12
@BootCache    40
@!AFSCompression.!AFSCompressionTypeZlib    1.0.0
@!AFSCompression.!AFSCompressionTypeDataless    1.0.0d1
@filesystems.apfs    1677.141.3
>AirPort.BrcmNIC    1400.1.1
>!AAHCIPort    346.100.2
|!ABCM5701Ethernet    11.0.0
@private.KextAudit    1.0
>!ARTC    2.0
>!AACPIButtons    6.1
>!AACPIEC    6.1
>!AHPET    1.8
>!ASMBIOS    2.1
>!AAPIC    1.7
>!A!ICPUPowerManagementClient    222.0.0
@!ASystemPolicy    2.0.0
@nke.applicationfirewall    311
|IOKitRegistryCompatibility    1
|EndpointSecurity    1
>!A!ICPUPowerManagement    222.0.0
>!AMultitouchDriver    4440.3.1
>!AInputDeviceSupport    4400.35
>!AHS!BDriver    4050.1
>IO!BHIDDriver    8.0.5d7
@kext.triggers    1.0
>!AHIDKeyboard    224
>!ASMBus!C    1.0.18d1
@kext.AMDRadeonX4030HWLibs    1.0
|IOAccelerator!F2    442.9
@kext.AMDRadeonX4000HWServices    4.0.6
|IOSerial!F    11
>DspFuncLib    283.15
@kext.OSvKernDSPLib    529
|IOAVB!F    940.4
|IOEthernetAVB!C    1.1.0
@kext.AMDSupport    4.0.6
@plugin.IOgPTPPlugin    985.2
|IOFireWire!F    4.8.3
>!UAudio    405.39
@!AGPUWrangler    6.3.6
@!AGraphicsDeviceControl    6.3.6
@plugin.IOAVBDiscoveryPlugin    940.4
>!AHDA!C    283.15
|IOHDA!F    283.15
|IOAudio!F    300.6.1
@vecLib.kext    1.2.0
>!AGraphicsControl    6.3.6
>!ABacklightExpert    1.1.0
|IONDRVSupport    585.2
|IOGraphics!F    585.2
>X86PlatformPlugin    1.0.0
>IOPlatformPlugin!F    6.0.0d8
|IOSlowAdaptiveClocking!F    1.0.0
>!UComposite    900.4.2
|Broadcom!BHost!CUSBTransport    8.0.5d7
|IO!BHost!CUSBTransport    8.0.5d7
|IO!BHost!CTransport    8.0.5d7
>usb.IOUSBHostHIDDevice    1.2
>!AThunderboltDPOutAdapter    8.1.4
>!AThunderboltPCIUpAdapter    4.1.1
>usb.!UHub    1.2
>usb.cdc    5.0.0
>usb.networking    5.0.0
>usb.!UHostCompositeDevice    1.2
|IOAHCIBlock!S    332
>!AThunderboltDPInAdapter    8.1.4
>!AThunderboltDPAdapter!F    8.1.4
>!AThunderboltPCIDownAdapter    4.1.1
>!ABSDKextStarter    3
|IOSurface    290.8.1
@filesystems.hfs.encodings.kext    1
>!AXsanScheme    3
>!AThunderboltNHI    7.2.8
|IOThunderbolt!F    9.3.2
>usb.!UXHCIPCI    1.2
>usb.!UXHCI    1.2
|IONVMe!F    2.1.0
|IO80211!F    1200.12.2b1
|IOSkywalk!F    1
>corecapture    1.0.4
|IOAHCI!F    294.100.1
>usb.!UEHCIPCI    1.2
>usb.!UEHCI    1.2
>mDNSOffloadUserClient    1.0.1b8
>usb.!UHostPacketFilter    1.0
|IOUSB!F    900.4.2
>!AEFINVRAM    2.1
>!AEFIRuntime    2.1
|IOSMBus!F    1.1
|IOHID!F    2.0.0
$!AImage4    3.0.0
|IOTimeSync!F    985.2
|IONetworking!F    3.4
>DiskImages    493.0.0
|IO!B!F    8.0.5d7
|IOReport!F    47
|IO!BPacketLogger    8.0.5d7
$quarantine    4
$sandbox    300.0
@kext.!AMatch    1.0.0d1
|CoreAnalytics!F    1
>!ASSE    1.0
>!AKeyStore    2
>!UTDM    511.141.1
|IOUSBMass!SDriver    184.140.2
|IOSCSIBlockCommandsDevice    436.140.1
|IO!S!F    2.1
|IOSCSIArchitectureModel!F    436.140.1
>!AMobileFileIntegrity    1.0.5
@kext.CoreTrust    1
>!AFDEKeyStore    28.30
>!AEffaceable!S    1.0
>!ACredentialManager    1.0
>KernelRelayHost    1
|IOUSBHost!F    1.2
>!UHostMergeProperties    1.2
>usb.!UCommon    1.0
>!ABusPower!C    1.0
>!ASEPManager    1.0.1
>IOSlaveProcessor    1
>!AACPIPlatform    6.1
>!ASMC    3.1.9
|IOPCI!F    2.9
|IOACPI!F    1.4
>watchdog    1
@kec.pthread    1
@kec.corecrypto    11.1
@kec.Libm    1

 

[bogdanw]

The "last started kext at 373505370766: @filesystems.smbfs " might suggest a hard disk problem. Have you tried running First Aid?
“Repair volumes, then containers, then disks”
https://support.apple.com/HT210898
https://support.apple.com/en-us/HT210898

 

[Patrice Brousseau]

This thing looks also suspect, for me at least:
/Volumes/L**********2/D*********s/ROMTool.app
DirectHW.kext - com.doresystems.driver.DirectHW (1.3 - SDK 10.12)

 

[arw]

"@filesystems.smbfs" is related to mounted network shares via SMB.
With Big Sur I had constant KPs when network shares were mounted via SMB from my Windows 10 "server".
Switching to AFP solved it completely for me. Though a pricy solution (Acronis Access Connect).
YMMV, but as a test you could pause using SMB / mounting shares.

EDIT: In my case it was a Mac Pro 6,1. Assuming yours is a MP5,1, any particular reason you're spoofing a 6,1 and are using an apparently quite old version of Open Core (your boot-args still include 'latebloom')? I'd update to a more recent Martin Lo package.

 

[steve123]

With Big Sur I had constant KPs when network shares were mounted via SMB from my Windows 10 "server".

I had a lot of problems with earlier versions of Big Sur but things seemed to be stable for a while. You could be right though, might be some sort of regression. I will disconnect the shares and see how things work.

In my case it was a Mac Pro 6,1. Assuming yours is a MP5,1, any particular reason you're spoofing a 6,1 and are using an apparently quite old version of Open Core (your boot-args still include 'latebloom')?

My machine is a MP 6,1. I am not running OCLP yet but was planning to upgrade to Ventura at some point since I have had issues with Monterey which is installed on another volume.

 

[steve123]

Volumes/L**********2/D*********s/ROMTool.app

Etrecheck picked this up on an external volume ... I use it to download and backup the SMC ROM when I use OpenCore.

 

[steve123]

Have you tried running First Aid?

Good suggestion, I have not tried that yet.

 

[arw]

My machine is a MP 6,1. I am not running OCLP (...)

I was asking because of your boot-args. The 6,1 never suffered from the 11.3+ race condition hence Latebloom was never necessary:

Boot args: keepsyms=1 debug=0x100 -lilubetaall latebloom=100, lb_range=1, lb_debug=1 amfi_get_out_of_my_way=1

 

[steve123]

I was asking because of your boot-args.

Ahh, I vaguely recall something about setting that years ago for some reason. It might have been when I was experiencing kernel panics when waking from sleep but I do not recall exactly why I set that. If I might ask, what are the standard (default) boot args? Should I set them back to default?

 

[arw]

Ahh, I vaguely recall something about setting that years ago for some reason. It might have been when I was experiencing kernel panics when waking from sleep but I do not recall exactly why I set that. If I might ask, what are the standard (default) boot args? Should I set them back to default?

If you perform a PRAM reset, they get erased. I see no reason for any of these entries on a 6,1.
Shutdown. Press power-on and immediately press and hold cmd+opt+p+r until you hear a second chime.

Reset NVRAM on your Mac - Apple Support

If one or more settings stored in NVRAM don't work as expected on an Intel-based Mac, resetting NVRAM might help.

support.apple.com

EDIT: In regards to issues waking from sleep, check the RTC battery voltage:

https://forums.macrumors.com/threads/help-me-understand-these-kernel-panics.2380620/post-31962909

 

[steve123]

If you perform a PRAM reset, they get erased. I see no reason for any of these entries on a 6,1.

Thank you. I will reset those settings.

I had a look at this thread:

https://forums.macrumors.com/threads/surplus-the-big-sur-monterey-fix-youve-been-waiting-for.2313858/?post=30356918#post-30356918

Now I am not sure why those settings are set the way they are ... I did not have to run OCLP to install Big Sur or Monterey on the MP 6,1. I downloaded OCLP to install on a USB drive for installation on another computer but I never installed it on the MP 6,1. I vaguely recall messing around with some settings trying to fix the wake from sleep issue but not sure now if it was the boot args.

 

[steve123]

Cleanup up the boot-args (empty). Ran disk utility First Aid to check the disk. No errors reported but there were "orphan" warnings. Not sure if these are normal.

I'll let it run for a while and see if I experience the kernel panic again. The last time it took a week or more to crash.

I've been noticing some lag lately too. From time to time it seems like an app will pause with a beach ball for several seconds. I have been wondering if the lag has something to do my Samsung 980 PRO SSD. I upgraded the SSD 18 months ago. Prior to the recent kernel panics, I have not noticed anything odd since the upgrade except a persistent wake from sleep kernel panic for which I disabled sleep. Recently, someone in another thread mentioned that the 980 PRO has some PCIe Gen 2 compatibility issues as other problems with power states. So, now I am wondering if I'm having problems with the blade and that is the source of the wake from sleep panics, the lag and the recent panics?

 

[GMShadow]

Cleanup up the boot-args (empty). Ran disk utility First Aid to check the disk. No errors reported but there were "orphan" warnings. Not sure if these are normal.

I'll let it run for a while and see if I experience the kernel panic again. The last time it took a week or more to crash.

I've been noticing some lag lately too. From time to time it seems like an app will pause with a beach ball for several seconds. I have been wondering if the lag has something to do my Samsung 980 PRO SSD. I upgraded the SSD 18 months ago. Prior to the recent kernel panics, I have not noticed anything odd since the upgrade except a persistent wake from sleep kernel panic for which I disabled sleep. Recently, someone in another thread mentioned that the 980 PRO has some PCIe Gen 2 compatibility issues as other problems with power states. So, now I am wondering if I'm having problems with the blade and that is the source of the wake from sleep panics, the lag and the recent panics?

The 980 Pro has some issues in the 2TB capacity in particular - that could be some of the issue. https://www.tomshardware.com/news/samsung-980-pro-ssd-failures-firmware-update

 

[arw]

https://forums.macrumors.com/threads/nvme-with-st-ngff2013-c-vega-internal-gpu-mac-pro-2013-6-1.2085886/post-32028878

While 980 PRO "works" fine if you have a PCIe v3.0/v4.0 switched card or a MacPro7,1, when you install it on a MacPro5,1 or MacPro6,1 with just a dumb adapter, it fails frequently when you wake from sleep or do warm reboots

 

[steve123]

The 980 Pro has some issues in the 2TB capacity in particular - that could be some of the issue.

Apologies, I should have included that I am using a 1TB blade and I applied the firmware update. Firmware revision is 5B2QGXA7

However, now that you mention this, the firmware update is one of the things that has changed in the last several weeks ... I do not recall exactly the day I did the update but sometime close the the point in time this issue came out. So, it could be some artifact of the new firmware that is causing the lag.

 

[steve123]

The 980 PRO is known for wake from sleep problems in MacPro5,1 and 6,1 when using a dumb adapter.

Yeah, tsialex was the guy that pointed those problems out to me. I've search around a bit but haven't been able to nail down some more details what is causing the problem. I do not seem to have a problem with PCIe configuration. The 980 PRO blade has a link speed of 5 GT/s and a link width of 4 when I inspect it in System Info.

I think Alex mentioned TRIM issues as well. I found a post on Reddit that also mentioned the TRIM issue which indicated the problem appeared as very long boot times with Monterey. I do not recall experiencing the long boot times when I have booted into Monterey instead of Big Sur but I only use Big Sur day to day for now. I'll probably skip Monterey and jump to Ventura and use OCLP.

 

[Patrice Brousseau]

Yeah, tsialex was the guy that pointed those problems out to me. I've search around a bit but haven't been able to nail down some more details what is causing the problem. I do not seem to have a problem with PCIe configuration. The 980 PRO blade has a link speed of 5 GT/s and a link width of 4 when I inspect it in System Info.

I think Alex mentioned TRIM issues as well. I found a post on Reddit that also mentioned the TRIM issue which indicated the problem appeared as very long boot times with Monterey. I do not recall experiencing the long boot times when I have booted into Monterey instead of Big Sur but I only use Big Sur day to day for now. I'll probably skip Monterey and jump to Ventura and use OCLP.

Yes, Samsung blades are no-go starting with Monterey. TRIM is broken as it induces long boot delays… The NVMe’s to get are WD if you plan to go to Monterey or Ventura.