In macOS, the system is limited to running no more than 1064 processes (or 2088 starting with Catalina) systemwide, and individual users are limited to 709 (or 1392 in Catalina). Why is there a limit? Why is it this size? Why not a round number like 2500 or a binary round number like 1024? **Update**: The limit actually varies in size depending on the version of OS X/macOS and the amount of memory installed in the computer. 1064 was a common limit prior to Catalina and then 2088 became common, but these are not the only limit values a Mac might have.

So basically kernel task has been high when my Macbook Pro 2019 (16 inch model) lags too much. I feel I can’t use it and this happens at random. I saw some people saying this might be caused by the charger but no even without the charger connected. And the weird this is I'm not even doing anything resource hungry, just mostly reading pdfs and watching Youtube videos. Even whilst writing this the lag is killing me.

When booting opensuse via rEFInd, the kernel options are wrong (the root device name is incorrect). Where do the kernel arguments that rEFInd is using come from, and how do I modify them? The line I'm looking for is of the form ro root=/dev/disk/by-id/ata-APPLE_SSD_SM768E_S119NYAC612 initrd=boot\initrd-3.7.xxx-default The root argument should be ata-APPLE_SSD_SM768E_S119NYAC612130-part7 as that is where the SUSE root partition is. If I edit the boot options from the rEFInd menu (higlight the SUSE entry, hit F2, hit F2 again on the default entry) and modify the options to include the 130-part7 suffix, everything works fine. If not, Linux asks me: > Could not find /dev/disk/by-id/ata-APPLE_SSD_SM768E_S119NYAC612. > Want me to fall back to > /dev/disk/by-id/ata-APPLE_SSD_SM768E_S119NYAC612130-part7? (Y/n) I'd happily hit "Y" here and move on but, unfortunately, the keyboard doesn't work at this stage in the boot process. If I attach a USB keyboard, it works, but I really don't want to carry one around with me. (Perhaps there is a market for a one-key USB keyboard that can be programmed for these things. Dear God...) So, I am left changing the options via the rEFInd menu every time I boot Linux. I'd thought about adding a symlink directing ...612 to ...612130-part7, but the links in /dev/disk/by-id/ are stored in tempfs (ie, not persistent). Also, that is a crappy solution. Help?!

From man open: --arch ARCH Launch with the given cpu architecture type and subtype; ARCH should be one of any, arm, arm64, arm64e, arm64_32, x86_64, x86_64h, i386. Two integers matching the values for cpu_type_t and cpu_subtype_t can be specified as integers separated by a '/' character, like "12/13" for CPU_TYPE_ARM/CPU_SUBTYPE_ARM_V8. The 12/13 suggests that there may exist 1→11 values for cpu_type_t and cpu_subtype_t.  **Where would I find a list, and what other uses do they have?** Related: https://apple.stackexchange.com/questions/477268/open-arch-arch-works-on-the-wrong-processor

OS X lacks the "Linux-friendly" free or /proc/meminfo. What would be the most reliable and backwards-compatible way of extracting this info: - Current free memory, in bytes Going back as far as possible in terms of OS versions, without requiring extensions like ports, brew, etc.

After choosing the guest option the system crashes and after the system restarts it gives the following logs to report, yes I've tried the Registered User option but that just not working. Panic(cpu 2 caller 0xfffffe0018bf4840): kfree: addr 0xfffffe4454684000, size 444 (offs:0) not found in any zone @kalloc.c:2668 Debugger message: panic Memory ID: 0xff OS release type: User OS version: 23D60 Kernel version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:33:31 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T8112 Fileset Kernelcache UUID: FEC775B3A6937256DD0F4754955B7AAF Kernel UUID: C7428EB0-BE7C-3056-8267-A75FED2CC4A4 Boot session UUID: 5DAC0FF5-04DA-4CC5-96FD-0144FD035DAF iBoot version: iBoot-10151.81.1 secure boot?: YES roots installed: 0 Paniclog version: 14 KernelCache slide: 0x000000000fe48000 KernelCache base: 0xfffffe0016e4c000 Kernel slide: 0x000000000fe50000 Kernel text base: 0xfffffe0016e54000 Kernel text exec slide: 0x00000000113a4000 Kernel text exec base: 0xfffffe00183a8000 mach_absolute_time: 0x2c63da26f Epoch Time: sec usec Boot : 0x65d33f96 0x00094859 Sleep : 0x00000000 0x00000000 Wake : 0x00000000 0x00000000 Calendar: 0x65d34181 0x000b9a0b Zone info: Zone map: 0xfffffe1a3a4ac000 - 0xfffffe3a3a4ac000 . VM : 0xfffffe1a3a4ac000 - 0xfffffe1f07178000 . RO : 0xfffffe1f07178000 - 0xfffffe20a0b10000 . GEN0 : 0xfffffe20a0b10000 - 0xfffffe256d7dc000 . GEN1 : 0xfffffe256d7dc000 - 0xfffffe2a3a4a8000 . GEN2 : 0xfffffe2a3a4a8000 - 0xfffffe2f07174000 . GEN3 : 0xfffffe2f07174000 - 0xfffffe33d3e40000 . DATA : 0xfffffe33d3e40000 - 0xfffffe3a3a4ac000 Metadata: 0xfffffe101061c000 - 0xfffffe101861c000 Bitmaps : 0xfffffe101861c000 - 0xfffffe101b390000 Extra : 0 - 0 CORE 0 recently retired instr at 0xfffffe001854c5a0 CORE 1 recently retired instr at 0xfffffe001854c5a0 CORE 2 recently retired instr at 0xfffffe001854ae00 CORE 3 recently retired instr at 0xfffffe001854c5a0 CORE 4 recently retired instr at 0xfffffe001854c5a0 CORE 5 recently retired instr at 0xfffffe001854c5a0 CORE 6 recently retired instr at 0xfffffe001854c5a0 CORE 7 recently retired instr at 0xfffffe001854c5a0 TPIDRx_ELy = {1: 0xfffffe2f067cb000 0: 0x0000000000000002 0ro: 0x000000016fbe70e0 } 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=0xfffffe0018473f34, LR=0xfffffe001840f648, FP=0xfffffe8e1bebb500 CORE 1: PC=0xfffffe0018542864, LR=0xfffffe0018541f64, FP=0xfffffe8e1c72ff10 CORE 2 is the one that panicked. Check the full backtrace for details. CORE 3: PC=0x00000001828f140c, LR=0x000000019b95cbe8, FP=0x000000016b8010e0 CORE 4: PC=0xfffffe001854732c, LR=0xfffffe0018547328, FP=0xfffffe8e1b4a7e80 CORE 5: PC=0xfffffe00184379c8, LR=0xfffffe00184379c8, FP=0xfffffe8e1c1f7ef0 CORE 6: PC=0xfffffe00184379cc, LR=0xfffffe00184379c8, FP=0xfffffe8e1c457ef0 CORE 7: PC=0xfffffe00184379cc, LR=0xfffffe00184379c8, FP=0xfffffe8e1c2b7ef0 Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space Panicked task 0xfffffe33d0ae1de8: 1123 pages, 7 threads: pid 1002: NetAuthSysAgent Panicked thread: 0xfffffe2f067cb000, backtrace: 0xfffffe8e1c4fee70, tid: 9568 lr: 0xfffffe00183fe9a8 fp: 0xfffffe8e1c4fef00 lr: 0xfffffe001854382c fp: 0xfffffe8e1c4fef70 lr: 0xfffffe0018541c98 fp: 0xfffffe8e1c4ff060 lr: 0xfffffe00183af8cc fp: 0xfffffe8e1c4ff070 lr: 0xfffffe00183fe29c fp: 0xfffffe8e1c4ff420 lr: 0xfffffe0018bf1cc4 fp: 0xfffffe8e1c4ff440 lr: 0xfffffe0018bf4840 fp: 0xfffffe8e1c4ff4c0 lr: 0xfffffe001840fbe8 fp: 0xfffffe8e1c4ff500 lr: 0xfffffe001b644b30 fp: 0xfffffe8e1c4ff9c0 lr: 0xfffffe001861ae98 fp: 0xfffffe8e1c4ffa20 lr: 0xfffffe001860cd30 fp: 0xfffffe8e1c4ffc40 lr: 0xfffffe00188b2520 fp: 0xfffffe8e1c4ffc80 lr: 0xfffffe0018918944 fp: 0xfffffe8e1c4ffd90 lr: 0xfffffe0018a0ece0 fp: 0xfffffe8e1c4ffe20 lr: 0xfffffe0018541dc8 fp: 0xfffffe8e1c4fff10 lr: 0xfffffe00183af8cc fp: 0xfffffe8e1c4fff20 Kernel Extensions in backtrace: com.apple.filesystems.smbfs(5.1)[C22A6A50-F264-363E-A2FA-98362C75B80C]@0xfffffe001b609ed0->0xfffffe001b6756d3 dependency: com.apple.kec.corecrypto(14.0)[1C9CBFB2-1EAF-3030-83D7-66135A0EDEC1]@0xfffffe001b4f7b00->0xfffffe001b54880b dependency: com.apple.kext.triggers(1.0)[2A33A36D-DCAA-3A3B-9241-C507139565FE]@0xfffffe001b67f620->0xfffffe001b681f2f last started kext at 10893536652: com.apple.filesystems.smbfs 5.1 (addr 0xfffffe0017898c70, size 82089) loaded kexts: com.apple.filesystems.smbfs 5.1 com.apple.filesystems.autofs 3.0 com.apple.driver.AppleBiometricServices 1 com.apple.driver.CoreKDL 1 com.apple.driver.BCMWLANFirmware4388.Hashstore 1 com.apple.driver.BCMWLANFirmware4387.Hashstore 1 com.apple.driver.BCMWLANFirmware4378.Hashstore 1 com.apple.iokit.AppleBCM5701Ethernet 11.0.0 com.apple.driver.DiskImages.ReadWriteDiskImage 493.0.0 com.apple.driver.DiskImages.UDIFDiskImage 493.0.0 com.apple.driver.DiskImages.RAMBackingStore 493.0.0 com.apple.driver.DiskImages.FileBackingStore 493.0.0 com.apple.driver.SEPHibernation 1 com.apple.driver.AppleThunderboltIP 4.0.3 com.apple.driver.AppleUSBDeviceNCM 5.0.0 com.apple.driver.AppleSmartBatteryManager 161.0.0 com.apple.driver.AppleFileSystemDriver 3.0.1 com.apple.nke.l2tp 1.9 com.apple.filesystems.tmpfs 1 com.apple.filesystems.nfs 1 com.apple.filesystems.lifs 1 com.apple.filesystems.apfs 2235.80.4 com.apple.IOTextEncryptionFamily 1.0.0 com.apple.filesystems.hfs.kext 650.0.2 com.apple.security.BootPolicy 1 com.apple.BootCache 40 com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0 com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1 com.apple.driver.usb.AppleSynopsysUSB40XHCI 1 com.apple.driver.AppleSmartIO2 1 com.apple.driver.AppleSN012776Amp 700.46 com.apple.driver.ApplePMP 1 com.apple.AppleEmbeddedSimpleSPINORFlasher 1 com.apple.driver.AppleAOPVoiceTrigger 300.7 com.apple.driver.AppleSPIMC 1 com.apple.driver.AudioDMAController-T8112 300.15 com.apple.driver.AppleSamsungSerial 1.0.0d1 com.apple.driver.AppleSerialShim 1 com.apple.driver.AppleCS42L84Audio 700.46 com.apple.driver.AppleTypeCRetimer 1.0.0 com.apple.driver.AppleMobileDispH14G-DCP 140.0 com.apple.driver.AppleT8020SOCTuner 1 com.apple.driver.AppleT8112CLPC 1 com.apple.driver.ApplePMPFirmware 1 com.apple.driver.AppleInterruptControllerV2 1.0.0d1 com.apple.driver.AppleProResHW 326.11.0 com.apple.AGXG14G 276.62 com.apple.driver.AppleS8000DWI 1.0.0d1 com.apple.driver.AppleS5L8920XPWM 1.0.0d1 com.apple.driver.AppleS8000AES 1 com.apple.driver.AppleT8112PMGR 1 com.apple.driver.AppleS5L8960XNCO 1 com.apple.driver.AppleAVE2 703.54.1 com.apple.driver.AppleJPEGDriver 6.2.2 com.apple.driver.AppleAVD 737.2 com.apple.driver.AppleBluetoothModule 1 com.apple.driver.AppleEventLogHandler 1 com.apple.driver.AppleBCMWLANBusInterfacePCIe 1 com.apple.driver.AppleT8110DART 1 com.apple.driver.AppleS5L8940XI2C 1.0.0d2 com.apple.driver.AppleT8110 1 com.apple.driver.AppleM68Buttons 1.0.0d1 com.apple.iokit.IOUserEthernet 1.0.1 com.apple.driver.usb.AppleUSBUserHCI 1 com.apple.iokit.IOKitRegistryCompatibility 1 com.apple.iokit.EndpointSecurity 1 com.apple.driver.AppleDiskImages2 273 com.apple.AppleSystemPolicy 2.0.0 com.apple.nke.applicationfirewall 404 com.apple.kec.InvalidateHmac 1 com.apple.kec.AppleEncryptedArchive 1 com.apple.driver.driverkit.serial 6.0.0 com.apple.plugin.IOAVBDiscoveryPlugin 1220.1 com.apple.driver.AppleHIDKeyboard 7400.2 com.apple.driver.usb.IOUSBHostHIDDevice 1.2 com.apple.driver.usb.cdc 5.0.0 com.apple.driver.AppleUSBAudio 610.3 com.apple.iokit.IOAudioFamily 500.4 com.apple.vecLib.kext 1.2.0 com.apple.driver.AppleMesaSEPDriver 100.99 com.apple.iokit.IOBiometricFamily 1 com.apple.driver.AppleConvergedIPCOLYBTControl 1 com.apple.driver.AppleConvergedPCI 1 com.apple.driver.AppleBluetoothDebug 1 com.apple.driver.usb.AppleEmbeddedUSBXHCIPCI 1 com.apple.driver.usb.AppleUSBXHCIPCI 1.2 com.apple.driver.DiskImages.KernelBacked 493.0.0 com.apple.driver.AppleXsanScheme 3 com.apple.driver.AppleSEPHDCPManager 1.0.1 com.apple.driver.AppleTrustedAccessory 1 com.apple.iokit.AppleSEPGenericTransfer 1 com.apple.driver.AppleBTM 1.0.1 com.apple.driver.usb.networking 5.0.0 com.apple.driver.AppleThunderboltPCIDownAdapter 4.1.1 com.apple.driver.AppleThunderboltUSBDownAdapter 1.0.4 com.apple.driver.AppleThunderboltDPInAdapter 8.5.1 com.apple.driver.AppleThunderboltDPAdapterFamily 8.5.1 com.apple.nke.ppp 1.9 com.apple.driver.AppleDCPDPTXProxy 1.0.0 com.apple.driver.DCPDPFamilyProxy 1 com.apple.driver.AppleBSDKextStarter 3 com.apple.kext.triggers 1.0 com.apple.driver.IOHIDPowerSource 1 com.apple.driver.AppleCallbackPowerSource 1 com.apple.filesystems.hfs.encodings.kext 1 com.apple.driver.AppleSyntheticGameController 11.3.1 com.apple.driver.AppleUSBXDCIARM 1.0 com.apple.driver.AppleUSBXDCI 1.0 com.apple.iokit.IOUSBDeviceFamily 2.0.0 com.apple.driver.usb.AppleSynopsysUSBXHCI 1 com.apple.driver.usb.AppleUSBXHCI 1.2 com.apple.driver.AppleEmbeddedUSBHost 1 com.apple.driver.usb.AppleUSBHub 1.2 com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2 com.apple.driver.AppleSPMIPMU 1.0.1 com.apple.driver.AppleDialogPMU 1.0.1 com.apple.driver.AppleSART 1 com.apple.driver.AppleStockholmControl 1.0.0 com.apple.driver.AppleSPMI 1.0.1 com.apple.iokit.IONVMeFamily 2.1.0 com.apple.driver.AppleDiagnosticDataAccessReadOnly 1.0.0 com.apple.driver.AppleNANDConfigAccess 1.0.0 com.apple.driver.AppleAOPAudio 300.14 com.apple.driver.AppleHPM 3.4.4 com.apple.driver.AppleCSEmbeddedAudio 700.46 com.apple.driver.AppleEmbeddedAudio 700.46 com.apple.iokit.AppleARMIISAudio 300.11 com.apple.driver.AppleT8112TypeCPhy 1 com.apple.driver.AppleT8103TypeCPhy 1 com.apple.iokit.IOMobileGraphicsFamily-DCP 343.0.0 com.apple.driver.AppleDCP 1 com.apple.iokit.IOMobileGraphicsFamily 343.0.0 com.apple.driver.AppleM2ScalerCSCDriver 265.0.0 com.apple.driver.ApplePassthroughPPM 3.0 com.apple.driver.DCPAVFamilyProxy 1 com.apple.driver.AppleFirmwareKit 1 com.apple.AGXFirmwareKextG14GRTBuddy 1 com.apple.AGXFirmwareKextRTBuddy64 276.62 com.apple.driver.AppleSPU 1 com.apple.driver.AppleH11ANEInterface 7.300.0 com.apple.driver.AppleDisplayCrossbar 1.0.0 com.apple.iokit.IODisplayPortFamily 1.0.0 com.apple.driver.AppleTypeCPhy 1 com.apple.iokit.IOGPUFamily 93.10.1 com.apple.driver.AppleARMWatchdogTimer 1 com.apple.driver.ApplePMGR 1 com.apple.driver.AppleThunderboltNHI 7.2.81 com.apple.driver.AppleT8112PCIe 1 com.apple.driver.AppleMCA2-T8112 800.11 com.apple.driver.AppleEmbeddedAudioLibs 300.1 com.apple.driver.AppleFirmwareUpdateKext 1 com.apple.driver.AppleT8103PCIeC 1 com.apple.iokit.IOThunderboltFamily 9.3.3 com.apple.iokit.IOPortFamily 1.0 com.apple.driver.ApplePIODMA 1 com.apple.driver.AppleMultiFunctionManager 1 com.apple.driver.AppleBluetoothDebugService 1 com.apple.driver.AppleBCMWLANCore 1.0.0 com.apple.iokit.IO80211Family 1200.13.0 com.apple.driver.IOImageLoader 1.0.0 com.apple.driver.AppleOLYHAL 1 com.apple.driver.corecapture 1.0.4 com.apple.driver.AppleEmbeddedPCIE 1 com.apple.iokit.IOAVBFamily 1220.1 com.apple.plugin.IOgPTPPlugin 1230.2 com.apple.driver.AppleGPIOICController 1.0.2 com.apple.driver.AppleFireStormErrorHandler 1 com.apple.driver.AppleMobileApNonce 1 com.apple.driver.usb.AppleUSBHostPacketFilter 1.0 com.apple.iokit.IOTimeSyncFamily 1230.2 com.apple.driver.DiskImages 493.0.0 com.apple.iokit.IOGraphicsFamily 598 com.apple.iokit.IOBluetoothFamily 9.0.0 com.apple.driver.AppleSSE 1.0 com.apple.driver.AppleSEPKeyStore 2 com.apple.driver.AppleUSBTDM 556 com.apple.iokit.IOUSBMassStorageDriver 243 com.apple.iokit.IOPCIFamily 2.9 com.apple.iokit.IOSCSIBlockCommandsDevice 492 com.apple.iokit.IOSCSIArchitectureModelFamily 492 com.apple.driver.AppleRSMChannel 1 com.apple.iokit.IORSMFamily 1 com.apple.driver.AppleLockdownMode 1 com.apple.driver.AppleIPAppender 1.0 com.apple.driver.AppleFDEKeyStore 28.30 com.apple.driver.AppleEffaceableStorage 1.0 com.apple.driver.AppleCredentialManager 1.0 com.apple.driver.KernelRelayHost 1 com.apple.iokit.IOUSBHostFamily 1.2 com.apple.driver.AppleUSBHostMergeProperties 1.2 com.apple.driver.usb.AppleUSBCommon 1.0 com.apple.driver.AppleSMC 3.1.9 com.apple.driver.RTBuddy 1.0.0 com.apple.driver.AppleEmbeddedTempSensor 1.0.0 com.apple.driver.AppleARMPMU 1.0 com.apple.iokit.IOAccessoryManager 1.0.0 com.apple.driver.AppleOnboardSerial 1.0 com.apple.iokit.IOSkywalkFamily 1.0 com.apple.driver.mDNSOffloadUserClient 1.0.1b8 com.apple.iokit.IONetworkingFamily 3.4 com.apple.iokit.IOSerialFamily 11 com.apple.driver.AppleSEPManager 1.0.1 com.apple.driver.IODARTFamily 1 com.apple.driver.AppleA7IOP 1.0.2 com.apple.driver.IOSlaveProcessor 1 com.apple.driver.AppleBiometricSensor 2 com.apple.iokit.IOHIDFamily 2.0.0 com.apple.AUC 1.0 com.apple.iokit.IOSurface 352.0.3 com.apple.iokit.IOAVFamily 1.0.0 com.apple.iokit.IOHDCPFamily 1.0.0 com.apple.iokit.IOCECFamily 1 com.apple.iokit.IOAudio2Family 1.0 com.apple.driver.AppleIISController 300.1 com.apple.driver.AppleAudioClockLibs 300.1 com.apple.driver.FairPlayIOKit 71.3.0 com.apple.driver.AppleARMPlatform 1.0.2 com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0 com.apple.iokit.IOReportFamily 47 com.apple.security.quarantine 4 com.apple.security.sandbox 300.0 com.apple.iokit.IOStorageFamily 2.1 com.apple.kext.AppleMatch 1.0.0d1 com.apple.driver.AppleMobileFileIntegrity 1.0.5 com.apple.iokit.CoreAnalyticsFamily 1 com.apple.security.AppleImage4 5.0.0 com.apple.kext.CoreTrust 1 com.apple.iokit.IOCryptoAcceleratorFamily 1.0.1 com.apple.kec.pthread 1 com.apple.kec.Libm 1 com.apple.kec.Compression 1.0 com.apple.kec.corecrypto 14.0 ** Stackshot Succeeded ** Bytes Traced 355899 (Uncompressed 882608) **

Occasionally my machine will have a kernel_task instance max out the CPU: This can last from minutes to sometimes hours. The machine is effectively unusable in this state. Restarting doesn't help; a new kernel_task pops up again until it finishes whatever it's doing. How can I find out what this process is doing?

I have a 2020 MacBook Pro 16", the last of the Intel based Macs. Just in the last couple of weeks it has been slowing down due the kernel_task process going up to 1000% CPU usage. I have done a SMC and NVRAM reset to no avail. I have followed the advice in this thread and have nothing plugged in on the left side and also disabled Turbo Boost. The lid is closed with one external monitor and I have both left and right fans running at full RPM. The usage does not seem limited to any one application (eg browser etc), it happens without or with various apps open. Temps are fine as per the image below? 60c. The one thing I can say is that it generally starts occurring after about 7-8 hours of work time (regardless of when I start work). Work is just browsers, nothing taxing. Any ideas on what I can do next? Have just about had it with my laptop slowing to a crawl every single afternoon.

I have had a week-long compression process run on an MacBook. When it hit 95%, the speed suddenly dropped to just 5% CPU usage. Tracing the problem, I found that kernel_task is taking up 6.87GB, leaving roughly 1GB to the other processes. This leads to thrashing on the compression process. Tracing the issue further, I found that a bash process is using nearly 1TB (!) of kernel memory. This is slightly more than the free space on my hard drive! No clue what it's doing, no other process seems to have this as its parent. I closed all bash windows, but the process stayed. Ran kill on it, no difference. I finally killed it using kill -9. In https://apple.stackexchange.com/questions/205332/why-does-leaked-memory-appear-malloced-to-kernel-task-and-why-cant-os-x-theref , killing Preview resolved this issue, but in my case, the memory usage of kernel_task remained. Maybe due to how it was killed. Tried running sync and purge, no difference. Garbage collect does not apply to kernel_task. Any other things I could do to reclaim this memory? Theoretically, if I could get the inactive memory at least moved to swap, then the compression process would have enough to quickly complete what it's doing. No kernel extensions seem to be using an abnormal amount of memory, no third-party extensions are installed.

I have a very annoying bug on my iMac 2019 (27", Retina 5K, i9, 8cores, Monterey, Radeon Pro Vega 8 Gb, 64GB Ram). It's likely caused by a hardware problem but also triggers a software bug I would try to mitigate. **The symptom** Sometimes, and currently nearly everyday, my Mac becomes unresponsive, the fan gets stuck to 3600 rpm, and can stay so for hours. **The diagnosis** This can be traced to the Mac trying to cool itself by launching a kernel_task process, which is a known strategy when CPUs are heating, devised to exclude other offending processes. I've installed a some third-party utility and can reproduce the problem: Quite at random (even in the middle of the night when the computer is asleep), a temperature sensor (named AC/DC T2 Sec HeatSink) would go in seconds from a normal room temperature to 70, 80 or even 125°. All other temp sensors show normal values (<40°) and no spikes. Then kernel_task kicks in, usually around 1000 %, making the Mac unresponsive then the fan goes to maximum speed (3600 rpm). After a while, sometimes in few seconds, the sensor usually comes back to normal by itself, and it also does so if I knock physically on the place where it is located (near the plug). I've studied extensively console logs and could not find any specific process that would trigger this behaviour. I'am very inclined to think this is a hardware bug, and this is also Apple opinion, since I've already brought my Mac for repair for this reason twice, they changed the logic board, and it disappeared for a few monthes. **Remedies and workaround** I surely should go back to Apple now a third time, but I'm wondering if I could delay it, especially since they charged me the last time, for what I believe is a design fault. Last time they were not of great help in understanding the problem, telling me I had too much third-party memory and to go back to 8GB Apple. Also I don't really want to upgrade my OS, since it would break some third party software again. For the record the problem was here on Catalina and Big Sur and upgrading the OS brought nothing as far as this bug is concerned (except from third-party obsolescence). Currently, every time this happens, I knock on the Mac to bring the sensor back to normal value if needed, then I suspend activity (using Apple menu), wait for the time for it to happen, between a few seconds and a minute, then I wake up the Mac and all is back to normal. Clearly there is also a software bug in the OS, since there is no process to cut kernel_task and bring back the fan to normal values when all temperatures are reported within normal operation range. I don't know the root cause of the hardware bug. I provide some clues for the reader interest: * Have I damaged the sensor by unplugging live the Mac (this can happen unwillingly when you move the screen, the cord plug being stuck on the wall behind) ? * Is there some accumulated dust that produces a short-circuit and moves when I knock ? I can't clean it, the iMac can't be opened * Is there too many USB devices plugged and does this raise the energy needed, triggering the sensor (there is a loosely correlation with the activation of the USB DAC connected, but is also happen when it is not here) ? I plan to buy a self-powered usb hub, just in case. **Which brings me to the objective of this post and my question :** Could I stop the un-needed cooling process without suspending activity ? There are some utilities that stop the fan but hey don't calm kernel_task, so this is of no use. Trying to kill the kernel_task process seems a bad idea, as it is essential to the system. There are obviously under-the-hood actions that cure the problem when activity suspension is triggered, so I wonder if I could reach the same result without loosing the minutes I currently loose because of the activity suspension. Thanks for your inputs.

My work requires long-running connections to databases that required this sysctl setting in earlier OSX versions. Since it no longer exists, these connections appear to remain open, but they disconnect. The database client awaits the results that never come while the database shows the query as completed. Is there any setting that can replace the functionality that net.inet.tcp.keepidle provided?

While cleaning some software off my computer, I noticed the following extensions listed in System Information → Software → Extensions. For context, I am running an M2 Max MacBook Pro with MacOS Ventura 13.4. I did not ever install applications by "HighPoint Technologies" or "Other World Computing," and I certainly never approved the activation of system software by either of these developers. **Can someone tell me what these pieces of software are, whether they should be on my Mac, and—if not—how I can get rid of them?** > **HighPointIOP:** > > Version: 4.4.5 > Last Modified: 2023-05-12, 18:29 > Bundle ID: com.highpoint-tech.kext.HighPointIOP > Notarized: Yes > Loaded: No > Get Info String: Version: 4.4.5, Copyright (c) 2020 HighPoint Technologies, Inc. > Obtained from: Identified Developer > Kind: Intel > Architectures: x86_64 > 64-Bit (Intel): Yes > Location: /Library/Extensions/HighPointIOP.kext > Kext Version: 4.4.5 > Loadable: Yes > Dependencies: Incomplete > Dependency Errors: > Dependency Resolution Failures: > Indirect dependencies can't be resolved: com.apple.iokit.IOSCSIParallelFamily, com.apple.iokit.IOPCIFamily > Signed by: Developer ID Application: HighPoint Technologies, Inc (DX6G69M9N2), Developer ID Certification Authority, Apple Root CA > > **HighPointRR:** > > Version: 4.22.1 > Last Modified: 2023-05-12, 18:29 > Bundle ID: com.highpoint-tech.kext.HighPointRR > Notarized: Yes > Loaded: No > Get Info String: Version: 4.22.1, Copyright (c) 2020 HighPoint Technologies, Inc. > Obtained from: Identified Developer > Kind: Intel > Architectures: x86_64 > 64-Bit (Intel): Yes > Location: /Library/Extensions/HighPointRR.kext > Kext Version: 4.22.1 > Loadable: Yes > Dependencies: Incomplete > Dependency Errors: > Dependency Resolution Failures: > Indirect dependencies can't be resolved: com.apple.iokit.IOSCSIParallelFamily, com.apple.iokit.IOPCIFamily > Signed by: Developer ID Application: HighPoint Technologies, Inc (DX6G69M9N2), Developer ID Certification Authority, Apple Root CA > > **SoftRAID:** > > Version: 6.3.1 > Last Modified: 2023-02-09, 04:39 > Bundle ID: com.softraid.driver.SoftRAID > Notarized: Yes > Loaded: No > Get Info String: SoftRAID version 6.3.1, Copyright © 2002-22 Other World Computing, Inc. All rights reserved. > Obtained from: Identified Developer > Kind: Intel > Architectures: x86_64 > 64-Bit (Intel): Yes > Location: /Library/Extensions/SoftRAID.kext > Kext Version: 6.3.1 > Loadable: Yes > Dependencies: Incomplete > Dependency Errors: > Dependency Resolution Failures: > Indirect dependencies can't be resolved: com.apple.iokit.IOStorageFamily > Signed by: Developer ID Application: Other World Computing (Q9P8K45M5C), Developer ID Certification Authority, Apple Root CA

The [Darwin Kernel Programming Guide](https://developer.apple.com/library/archive/documentation/Darwin/Conceptual/KernelProgramming/About/About.html) has been last updated on 2013-08-08, and the mention "Documentation archive" is in the title bar. So, my question is : How to access the latest version of the Darwin Kernel Programming Guide?

I am running Venture 13.5 on a M1 MacBook Pro. Because Lockdown mode is on, I am prompted to approve/deny each time a USB device is plugged into my machine. However, I am also randomly being prompted to approve/deny an SD card. During these occurrences, I do not enter any USB device, let alone an SD card. Why is this happening? I've captures logs and timestamps I'll share below. I'm not exactly sure of what to look for and these logs don't tell me too much. Note that some data is redacted for privacy: **At notification popup**

2023-0x-xx xx:xx:15.867963-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortTransportState::setActive(): [Port-SD Card@1: SD] active: YES (transportType: 12 [SD])
2023-0x-xx xx:xx:15.867985-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortTransportState::_updateTRMState(): [Port-SD Card@1: SD] Updating TRM state...
2023-0x-xx xx:xx:15.867992-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortTransportState::calculateAuthorizationState(): [Port-SD Card@1: SD] Calculating authorization state...
2023-0x-xx xx:xx:15.867999-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortTransportState::calculateAuthorizationState_block_invoke(): [Port-SD Card@1: SD] *** RTRR ***
2023-0x-xx xx:xx:15.868029-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortTransportState::handleStateChange(): [Port-SD Card@1: SD] Handling state change...
2023-0x-xx xx:xx:15.868038-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOServiceNotificationManager::sendMessages(): [Port-SD Card@1/SD] Sending 3 message(s)... (m_propertyChanged: YES)
2023-0x-xx xx:xx:15.868091-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) AppleNotificationQueue::processNotifications(): Processing 1 notification(s)...
2023-0x-xx xx:xx:15.868115-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOServiceNotificationManager::handleServiceReregistration(): [Port-SD Card@1/SD] Re-registering service...
2023-0x-xx xx:xx:15.868119-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortTransportState::registerService(): [Port-SD Card@1: SD] Registering service SD@(null)... (transportType: 12, provider: Port-SD Card@1)
2023-0x-xx xx:xx:15.868283-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) AppleNotificationQueue::_handleNotifications(): Handling notifications...
2023-0x-xx xx:xx:15.868361-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPort::_updateConnectionActive_block_invoke(): [Port-SD Card@1] m_connectionActive: YES, m_connectionCount: 7, m_connectionUUID: AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA
2023-0x-xx xx:xx:15.868397-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOServiceNotificationManager::sendMessages(): [Port-SD Card@1] Sending 2 message(s)... (m_propertyChanged: YES)
2023-0x-xx xx:xx:15.869605-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOServiceNotificationManager::sendMessages(): [Port-SD Card@1] Sending 3 message(s)... (m_propertyChanged: YES)
2023-0x-xx xx:xx:15.869607-0400 0xbb       Default     0x0                  0      0    kernel: (IOgPTPPlugin)   IOTimeSyncTimeSyncTimePort(0xaaaaaaaaaaaaaaaa): Other 0xaaaaaaaa
2023-0x-xx xx:xx:15.870997-0400 0xbb       Default     0x0                  0      0    kernel: (IOgPTPPlugin)   IOTimeSyncTimeSyncTimePort(0xaaaaaaaaaaaaaaaa): Other 0xaaaaaaaa
2023-0x-xx xx:xx:15.871095-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOServiceNotificationManager::handleServiceReregistration(): [Port-SD Card@1] Re-registering service...
2023-0x-xx xx:xx:15.871098-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPort::registerService(): [Port-SD Card@1] Registering service Port-SD Card@1...
2023-0x-xx xx:xx:15.871268-0400 0xbb       Default     0x0                  0      0    kernel: (IOgPTPPlugin)   IOTimeSyncTimeSyncTimePort(0xaaaaaaaaaaaaaaaa): Other 0xaaaaaaaa
2023-0x-xx xx:xx:15.871544-0400 0xbb       Default     0x0                  0      0    kernel: (IOgPTPPlugin)   IOTimeSyncTimeSyncTimePort(0xaaaaaaaaaaaaaaaa): Other 0xaaaaaaaa

**At notification close (triggered by me pressing "Don't allow")**

2023-0x-xx xx:xx:24.213640-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortUserClient::setUserAuthorizationStatus(): Setting user authorization status... (target: Port-SD Card@1, newUserAuthorizationStatus: 3 [Ignored])
2023-0x-xx xx:xx:24.213653-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPort::_setUserAuthorizationStatus(): [Port-SD Card@1] userAuthorizationStatus: 3 [Ignored]
2023-0x-xx xx:xx:24.213699-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOServiceNotificationManager::sendMessages(): [Port-SD Card@1] Sending 2 message(s)... (m_propertyChanged: YES)
2023-0x-xx xx:xx:24.213971-0400 0xbbbbbb   Default     0x0                  581    0    loginwindow: (LoginUIKit) messageType: kIOPort_Message_AuthorizationStateChange
2023-0x-xx xx:xx:24.213976-0400 0xbbbbbb   Default     0x0                  581    0    loginwindow: (LoginUIKit) Updating properties... (self.registryEntryID: 1111111111)
2023-0x-xx xx:xx:24.214538-0400 0xaaaaaa   Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortUserClient::clientClose(): Stopping IOPortUserClient... (this: IOPortUserClient@(null), m_provider: Port-SD Card@1)
2023-0x-xx xx:xx:24.215275-0400 0xcc       Default     0x0                  0      0    kernel: (IOAccessoryManager) IOPortUserClient::stop(): Stopping IOPortUserClient... (this: IOPortUserClient@(null), provider: Port-SD Card@1)

**Additional Information** * This has been occurring since Lockdown mode has been on (Ventura 13.2) * This happens randomly, sometimes once a week, sometimes twice a day

My MacBook (2016 with TouchBar) running macOS 10.13 has a 512GB SSD. Looking at the activity monitor after a couple of weeks of uptime (most of it spent in standby), kernel_task shows 1.43TB (!) of bytes written to disk right now: What is wrong here - how can I diagnose why kernel_task is writing so much data to the disk? (This happens all the time after each reboot). Memory pressure is still "green" most of the time. Running out of space is also not an issue so most of the data seems to be "temporary". However, I am a bit worried about my SSD - writing 25 TB per year (in addition to the "regular" workload) does not seem to be a good idea... Any ideas?

When I try to do a calculation that needs to allocate and use 128 GB of memory (it is a command line program written in C), the kernel kills my process with extreme prejudice. This console log entry is an example of one instance: > 9/25/15 7:08:40.000 PM kernel: low swap: killing pid 6202 (huffgrp) The calculation works fine and in a reasonable amount of time when it allocates and uses 64 GB of memory. My machine has 32 GB of RAM and beaucoup space on the hard drive. I also tried this on another machine with 8 GB of RAM, on which the 64 GB calculation runs fine as well, taking longer of course, but the 128 GB calculation gets killed by the kernel in the same way. On both I am running Yosemite 10.10.5. By the way, malloc() never returns an error, no matter how much space I ask for. The kernel will only kill the process once too much of that memory is actually being used by the process, resulting in lots of swapping to the hard drive. So there appears to be a secret swap space limit somewhere between 64 GB and 128 GB. My question is: how do I reconfigure the kernel to permit more swap space? I found a promising looking file, /System/Library/LaunchDaemons/com.apple.dynamic_pager.plist, but I don't see the secret number in there. The man page for dynamic_pager says that all it does is set the name and location of the swap files. There is an older version of the same man page that documents a -S option to set the size of the swapfiles created. I tried that, requesting 160 GB swapfiles, but it had no effect. The swapfiles were still 1 GB each, and the process was still killed by the kernel.

Linux has a kernel argument memtest: > Specifies the number of memtest passes to be performed. Each pass selects another test pattern from a given set of patterns. Memtest fills the memory with this pattern, **validate memory contents and reserves bad memory regions that are detected.** By reserving the memory what it means is that kernel makes it unavailable for userland allocation. This means you can run programs without having to worry about them writing to a defective sector of ram. You use memtest by providing the Linux kernel an argument to boot,

memtest=        [KNL,X86,ARM,PPC] Enable memtest
                Format: 
                default : 0

This is not a default. It takes 5-10 minutes to run through the 17 passes (current default). How can I do this on OS10? ---- _**Note: I can not replace the RAM. [It's BGA soldered on.](https://apple.stackexchange.com/q/157719/76955)**_

I know it seems like this question is like the dozens of other questions about CPU overheating and kernel_task overloading it, but nope. I found an iMac (yep, found it. In the trash). I fixed it (power board was busted, screen was busted, there was no hard drive). For some reasons that are too long to explain, I ended up with both a SSD and a PCIe SSD. Whatever. I changed the LCD panel with a panel I knew was working, it didn't light up. Obviously, problem was not the LCD panel. Probably lvds connectors, since I already replaced the lvds cable by a new one. I installed El Capitan on the PCIe SSD. Other SSD, for the moment, was left alone. Computer was unusually slow, so I did a benchmark with geekbench. I got these results: 430 single core, and 1220 multi-core. Usual results for this computer are around 3600 single core and 10 000 multi-core. After running apple diagnostic, I got errors **VFD001** (screen) and **PFM006** (**SMC controler**). Here we go... Fan was going crazy from the beginning, so I had installed macs fan control. People kept telling me it was a firmware issue, but my PCIe SSD was fresh out of an Apple computer, so no reason it shouldn't work. Checking the temperatures dgave me normal results (around 90°F for the cores and surroundings). Activity monitor told me **kernel_task was operating at 230% all the time** (sometime it would go up to 500%), and Intel Power Gadget told me the CPU frequency stayed steadily at 0.8Ghz. Except... when the computer would wake up from sleep. Then, kernel_task hadn't already kicked in, and the processor went up to 1.8Ghz (would probably go up more, but with only safari, power gadget and the activity monitor on, why would it). After some tests (I checked the ram, because why not, I checked both hard drives, I checked the CPU (100% in working order, frequency at 2.7 as should be), I came to the conclusion that the faulty SMC was the culprit. By then, I had long done the **SMC reset** (one of the first things I tried), **PRAM reset**, **reinstalled el Capitan**, installed **Mavericks** on the second hard-drive, booted on a **Yosemite** system on a thunderbolt SSD, booted in **safe mode**, booted on a **new admin session**... All the basics were covered. I had also gone to the apple store, where the "genius" told me I had a screen problem (no kidding) and nothing about the SMC (I watch the diagnostic above his shoulder, and I had already ran my diagnostic, so I expected him to say something about it, but he didn't, he just mentionned that my fan was going crazy, and I told him I fixed the fan problem with a third party software). They didn't give me a paper diagnostic or emailed me anything. From what I could gather, other people have had the same problems on their iMacs. The solution? Sell the computer. Or come on forums and ask questions about the problem, and disappear. So nobody ever posted a solution about that problem. The "go into the extension folder and delete the list file corresponding to your computer name" famous hack so that the kernel_task wouldn't go crazy about the temperature can't work with my computer : iMac14,1, list stops at iMac12,2. I tried deleting all the files (at that point, what could I lose), nothing changed. **Running powermetrics gave me this :** $ sudo thermal levels cpu: 255 gpu: 0 io: 12 $ sudo powermetrics Machine model: iMac14,1 SMC version: 2.14f24 EFI version: IM141.0118.B13 OS version: 15G31 Boot arguments: Boot time: Tue Nov 29 13:50:48 2016 *** Sampled system activity (Tue Nov 29 14:13:05 2016 +0100) (5031.17ms elapsed) *** **Running tasks** Name ID CPU ms/s User% Deadlines (<2 ms, 2-5 ms) Wakeups (Intr, Pkg idle) kernel_task 0 2418.23 0.00 0.00 0.20 223.01 70.56 WindowServer 187 17.53 45.16 1.19 1.79 4.77 0.99 Activity Monitor 240 44.06 94.37 0.00 0.00 0.60 0.40 Terminal 1027 36.47 52.98 0.00 0.00 0.60 0.40 fontd 256 25.75 76.78 0.00 0.00 0.60 0.00 Intel(R) Power Gadget 368 18.29 87.83 0.00 0.00 12.12 2.78 sysmond 270 9.51 60.13 0.00 0.00 0.80 0.00 MacsFanControl 338 6.30 62.71 0.00 0.00 3.38 0.80 DEAD_TASKS -1 6.11 50.54 0.00 0.00 0.99 0.00 dpd 1082 6.88 54.60 0.00 0.00 0.41 0.00 powermetrics 1080 1.97 23.92 0.00 0.00 0.20 0.20 launchd 1 0.85 29.29 0.00 0.00 0.00 0.00 notifyd 97 0.83 48.82 0.00 0.00 0.00 0.00 softwareupdate_notify_agent 987 0.63 37.78 0.00 0.00 1.79 0.60 nsurlsessiond 295 0.54 67.67 0.00 0.00 0.80 0.80 mDNSResponder 87 0.34 40.41 0.00 0.00 1.99 0.99 launchservicesd 75 0.51 61.01 0.00 0.00 0.40 0.00 SafariCloudHistoryPushAgent 342 0.36 35.88 0.00 0.00 0.99 0.60 nsurlsessiond 190 0.43 59.51 0.00 0.00 0.99 0.80 cfprefsd 124 0.56 63.26 0.00 0.00 0.00 0.00 opendirectoryd 70 0.37 51.18 0.00 0.00 0.20 0.00 SystemUIServer 245 0.32 49.30 0.00 0.00 0.40 0.20 cfprefsd 237 0.21 53.42 0.00 0.00 0.20 0.00 syslogd 39 0.27 50.78 0.00 0.00 0.80 0.00 powerd 49 0.18 87.67 0.00 0.00 0.00 0.00 ntpd 191 0.08 26.55 0.00 0.00 0.99 0.20 mds_stores 188 0.05 28.27 0.00 0.00 0.40 0.20 mds 58 0.03 27.77 0.00 0.00 0.20 0.20 CommCenter 239 0.06 30.47 0.00 0.00 0.60 0.00 locationd 79 0.02 29.37 0.00 0.00 0.40 0.20 netbiosd 1006 0.02 31.89 0.00 0.00 0.40 0.20 diskarbitrationd 65 0.01 23.78 0.00 0.00 0.20 0.20 airportd 55 0.07 34.68 0.00 0.00 1.19 0.00 UserEventAgent 40 0.05 21.09 0.00 0.00 0.00 0.00 apsd 74 0.04 40.07 0.00 0.00 0.20 0.00 fseventsd 43 0.02 35.36 0.00 0.00 0.20 0.00 configd 48 0.01 24.50 0.00 0.00 0.20 0.00 UserEventAgent 233 0.01 25.15 0.00 0.00 0.20 0.00 systemstatsd 492 0.01 22.25 0.00 0.00 0.20 0.00 ALL_TASKS -2 2597.72 4.81 1.19 1.99 261.37 81.29 **Interrupt distribution** CPU 0: Vector 0x46(SMC): 6.56 interrupts/sec Vector 0x72(IGPU): 169.74 interrupts/sec Vector 0x74(XHC1): 0.40 interrupts/sec Vector 0x79(SSD0): 18.29 interrupts/sec Vector 0x7a(GIGE): 2.78 interrupts/sec Vector 0xdd(TMR): 221.62 interrupts/sec Vector 0xde(IPI): 93.42 interrupts/sec CPU 1: Vector 0xdd(TMR): 163.58 interrupts/sec Vector 0xde(IPI): 99.98 interrupts/sec CPU 2: Vector 0xdd(TMR): 166.76 interrupts/sec Vector 0xde(IPI): 124.03 interrupts/sec CPU 3: Vector 0xdd(TMR): 167.95 interrupts/sec Vector 0xde(IPI): 119.26 interrupts/sec **Processor usage** Intel energy model derived package power (CPUs+GT+SA): 3.24W LLC flushed residency: 0% System Average frequency as fraction of nominal: 29.56% (798.18 Mhz) Package 0 C-state residency: 85.58% (C2: 83.85% C3: 0.33% C6: 1.40% C7: 0.00% ) Core 0 C-state residency: 90.40% (C3: 0.22% C6: 90.18% C7: 0.00% ) CPU 0 duty cycles/s: active/idle [< 16 us: 38.76/8.94] [< 32 us: 5.96/9.74] [< 64 us: 15.30/18.29] [< 128 us: 13.91/17.49] [< 256 us: 9.74/11.33] [< 512 us: 8.35/6.56] [< 1024 us: 2.98/6.96] [< 2048 us: 2.58/15.30] [< 4096 us: 0.40/17.69] [< 8192 us: 0.00/39.75] [< 16384 us: 50.88/0.00] [< 32768 us: 1.79/0.00] CPU Average frequency as fraction of nominal: 29.56% (798.17 Mhz) Core 1 C-state residency: 93.28% (C3: 0.07% C6: 93.21% C7: 0.00% ) CPU 1 duty cycles/s: active/idle [< 16 us: 35.38/17.29] [< 32 us: 8.55/2.58] [< 64 us: 9.34/16.70] [< 128 us: 7.35/13.32] [< 256 us: 10.34/14.11] [< 512 us: 9.54/6.56] [< 1024 us: 2.78/5.57] [< 2048 us: 2.58/8.35] [< 4096 us: 1.19/12.72] [< 8192 us: 0.99/46.71] [< 16384 us: 54.06/0.00] [< 32768 us: 0.80/0.00] CPU Average frequency as fraction of nominal: 29.56% (798.19 Mhz) Core 2 C-state residency: 93.68% (C3: 0.13% C6: 93.55% C7: 0.00% ) CPU 2 duty cycles/s: active/idle [< 16 us: 38.16/17.49] [< 32 us: 6.36/4.37] [< 64 us: 10.73/16.50] [< 128 us: 8.35/13.52] [< 256 us: 10.93/13.12] [< 512 us: 7.35/5.57] [< 1024 us: 2.78/4.97] [< 2048 us: 2.58/9.54] [< 4096 us: 1.59/13.71] [< 8192 us: 0.80/46.71] [< 16384 us: 54.06/0.00] [< 32768 us: 1.19/0.00] CPU Average frequency as fraction of nominal: 29.56% (798.18 Mhz) Core 3 C-state residency: 92.33% (C3: 0.03% C6: 92.31% C7: 0.00% ) CPU 3 duty cycles/s: active/idle [< 16 us: 24.65/20.07] [< 32 us: 3.98/0.00] [< 64 us: 10.14/13.12] [< 128 us: 9.94/9.54] [< 256 us: 9.74/7.55] [< 512 us: 3.98/4.97] [< 1024 us: 3.58/5.17] [< 2048 us: 1.19/8.55] [< 4096 us: 0.80/6.76] [< 8192 us: 1.39/48.10] [< 16384 us: 51.88/0.00] [< 32768 us: 1.59/0.00] CPU Average frequency as fraction of nominal: 29.56% (798.17 Mhz) **GPU usage** GPU 0 name IntelIG GPU 0 C-state residency: 98.76% (0.00%, 98.76%) GPU 0 P-state residency: 1150MHz: 0.00%, 1100MHz: 0.00%, 1050MHz: 0.00%, 1000MHz: 0.00%, 950MHz: 0.00%, 900MHz: 0.00%, 850MHz: 0.00%, 800MHz: 0.00%, 750MHz: 0.00%, 700MHz: 0.00%, 650MHz: 0.00%, 600MHz: 0.00%, 550MHz: 0.00%, 500MHz: 0.00%, 450MHz: 0.00%, 400MHz: 0.00%, 350MHz: 0.00%, 300MHz: 0.00%, 250MHz: 0.00%, 200MHz: 1.37% GPU 0 average active frequency as fraction of nominal (200.00Mhz): 100.00% (200.00Mhz) GPU 0 GPU Busy 1.37% GPU 0 FB Test Case 0 **SMC sensors** CPU Thermal level: 255 IO Thermal level: 13 Fan: 1750 rpm CPU die temperature: 27.00 C (sorry about the formatting, can't really go and indent each and every line by four spaces..) I also ran the hotkernel script, got the console log, the log of the verbose boot... But all this might be too much information already? I don't know, I wanted to be thorough. I have them uploaded and ready if needed. What I'd like to know: **Is there anything I can do about the PFM006 error (by this, I mean the kernel_task eating up all my CPU) or is this hardware issue something that can't be fixed?** I don't really wish to spend anymore time on this computer if the answer ends up being "you need to change the motherboard". The Apple Support (level 2) wouln't give me any information on the PFM006 error, because I don't have a proper diagnostic done by an Apple Store (they tried calling the apple store, but the guy over there said I should go and maybe they could see if they still have it and email it to apple. WTF? Anyway... We're waiting on that, a friend is going to the shop today). The very nice lady at the level 2 support told me she was not authorized to tell me what the PFM006 error was without the proper diagnostic. So yeah. Kinda stuck here. But both the guy from support level 1 and the lady from support level 2 implied it didn't look good. Is there anything else I can do? From what I could see on the geekbench website, I'm not the only one with these crazy results, and it seems when there's some CPU throttling on this computer, CPU automatically falls down to 0.8Ghz. And yes, the computer has been cleaned, no dust inside, I checked it. I haven't tried changing the thermal paste because from what I could see, one guy with the same problem did that and it didn't fix the problem, so it seems like a waste of thermal paste and moreover I'd need to buy some. Also, the CPU is at 90°F, which means it's not hot at all, so the thermal paste wouldn't really change that. If the SMC is busted and reporting the highest possible temperature as a matter of security, all the thermal paste in the world wouldn't change it. Any clues or advice on the next step(s)? Disassembling the computer and taking back both my SSDs, the perfectly fine RAM, both speakers, my new powerboard and the fine working fan seems like the way to go right now, but maybe some of you have other suggestions I haven't tried yet. A friend suggested installing it as a hackintosh, that's an option I might try as a last resort, as I'm not sure it would change anything, but why not. Thanks! And sorry for the very long post, I really wanted to be thorough, that way you wouldn't have to ask "did you do that, and that and that" and lose your time. EDIT (1st March 17) : I have more or less left the computer on its own for the last couple of months since I had lots of other stuff to do, but one more thing I tried recently was to start it with a SMC bypass. Of course, I got the fan working like a helicopter, BUT the CPU was at its best, and the computer was crazy fast. No more CPU overload by the system. But of course I didn't leave it like that, I just ran some tests and shut it down, since it would have been damaged from the fan working full power for too long. Too bad I couldn't control the fan from a third party app (I stupidly tried "SMC fan control" before realizing why it couldn't work, aahaha, as well as a bunch of others, but they all rely on the SMC for information). What about my friend's suggestion: installing the computer as a hackintosh with a fake SMC? Does anybody think that could be a solution? I have no idea what I would be getting myself into, I'm in total "ennemy territory" here, so I'd rather spend the time disassembling it and selling it for parts than learning how to do that if somebody tells me it's bound to fail. Thanks!

For a couple days I’ve been having random hangs from macOS. It seems to happen quite often when opening PDF files stored in Zotero with an external reader (PDF Expert) but it is *not* limited to that—which makes me think it could be a hard disk problem (?) When it happens, the whole system is still responsive (can move the mouse, click or type things, etc.), but several things seem to halt: if I just clicked on a web page link, the new page won’t load (as if network was disconnected), Finder seems to hang (mouse becomes a spinning wheel when switching to it), my iStat menu showing active processes will freeze, or if I’m opening a file it’s gonna hang as well. Then all of a sudden, after 10-30 seconds, everything will un-freeze, web pages will load, files will open, etc. This seems pretty random, or at least, I have not been able to reproduce the behavior reliably. I’m somewhat technical but not an expert in OS kernels, but it seems as if a kernel thread was stuck or something (?) which blocks all the other requests from being processed. The

process uses exactly 1 core (12.5% of overall CPU on my system) during the whole time the system hangs. The big problem here is that I have *absolutely no idea* how to debug this, if it’s a software or a hardware issue, or anything. I’ve taken a look at the Console and the various logs and I don’t see anything too obvious, but I’m not technical enough in macOS’s internal workings to be able to really discern between normal or problematic entries. I have suspected CPU temperature issues (seems to be frequent with this process using up CPU) but it also happens while the machine is mostly idle, and I’ve taken a look at temperature readings and they don’t seem too unusual. I’m running the latest Ventura available on my machine, 13.1 (22C65). The computer is a 13-inch, 2020, macbook pro. Where should I start?

For the past 2 weeks, I've experienced a few Kernel Panics. When looking at the crash logs, it specifies that there was an assert fail, containing the following information: panic(cpu 1 caller 0xfffffff00bb5c154): ANS2 Recoverable Panic - assert failed: :low wA f4 i1875522 s3180082 n16 d0 w1.6 tGC9 tL30, d:0x22401, a2:0x2890041, a3:0x60000000 - power(13). I noticed it usually happens when I am performing a lot of Memory and/or CPU intensive tasks, though I don't know if there is there is any true correlation between the two. Does anybody have an idea that the specific assert means? The following link is to a pastebin with the entire crash log: https://privatebin.randomserver.xyz/?fb94ef9e6656eb9f#Ah5qpzLErBk1ZqM4egsbnqGtTaPZnokx3dQoJHdoppbJ Edit: I'm using an Intel MacBook Pro (2019), running macOS 12.5 (Monterey)