The Console.app found in the Application -> Utilities folder (or Other folder in Launchpad) gives you access to the logs for the machine.
Under /var/log, the file named install.log (and any variants named install.log.x.bz2) will give you the information about the last install.
Note the files named install.log.x.bz2 are older versions of the same file created duting a process called rolled over when the file size of the current install.log file reaches 1000K
You need to search your install.log for the string "OSXUpd10.8.2Supp.pkg" which will give you an idea of what happened during your install.
Update: From your log file, it would appear that your have a Kernel Extension that is causing this issue. Either it has a permissions problem, or is somehow causing this annoying issue.
can you paste this line into Terminal, and post the results?
kextstat -kl | awk ' !/apple/ { print $6 $7 } '
Update 2: This would appear to be at least a trial and error solution. There are multiple threads on the Apple Support forums, from installing 10.8.2 to installing Xcode. Each one has different people each having issues with different kernel extensions that when removed resolved their issues.
I'm afraid I don't have any way to determine which of your kernel extensions is the cause; someone else may be able to shed more light. I would however expect the Virtual Box and Parallels extensions to be fine, not the least since I have them both also, but that this issue would be more widespread if they were the issue.
Finally: the manual for kextcache advises that using the touch command on /System/Library/Extensions/ forces the kext cache to be rebuilt. You could use this as a method to determine which kext is causing the issue by uninstaling each in turn, performing the cache update and checking the logs to see if the cache was updated successfully.
First, try starting the machine in Safe Mode to re-confirm that this is a third party software issue and not related to hardware:
- Shut down your Mac and wait 10 seconds.
- Press the power button.
- Immediately after you hear the startup tone, hold down the Shift key.
You should press the Shift key as soon as possible after you hear the startup tone, but not before.
- Release the Shift key when you see the gray Apple logo and progress indicator (spinning gear).
To leave safe mode, restart the computer normally without holding down any keys during startup.
If it works fine in Safe Mode without issues, then you could try uninstalling some potential culprits seen in the log. The backtrace in your log shows the application firewall crashing. The key suspects in this case, based on what was loaded most recently, are the following:
com.speedbit.driver.vadriver 1.0.8
- Uninstall the Speedbit Video Accelerator for Mac from your system and see if it helps.
com.seagate.driver.PowSecLeafDriver_10_5 5.2.3 and com.seagate.driver.PowSecDriverCore 5.2.3
- Uninstall any Seagate Diagnostics Tool that you may have and see if it helps.
Best Answer
I have observed the same error when deploying my own signed apps. It appears that if you mv/cp a new binary over an existing signed one, the kernel does not keep track of this very well and starts generating these errors. I have found that this does not occur if the new binary is installed as part of a package, or if the original binary is deleted first and then the new binary put in place. Additionally once in this situation, a reboot fixes the issue, presumably as the kernel codesigning table is stored in memory. I appreciate rebooting may not be an option in a server environment.