Sponsored Content
Operating Systems OS X (Apple) 12-Core MacPro (2013) kernel_task over 1200% Post 303033963 by Neo on Monday 15th of April 2019 10:57:32 AM
Old 04-15-2019
Thanks Wise,

I'm in Thailand (on the seaside) and we have great Apple service here.

Recently my MacBook Air 2013 died and I went to Apple and paid them a small fee (around $28 USD) to check it out. They did a full analysis (it would not power up at all) and their Apple techs told me the logic board was bad. They quoted around $600 to replace.

I took that MBA to some local repair shop and they fixed the logic board for about $200 dollars and it works great. That's much better than the $600 for a logic board or nearly $2000 for a new one I don't really need.

The only thing I don't look forward to is lugging the heavy MacPro up there, since it is a lot heavier and bulkier than my little MBAs.
This User Gave Thanks to Neo For This Post:
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Can I use a general printer(HP LaserJet 1200) on solaris?

can it be used? how to config it? thanks (4 Replies)
Discussion started by: cloudsmell
4 Replies

2. OS X (Apple)

kernel_task help

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

T5140 CPU Speed is 1200 Mhz or 1165 Mhz?

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

2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1

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)

DiskSpeedTest 256GB OEM v. 960GB Transcend 855 SSD MacPro 2013, 12-Core, 64GB RAM

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! Upgrade to Catalina 10.15.3 Crashes MacPro (2013) - Will Not Boot !

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
CRASHINFO(8)						    BSD System Manager's Manual 					      CRASHINFO(8)

NAME
crashinfo -- analyze a core dump of the operating system SYNOPSIS
crashinfo [-d crashdir] [-n dumpnr] [-k kernel] [core] DESCRIPTION
The crashinfo utility analyzes a core dump saved by savecore(8). It generates a text file containing the analysis in the same directory as the core dump. For a given core dump file named vmcore.XX the generated text file will be named core.txt.XX. By default, crashinfo analyzes the most recent core dump in the core dump directory. A specific core dump may be specified via either the core or dumpnr arguments. Once crashinfo has located a core dump, it analyzes the core dump to determine the exact version of the kernel that generated the core. It then looks for a matching kernel file under each of the subdirectories in /boot. The location of the kernel file can also be explicitly provided via the kernel argument. Once crashinfo has located a core dump and kernel, it uses several utilities to analyze the core including dmesg(8), fstat(1), iostat(8), ipcs(1), kgdb(1), netstat(1), nfsstat(1), ps(1), pstat(8), and vmstat(8). The options are as follows: -d crashdir Specify an alternate core dump directory. The default crash dump directory is /var/crash. -n dumpnr Use the core dump saved in vmcore.dumpnr instead of the latest core in the core dump directory. -k kernel Specify an explicit kernel file. SEE ALSO
textdump(4), savecore(8) HISTORY
The crashinfo utility appeared in FreeBSD 6.4. BSD
June 28, 2008 BSD
All times are GMT -4. The time now is 12:50 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy