04-15-2019
Resetting the SMC did not work.
Activity monitor still shows CPU at 2000% for the kernel_task.
I will test to see if the problem is the SSD, next.
I tried running First Aid on the SSD but the high CPU at around 2000% makes this very slow, and the system just hangs.
The restore process did not indicate the SSD was bad, and I've tried every Apple support suggestion.
Hmmmm. This is a mystery that needs to be solved.
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
can it be used?
how to config it?
thanks (4 Replies)
Discussion started by: cloudsmell
4 Replies
2. OS X (Apple)
I installed 10.5 (Leopard) on my G4 733 Mhz (after minor tampering with the install package, just switched a boolean FALSE to TRUE).
Everything works fine after startup, but once I sleep the computer and wake it back up, kernel_task starts using at as much CPU runtime as it can, as in past 90%.... (0 Replies)
Discussion started by: peter.story
0 Replies
3. Solaris
Hi bros,
CPU speed of Sun Sparc Enterprise T5140 in data sheet is 1200 Mhz. Why it shows in "prtdiag -v" command each thread just has speed at 1165 Mhz.
Thank you,
tien86 (4 Replies)
Discussion started by: tien86
4 Replies
4. Hardware
Hey MacPro users.
I just bought a refurbished 13-Core MacPro with 64GB of RAM for a cybersecurity gaming project I'm working on. Could not wait for the new MacPro in 2019, so this will have to do:
2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1
Now, I'm... (0 Replies)
Discussion started by: Neo
0 Replies
5. OS X (Apple)
Before Upgrade:
https://www.unix.com/members/1-albums177-picture1220.png
After Upgrade:
https://www.unix.com/members/1-albums177-picture1221.png (0 Replies)
Discussion started by: Neo
0 Replies
6. OS X (Apple)
WARNING!
Just upgraded my MacPro (2013) from Catalina 10.15.2 to 10.15.3.
After the routine download and restart for upgrade installation, the Mac would not boot. Totally crashed.
Now, I'm in the process of a 15 hour restore from my last time machine backup.
I'm not very happy with... (3 Replies)
Discussion started by: Neo
3 Replies
CORE(5) BSD File Formats Manual CORE(5)
NAME
core -- memory image file format
SYNOPSIS
#include <sys/param.h>
DESCRIPTION
A small number of signals which cause abnormal termination of a process also cause a record of the process's in-core state to be written to
disk for later examination by one of the available debuggers. (See sigaction(2).) This memory image is written to a file named by default
core.pid, where pid is the process ID of the process, in the /cores directory, provided the terminated process had write permission in the
directory, and the directory existed.
The maximum size of a core file is limited by setrlimit(2). Files which would be larger than the limit are not created.
The core file consists of the Mach-O(5) header as described in the <mach-o/loader.h> file. The remainder of the core file consists of vari-
ous sections described in the Mach-O(5) header.
NOTE
Core dumps are disabled by default under Darwin/Mac OS X. To re-enable core dumps, a privileged user must do one of the following
* Edit /etc/launchd.conf or $HOME/.launchd.conf and add a line specifying the limit limit core unlimited
* A privileged user can also enable cores with launchctl limit core unlimited
* A privileged user can also enable core files by using ulimit(1) or limit(1) depending upon the shell.
SEE ALSO
gdb(1), setrlimit(2), sigaction(2), Mach-O(5), launchd.conf(5), launchd.plist(5), sysctl(8)
HISTORY
A core file format appeared in Version 6 AT&T UNIX.
BSD
June 26, 2008 BSD