Kernel[0]: SMC::smcReadKeyAction ERROR TC0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8037fe0000

I have these messages popping up in my console:
kernel[0]: SMC::smcReadKeyAction ERROR TC0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8037fe0000
Does anyone know how to get rid of these?

Weird indeed. Yeah, on other Macs it shows four bars, you're right, but on mine only on bar. The floating window sees 8 as it should. They're all Quad Core i7. I have no clue why mine is showing only one bar. Always did, even under 10.8 so that's why I started using CPULed. Anyway, it's a minor inconvenience.

Similar Messages

Kernel[0]: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8033e13000

Does anybody know what causes this and how to fix it? I have had 2 kernel panics in a row and am wondering if this has to do with it. I see rows and rows of this massage. I am not 100% sure but it seems to happen as I use Safari, but I can not be sure.
Using, OS 10.9.2.
Message in consol reads:
01/03/2014 06:59:55.000 kernel[0]: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8033e13000
Thanks.

Hey Buddy,
It's hard to find anything out there since all this stuff is internal to Apple.
Your error code is different than mine (which was a light sensor), so I've been looking up yours too.
Your System Management Console is having a problem reading the TMFS key. It's not uncommon for SMC key issues from my experience. It's just hard to point to what TMFS stands for. Do you happen to have a Time Machine storage mounted or an automatic backup scheduled? It could stand for Time Machine File Storage. Maybe the drive became unmounted or a backup was performed on an absent drive. Just a hunch.
Regardless, I don't think that would cause a kernel panic alone. But, since no one else is helping, I can try. I'm a software developer, not a sys admin, but here's what I would suggest:
Download EtreCheck: http://www.etresoft.com/etrecheck. This quickly compiles your system configuration and any custom hooks (aka launch agents and such) you have.
Paste the results here
If you have a copy (or can scroll up) of the Console log from when you got that error during the kernel panic, paste that also in another post
I'll take a look and assist how I can, if I can
Safari seems to bind pretty tightly to the OS, similar to Internet Explorer on Windows. Sometimes it can trigger a GPU switch on its own, showing vertical tearing, or consume more resources for itself (a runaway web app) than a 3rd party browser would be allowed to. I prefer to use it, but I DO find that Safari can bring the OS down if something happens to it, unlike other browsers.
Good luck!
-Greg

Hi, i got same error all the time... kernel[0]: SMC::smcReadKeyAction ERROR F1Mn kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801c97d000

i read allready some smcFan error from another dude's, i don't use it
anyone know the code: "fKeyHashTable=0x0xffffff801c97d000" for what is ?
thx, regards b4rb0s

Another update for iStat Menus today but still the same erors are occuring on my MacPro 3,1 with Lion 10.7.5.
I have been having stability issues on this machine for several weeks and I am unable to determine what the cause is. I have done everything (except what works ) including a reinstall of the OS and upgrade, repairs of this and that. I do not specifically think my instability is related to the SMC::smcReadKeyAction errors that happen each time iStatMenus loads at startup...... but I guess it is possible there is an intersection.....
Have you uninstalled iStatServer which you might have installed to remotely monitor your machine parameters with your iPhone, iPad, etc? While I loved that feature of iStat, I uninstalled it some weeks back as I was closing up security attack surface on my servers and workstations?
Here's the tail of my iStat related logs from today after upgrade....
10/24/12 7:30:01.000 AM kernel: SMC::smcReadKeyAction ERROR PG0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff802a020000
10/24/12 7:30:01.000 AM kernel: SMC::smcReadKeyAction ERROR PH1Z kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff802a020000
10/24/12 7:30:02.009 AM SystemUIServer: iStatMenus Daemon version 3.27 (103)
10/24/12 7:30:02.012 AM SystemUIServer: iStatMenus Daemon version 3.27 (103)
10/24/12 7:30:32.423 AM SystemUIServer: -[TCMNATPMPPortMapper refreshExternalIPInThread] NAT-PMP: IP refresh did fail: -7

Kernel: SMC::smcReadKeyAction ERROR F1Mn kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80135a4000

I am getting the following error in console every 5 seconds:
kernel: SMC::smcReadKeyAction ERROR F1Mn kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff80135a4000
I have checked the threads and am not sure why I have the error
1. I long ago deleted SMC Fan-Control and cant find any traces of it (perhaps I am missing some)
2. I removed iStat Menu's using its uninstall function and also cannot find any traces
3. I also no removed the iStat Mini Widget just in case.
The problem has not gone and every now and then it appears to be crashing my machine.
Any ideas where this error may be coming from ? Any help would be appreciated.
I am now on OSX 10.7.5
Thanks,

Another update for iStat Menus today but still the same erors are occuring on my MacPro 3,1 with Lion 10.7.5.
I have been having stability issues on this machine for several weeks and I am unable to determine what the cause is. I have done everything (except what works ) including a reinstall of the OS and upgrade, repairs of this and that. I do not specifically think my instability is related to the SMC::smcReadKeyAction errors that happen each time iStatMenus loads at startup...... but I guess it is possible there is an intersection.....
Have you uninstalled iStatServer which you might have installed to remotely monitor your machine parameters with your iPhone, iPad, etc? While I loved that feature of iStat, I uninstalled it some weeks back as I was closing up security attack surface on my servers and workstations?
Here's the tail of my iStat related logs from today after upgrade....
10/24/12 7:30:01.000 AM kernel: SMC::smcReadKeyAction ERROR PG0R kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff802a020000
10/24/12 7:30:01.000 AM kernel: SMC::smcReadKeyAction ERROR PH1Z kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff802a020000
10/24/12 7:30:02.009 AM SystemUIServer: iStatMenus Daemon version 3.27 (103)
10/24/12 7:30:02.012 AM SystemUIServer: iStatMenus Daemon version 3.27 (103)
10/24/12 7:30:32.423 AM SystemUIServer: -[TCMNATPMPPortMapper refreshExternalIPInThread] NAT-PMP: IP refresh did fail: -7

Intel-based iMac stuck in grey screen with spinning wheel. SMC::smcReadKeyAction ERROR THOP kSMBadArgumentError(0x89)

Hi guys,
since yesterday my Intel-Based iMac doesn't boot normally, its stuck in grey screen with a spinning wheel.
Its an Intel-based iMac 21.5'' purchased in 2011, and i recently (2 months ago) upgraded it to Mavericks.
-2 weeks ago, i installed smcFanControl app
-Tried start up in Safe Mode by holding Shift but its not working. i think i hear fans are working more than they were before the problem occurs.
-entered Single User Mode and i get an error
SMC ::smcReadKeyAction ERROR THOP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8029fa1000
-followed some instructions found online, but can execute the correct commands in SingleUserMode
tried to remove FanControl as explained here: http://apple.stackexchange.com/questions/110667/errorr-kernel-smcsmcreadkeyactio n-in-console
any ideas what may caused this and how can i fix this?
Thanks in advance

Take each of these steps that you haven't already tried. Stop when the problem is resolved.
Step 1
The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, boot from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
Step 2
If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
Step 3
Sometimes a startup failure can be resolved by resetting the NVRAM.
Step 4
If you use a wireless keyboard, trackpad, or mouse, replace or recharge the batteries. The battery level shown in the Bluetooth menu item may not be accurate.
Step 5
If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
Step 6
Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
Step 7
If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
Start up in safe mode. Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Post for further instructions.
Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 10. If you ever have another problem with the drive, replace it immediately.
If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
Step 8
Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
Step 9
Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
Step 10
Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
Step 11
This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
Step 12
If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

Kernel Panic -- Graphics chip error! Restarted.

Anyone out there seen ridiculous gfx card/kernel errors with Adobe CS2? My machine runs weird every time that I use Photoshop or Illustrator. Batches don't finish, and I have even been getting kernel panics lately. I would post it to Adobe, but kernel panics and hardware errors fall into Apple's domain. Hardware/Software/OS is fine for all but CS2, including opengl/coreimage/corevideo apps. I have a quad g5 with an nvidia 6800 GT gfx card with dual cinema displays and a wacom tablet. OSX is up-to-date, as is CS2.
Here's a snippet from my rather scary system log for yesterday, when I was attempting to run a batch process in illustrator...my logs are peppered with graphics chip errors every time that I use CS2. Any options other than wait for a new gfx driver from Apple or keep re-running the hardware tests?
Feb 5 03:15:01 bourbon cp: error processing extended attributes: Operation not permitted
Feb 5 08:55:06 bourbon ntpd[158]: time reset 0.443060 s
Feb 5 18:27:49 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 18:27:51 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 18:27:51 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 18:28:19 bourbon /Applications/Adobe Illustrator CS2/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator: Emergency Save Failed
Feb 5 22:59:03 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 22:59:44 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 22:59:45 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 22:59:52 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 22:59:56 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 22:59:56 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 22:59:58 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 22:59:58 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:04 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:06 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:06 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:06 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:06 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:07 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:07 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:08 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:12 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:12 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:12 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:12 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:15 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:16 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:19 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:20 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:21 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:21 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:22 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:22 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:22 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:23 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:23 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:23 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:24 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:25 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:25 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:25 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:25 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:25 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:27 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:27 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:28 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:30 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:31 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:32 bourbon kernel[0]: Graphics chip error! Restarted.
Feb 5 23:00:35 bourbon /Applications/Adobe Illustrator CS2/Adobe Illustrator.app/Contents/MacOS/Adobe Illustrator: Emergency Save Failed
Feb 5 23:37:58 bourbon crashdump[828]: Adobe Illustrator crashed
PowerMac G5 Mac OS X (10.4.8)
PowerMac G5 Mac OS X (10.4.8) CS2, nvidia 6800 GT, kernel panic

Here are the relevant snippets from panic log...I got a new wacom tablet in January. From the logs, it looks like 1 USB panic and 2 gfx driver panics this year....
Sun Jan 14 18:41:43 2007
panic(cpu 3 caller 0x0003FFE8): zalloc: "ipc kmsgs" (3061024 elements) retry fail 3
Latest stack backtrace for cpu 3:
Backtrace:
0x00095138 0x00095650 0x00026898 0x0003FFE8 0x0001A308 0x0001AA8C 0x000295B0 0x002E84C4
0x002BD140 0x002BD294 0x002BF230 0x00446A0C 0x004D0E08 0x002EB00C 0x0008C318 0x0002921C
0x000233F8 0x000ABAAC 0x6B3C2F73
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBUserClient(2.5.0)@0x4cc000
dependency: com.apple.iokit.IOUSBFamily(2.5.6)@0x43e000
com.apple.iokit.IOUSBFamily(2.5.6)@0x43e000
Proceeding back via exception chain:
Exception state (sv=0x60BBF280)
PC=0x9000AB48; MSR=0x0000D030; DAR=0x36CE7000; DSISR=0x42000000; LR=0x9000AA9C; R1=0xF0080A20; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
Sun Jan 14 22:14:00 2007
Unresolved kernel trap(cpu 3): 0x300 - Data access DAR=0x000000007970E34E PC=0x0000000000939D3C
Latest crash info for cpu 3:
Exception state (sv=0x60C3BA00)
PC=0x00939D3C; MSR=0x00009030; DAR=0x7970E34E; DSISR=0x40000000; LR=0x00939D24; R1=0x4684BB40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00949814 0x00922EE0 0x002E8A34 0x002EA900 0x0008BEC4
0x0002921C 0x000233F8 0x000ABAAC 0x4D697861
backtrace terminated - frame not mapped or invalid: 0xBFFFE050
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x917000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x714000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x738000
dependency: com.apple.NVDAResman(4.1.8)@0x74e000
Proceeding back via exception chain:
Exception state (sv=0x60C3BA00)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x60988500)
PC=0x9000AB48; MSR=0x0200F030; DAR=0x3715D000; DSISR=0x42000000; LR=0x9000AA9C; R1=0xBFFFE050; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 3 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 3:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780
Proceeding back via exception chain:
Exception state (sv=0x60C3BA00)
PC=0x00939D3C; MSR=0x00009030; DAR=0x7970E34E; DSISR=0x40000000; LR=0x00939D24; R1=0x4684BB40; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00949814 0x00922EE0 0x002E8A34 0x002EA900 0x0008BEC4
0x0002921C 0x000233F8 0x000ABAAC 0x4D697861
backtrace terminated - frame not mapped or invalid: 0xBFFFE050
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x917000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x714000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x738000
dependency: com.apple.NVDAResman(4.1.8)@0x74e000
Exception state (sv=0x60988500)
PC=0x9000AB48; MSR=0x0200
Sun Feb 4 13:53:46 2007
Unresolved kernel trap(cpu 3): 0x300 - Data access DAR=0x000000007BA1A34E PC=0x0000000000939E14
Latest crash info for cpu 3:
Exception state (sv=0x61ACE500)
PC=0x00939E14; MSR=0x00009030; DAR=0x7BA1A34E; DSISR=0x40000000; LR=0x0093A82C; R1=0x46753AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0093B6C4 0x0093A82C 0x00935D5C 0x00922C74 0x002E8A34 0x002EA900
0x0008BEC4 0x0002921C 0x000233F8 0x000ABAAC 0x3C3C3C3C
backtrace terminated - frame not mapped or invalid: 0xBFFFE240
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x917000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x714000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x738000
dependency: com.apple.NVDAResman(4.1.8)@0x74e000
Proceeding back via exception chain:
Exception state (sv=0x61ACE500)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x60D3C000)
PC=0x9000AB48; MSR=0x0200F030; DAR=0x01852808; DSISR=0x0A000000; LR=0x9000AA9C; R1=0xBFFFE240; XCP=0x00000030 (0xC00 - System call)
Kernel version:
Darwin Kernel Version 8.8.0: Fri Sep 8 17:18:57 PDT 2006; root:xnu-792.12.6.obj~1/RELEASE_PPC
panic(cpu 3 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 3:
Backtrace:
0x00095138 0x00095650 0x00026898 0x000A7E04 0x000AB780
Proceeding back via exception chain:
Exception state (sv=0x61ACE500)
PC=0x00939E14; MSR=0x00009030; DAR=0x7BA1A34E; DSISR=0x40000000; LR=0x0093A82C; R1=0x46753AE0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0093B6C4 0x0093A82C 0x00935D5C 0x00922C74 0x002E8A34 0x002EA900
0x0008BEC4 0x0002921C 0x000233F8 0x000ABAAC 0x3C3C3C3C
backtrace terminated - frame not mapped or invalid: 0xBFFFE240
Kernel loadable modules in backtrace (with dependencies):
com.apple.GeForce(4.1.8)@0x917000
dependency: com.apple.iokit.IOPCIFamily(1.7)@0x45f000
dependency: com.apple.iokit.IOGraphicsFamily(1.4.1)@0x714000
dependency: com.apple.iokit.IONDRVSupport(1.4.1)@0x738000
dependency: com.apple.NVDAResman(4.1.8)@0x74e000
Exception state (sv=0x60D3C000)
PC0
PowerMac G5 Mac OS X (10.4.8)

"System error KERNEL.446571: 1528: Internal error detected by SMP multi-tasker" in LabVIEW RT 8.5

When I try to run my startup executable on LabVIEW RT 8.5 I get the message "System error KERNEL.446571: 1528: Internal error detected by SMP multi-tasker". What does this mean? How do I get around it? Has anyone else seen something simliar?
Robert C. Mortensen
Certified LabVIEW Architect
Certified LabVIEW Embedded Systems Developer
Endigit

Just crashed again with the same error. This time it was accompanied by a support.cpp error line 1112. The data in the error log file (rtlog.txt attached) doesn't seem to correlate with the crashes I'm seeing. I think a lot of the crashes aren't getting logged at all. The latest development is crashes after it's been running a while (1528 & 1510 happen on startup). The RT desktop simply reboots without showing or logging an error. Any way to track that down? Does this file mean anything more to you than me? I don't feel like I have enough material or info to create an SR.
Thanks,
Robert C. Mortensen
Certified LabVIEW Architect
Certified LabVIEW Embedded Systems Developer
Endigit
Attachments:
rtlog.txt ‏548 KB

Kernel Panics and other errors

Ok here's the deal. I was having a lot of problems with my MacBook Pro and reinstalling Leopard did nothing to help, so I took it to the Apple store near me and checked it in. A couple of weeks later I got it back with a new logic board, new hard drive, and new hard drive cable. Since then I've been having kernel panics every now and then. The only time it happens regularly is when I try to do a directory repair with DiskWarrior on my external Firewire drive running 10.5.3.
The FW drive's panic log refers to a simple lock deadlock detection caused by com.alsoft.Preview. A Safe Boot fixes the issue, which would point to a conflicting kext or login item or something like that. What I can't figure out is why it worked perfectly before my laptop was repaired, and now consistently causes a kernel panic whenever I run it. Nothing on the external drive has changed since then, so I'd have to assume the hardware change would be the problem. But then why would a Safe Boot solve the problem? Maybe a driver or something that isn't being loaded in Safe Mode but normally is encountering an error due to bad hardware?
I also have two other panic logs from my internal hard drive. The first is a kernel trap, also caused by com.alsoft.Preview. I'm not sure why it was stored on the internal hard drive's Logs folder since I only run DiskWarrior from my FW drive (it's not even installed on the internal drive), but I digress. The other panic was caused by an "IOGMD: not wired for the IODMACommand" error. Apparently the error had to do with a few USB-related drivers and IOKits, namely IOUSBMassStorageClass, AppleUSBEHCI, and IOUSBFamily. I've been having some weird issues with my USB flash drive lately, mostly file transfers going incredibly slow (like 300 KB/sec slow). I haven't been having these issues on any other computer, and I've even verified the flash drive with Disk Utility, so I would have to say the problem is with the Mac and not the drive itself.
Now for the other errors. I've been getting Disk Too Slow errors in GarageBand when recording guitar tracks (which I've never gotten before), and there's a lot of background noise when recording that wasn't there before the repair. Before I could connect the audio output on the amp to the line in on my laptop using a 1/4" to 3.5 mm cable, and everything sounded pretty clean. Now the sound is distorted and there's a lot of static during silence. The only way to get it sound somewhat decent is to play around with the gate and compression settings.
I'm also having occasional issues ejecting drives and virtual drives, Spotlight tries to index drives that are added to the exception list in System Preferences, and weird random errors showing up in Console related to Finder, Dock, certain apps, and fseventd (the fseventd errors are usually about my flash drive). I'm leaning toward a bad logic board, even though that was just replaced. I just did an Erase and Install a few weeks ago so I doubt it's software-related. Plus I've been having issues with it in one form or another since I got it back, which also makes me think it's not the OS.
Anyway, I'm just looking for opinions at this point. I'm going to take it back to the Apple store in a few days because of a small group of dead pixels, so as long as I'm down there I'll ask them. In the meantime, anyone have any thoughts?

https://bbs.archlinux.org/viewtopic.php?id=138105

Manual Kernel Compilation fails with "Error: not a valid kernel..."

I wanted to try out the Zen kernel to compile my own custom kernel. The basic steps that I did were:
1. $ make localmodconfig
2. $ make -j3
3. # make modules_install
4. # cp -v ~/<build directory>/arch/x86_64/boot/bzImage /boot/vmlinuz-linux-zen-3.1.4.img
5. # mkinitcpio -k vmlinuz-linux-zen-3.1.4 -g /boot/initramfs-linux-zen-3.1.4
and I get the error:
==> ERROR: '/lib/modules/vmlinuz-linux-zen-3.1.4' is not a valid kernel module directory
Inside of /lib/modules I have a new files called "3.1.4-zen-ARCH-g30db333 (and the original files that were there from the stock kernel).
Inside of /boot/ I have the stock image and the stock initram as well as "vmlinuz-linux-zen-3.1.4.img"
Which step am I missing? Also, I was thinking it was possible to NOT use an initram if I just compiled the ext2 and ext4 (root is ext4) into the kernel instead of building them as modules. Is my thinking correct? Also, if anyone needs a reason why I'm using the zen sources instead of the nice Liquorix binary, the answer is simply that I wanted to mess around with it to satisfy my curiosity. Thanks.

As per the man page:
-k kernelversion
Use kernelversion, instead of the current running kernel. This may be a path to a kernel image or a
specific kernel version. If specified as a path to an image, this will always be prefixed by the basedir.
You've picked... neither? I guess you want "/boot/vmlinuz-linux-zen-3.1.4.img" or "3.1.4-zen-ARCH-g30db333".
Compiling the filesystem module into the kernel alone is not sufficient to avoid using an initramfs. You also need, at a minimum, drivers for the disk controller and a block device driver.
Last edited by falconindy (2011-12-08 04:43:21)

SMC Install Error

Hi - can someone help with my install problem please? I'm trying to install SMC 4.0 onto OpenSolaris 2009.06 snv_111b x86. I've got as far as running ./es_guiinst from the command line and the installer starts - but as soon as I hit the "Next" button it errors with "The Wizard could not detect the source files. Exiting".
I'm installing this using the guidelines from docs.sun.com and all it says is to run that command - am I missing something?
Thanks.

Apparently isn't supported / work with opensolaris just yet. Installed Solaris 10 instead and the install works, it even starts just can't login.

Kernel 2.6.23 error

Hi,
So I'm recieving a error everytime I boot into the kernel, and I've been having this ever since 2.6.23 came out.
The error is
ata3:comreset failed (errno=880)
ata4:comreset failed (errno=880)
any help would be appreciated, thanks.

well you could step back using ide-legacy.
means you need to change initramdisk and fstab, bootloader entries to old hdX scheme from sdX scheme
a bit complicated and well prepared step, else your system is unbootable

Kernel panic defeated, 'serious error' remains

Hi,
As most posters around here, I've been having severe problems with Premiere Pro 6.02 on OS 10.7.4 FW800 drive, eSATA external drive for project and clips, Macbook Pro 8,3 (early 2011, 16GB RAM, AMD Radeon HD 6750M 1024MB). The project is 1080p50 AVCHD material and psd stills. I'm using Mercury and I have set the System to never use Intel graphics.
The major hurdle was apparently random kernel panics, especially when I tried to scrub using the left/right arrow keys.
That problem was solved when I followed the advice of a poster in this forum, who created a fresh admin account. No more kernel panics!
The 'serious error' crashes remain and are easily recreated:
• I double click a clip (AVCHD or still) in the Timeline to load it into the Source monitor.
• I close the Source monitor by clicking in the 'x' close box in the upper r/h corner.
BAM!
Luckily, Premiere manages to save the file before shutting down and the file is good to go. The original project file causes a kernel panic if I try to open it, though.
However, I can unload the clip in the Source monitor by using Close in the drop-down.
Also, I can close the Source monitor after it's empty by clicking on the 'x' – no crash.
So, it's the act of clicking on the Source monitor 'x' icon when it's loaded with a clip that triggers the crash, every time.
I suspected that the Microsoft IntelliMouse driver might be the culprit and uninstalled it. Didn't change anything.
I take the liberty of attaching the crash report below, in the hope that someone with better log reading chops than I can spot some crucial lead.
Best regards,
Joachim
Process:
Adobe Premiere Pro CS6 [891]
Path:
/Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6
Identifier:
com.adobe.AdobePremierePro
Version:
6.0.2 (6.0.2)
Code Type:
X86-64 (Native)
Parent Process: launchd [259]
Date/Time:
2013-02-26 15:31:01.999 +0500
OS Version:
Mac OS X 10.7.4 (11E53)
Report Version: 9
Interval Since Last Report:
19955 sec
Crashes Since Last Report:
5
Per-App Interval Since Last Report: 16869 sec
Per-App Crashes Since Last Report:   3
Anonymous UUID:
120ECC69-5B41-4EFF-A88F-2D877C7A261B
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__TEXT
0000000100000000-0000000100004000 [   16K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CS6/Adobe Premiere Pro CS6.app/Contents/MacOS/Adobe Premiere Pro CS6
Application Specific Information:
objc[891]: garbage collection is OFF
abort() called

First off, upgrade to 10.7.5 without delay. Pr much prefers that to any other 10.7 build.
KPs are almost always driver related. Run Disk Warrior after each KP. Reinstall new drivers if that doesn't help. Which one? The one you installed right before your KP.
Serious Errors on my system are almost always related to corruption in the Media Cache. Deleting the contents usually sends them on their way, for a while.
Delete your Pr prefs at any sign of weirdness. I need to do this frequently (several times a week), so I use Digital Rebellion's Preference Manager.

Kernel broken. Pacman errors with PGP sig [solved]

I had the unlucky situation to have a power failure in the middle of a Kernel upgrade using Pacman. System came back up and the kernel was not installed. So I have NO working OS on the machine.
I can boot into a live USB environment and chroot into my install. I can run Pacman, and thought I could just pacman -S linux and let it do it's thing and I'd be all good. but... I get package signature PGP verification error message and cannot install anything with Pacman.
Of course, the error with the Kernel install happened before Daylight savings time, and now we're INTO DST, so I suspect it's a "time" issue as reported on the Wiki.
timedatectl will not work in the chroot environment. Can't connect to dbus. I am totally migrated to a systemd install, but systemctl enable dbus.service does not start the dbus from within the chroot environment.So I cannot even see if my chroot environment is on the right time. 'cal' works and shows the proper date, which I can change in the BIOS to whatever I want.
running ntpd first doesn't fix the error with Pacman.
Any ideas?
Last edited by hooya (2013-03-16 20:02:35)

I tried that and didn't work either, because there were files left behind in the initial installation that was broken. Even after removing them I got disk spacer errors (there was no disk space issue, so that's weird).
I did get it finally though. I ended up using the initial pacstrap install script to install the base packages as per the Beginner Install Guide (and selected only option 26 "Linux") which did work, probably because it was operating from outside of the chroot environment. A bit "hacky" but I'm at least typing this message from my normal installation this time!

[Resolved] Borkage after Upgrade (A Kernel or SSL Upgrade Error?)

Turned my x121e on this morning and felt like a quick System upgrade. In came groff, a filesystem package, ssl, and the newest kernel Arch is sending out. Once complete, I rebooted- the machine would not reboot itself, and froze. So I had to hard reboot. On the next bootup there was an error of some filename being too short (sorry cant remember precise error), and then after that the system boots, but the text size in console has changed, graphics seem slightly different, and when I login I cannot use trackpoint or touchpad, DWM is without wallpaper, all dwm-panel just default. It doesn't turn off from pressing hardswitch (it used to, very quickly), I can't open anything.
I am at a complete ends immediately. All I can think of is the few grub parameters I've added, but these were working perfectly up until the upgrade, and probably should not be mentioned here.
I will look into rolling back the upgrades. I can try and provide any info- though do not have connection for Arch at the moment as not running in X and don't have wired around currently (should do later).
I would really appreciate some help with this if anyone can.
Thank you.
Last edited by dura (2013-03-03 17:31:19)

Ok, so I chrooted into my system with usb, then tried to downgrade the kernel to what was used before 3.7.7-1, following the wiki page on downgrading the kernel.
Pacman then reads an error:
Error while loading shared libraries: /usr/lib/libcrypto.so.1.0.0:file too short
Incidentally, there was also a ssl upgrade as part of the -Syu this morning. I expected nothing from it, but read elsewhere off an ssl upgrade causing multiple errors.
Stumped again really.
Not sure if the original error message was anything to do with kernel: all I can state is was either mkinit related, or libcrypto related (sorry- I'd literally just woken up when I -Syu'd).
Thank you for any ideas.
Last edited by dura (2013-02-16 16:50:52)

Kernel panic and RAM errors

Hi there,
I have a problem with my MacBook which I bought in April 2007. I upgraded my memory and now have 3GB, the maximum capacity my MacBook 2,1 can deal with. In last week, my computer froze entirely...but the mouse pointer was still moveable what struck me a little. Now, this morning, I had a kernel panic. I'll post the log at the end of this message. I tested my memory because of that with a linux dvd: memtest86. I have up to now 510 errors. I've already changed the memory modules and tested them separately - always errors. Now I wonder if both modules are defective or perhaps something else like perhaps the logic board or the memory controller. The really strange thing is that if I test the memory within OSX, there are no errors found.
Panic log:
panic(cpu 0 caller 0x00241FFA): "ip_output: mix of packet in packetlist is wrong=0x4396a900"@/SourceCache/xnu/xnu-1228.9.59/bsd/netinet/ip_output.c:1494
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x415c3778 : 0x12b4f3 (0x45b13c 0x415c37ac 0x1335e4 0x0)
0x415c37c8 : 0x241ffa (0x4771b8 0x4396a900 0x0 0x0)
0x415c3918 : 0x248771 (0x4396a900 0x3 0x0 0x506b6b0)
0x415c3968 : 0x249f60 (0x3 0x0 0x0 0x1)
0x415c3a98 : 0x24724b (0x506b720 0x415c3c38 0x187c4a61 0x6401a8c0)
0x415c3c78 : 0x23bdc5 (0x438fa800 0x14 0x19cb07 0x0)
0x415c3cb8 : 0x23db47 (0x438fa800 0x14 0x6 0x0)
0x415c3dd8 : 0x23db83 (0x438fa800 0x0 0x6 0xb994)
0x415c3df8 : 0x229b3e (0x2 0x438fa800 0x415c3e48 0x14219
0x415c3e38 : 0x218b47 (0x2 0x438fa800 0x415c3e68 0x5935cb5
0x415c3ec8 : 0x215202 (0x5ae1e04 0x2 0x438fa800 0x3eabf2)
0x415c3ef8 : 0x21595b (0x52ad64 0x546fe88 0x2 0x415c3f74)
0x415c3f68 : 0x215bb9 (0x0 0x438fa800 0x0 0x58f3f2c)
0x415c3fc8 : 0x1a017c (0x58f3f04 0x0 0x1a30b5 0x588604
Backtrace terminated-invalid frame pointer 0
BSD process name corresponding to current thread: kernel_task
Mac OS version:
9G55
Kernel version:
Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; rootnu-1228.9.59~1/RELEASE_I386
System model name: MacBook2,1 (Mac-F4208CA9)
Can anybody help me?
Thanks already...Henning
EDIT: I tested the memory in OSX with rember and the TechTool Deluxe.
Message was edited by: commanderchen

I might have found a solution: memtest86 found on linux dvds/cds doesn't seem to be suitable for Intel Macs. There is a port for Intel Macs: http://matt.ucc.asn.au/memtest/
This program blocks the first 1.2MB, where information concerning Boot Camp are located, which cause errors in the normal memtest86. More information in the link given above.
That's why I received those much error messages. That's also why a memory test within OSX didn't show errors. The test is now running for 14mins and no error has occurred yet.
But can anyone read any information from the panic log?

Kernel[0]: SMC::smcReadKeyAction ERROR TC0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff8037fe0000

Similar Messages

Maybe you are looking for