![]() So its definitely a hardware issue, or a common Mojave bug. Set computer to sleep and it crashed right away on a fresh install, same errors as KP in above post.Great. Just deleted and readded everything to fix that.ĭid some testing to invoke a crash. Bluetooth was a bit annoying since the SMC/PRAM still had memory of the devices. It finished up the installer with absolutely no hitches and I was able to set everything up. I let the installer do everything before its first reboot, then powered down the MBP and placed the SSD into the cMP. Created a USB installer then booted my Catalina MBP from it, with a blank SSD in an external dock. To eliminate it being the fact that my install is super screwed up, I installed Mojave (10.14.6 combined) that i pulled down tonight from Apple's website. I am officially out of ideas to troubleshoot. I am officially at my wits end with this thing. Kernel Extensions in process name corresponding to current thread: kernel_task I did get a newer more useful KP though, full log attached, summary below This ended up not really changing anything. This might fix this issue, or their may be other factors. Might push me to find a different solution for VMs in the future. I am going to use the VBox uninstall helper script and completely remove it, I had some issues with stability of VMs in the past so for the most part I stopped using it altogether on this machine. 17:02:58 signpost_reporter - High CPU UseĮxecutable: /usr/libexec/signpost_reporterĮxtra tidbit, if the below is failing, sleep will definitely not work properly, ACPI controls such functionality. Panic(cpu 0 caller 0xffffff7f859449f0): pmLock: waited too long, held VirtualBox is causing a pmLock condition that is crashing the machine.ĭiagnostics Information (past 7-30 days): ![]() I ran EtreCheck, if what it reports seems accurate. Currently it seems to just sit on a black screen. I have attached the most recent kernel panic (this was prior to the security update i applied today), but the behavior of the system when it produces kernel panics like the attached, the computer is sitting idle and it probably has to do with CPU power management as I had mentioned, but it will recover and reboot to the login screen. I can collect any information necessary and perform any steps needed to further identify/fix the problem. ![]() I am unable to see if there are any crash messages on the screen when this occurs, that may be because I am using an RX 580, but not the Sapphire card that supports boot splash. Pressing the power button instantly turns the machine off. The power LED will pulse slowly like it would if it were asleep, and the fans are still running on the system.Īny attempt to wake the machine fails, no input on the keyboard or mouse will work. Now, I have no idea because my only cue to the system hanging or crashing is the hard disks shutting off. In the past, crashes with automatic reboots have occurred due to issues with cpuPowerManagement. I just installed the latest security patch for 10.14.6, and this may have made the problem worse. The computer seems to work just fine when I am using it and I don't allow it to lock, turn off the screen, or sleep. I am not sure where to start because I am not seeing any kernel panics being generated in the Logs folder.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |