Okay, I updated to Mac OS 10.6.5 yesterday and all seemed well. Today I had my somewhat usual Applications open (iChat, Mail, Safari, iTunes, Photoshop, Dashcode, and Final Cut Express Exporting) and when I went to save the Photoshop image it froze. After thinking only photoshop froze i tried to do the command, option, escape command to bring up the force quit menu but realized it wouldn't open. I tried to go to the Apple menu but when I dragged my mouse off of the Photoshop window I realized finder had a beachball also. Even the menu bar and dock. No response from Exposé either. After about 5 minutes of everything just frozen it finally kernel panicked. When I rebooted the system it took about 5 minutes to boot which is long. After it booted I went to console and looked at the log file. This is what it says:
+panic(cpu 1 caller 0x28f16b): "pmap
flushtlbs() timeout: "P"cpuanic(Cin 0)o res oUn to entspousiv,e promesaps+
Is this a serious issue? Last time I had a kernel panic back in January 2010 my hard drive needed to be replaced.
Thanks,
[Bryan W.|http://bryanw0104.tk]
MacBook Pro (Late 2008),
Mac OS X (10.6.5),
iPhone 4, iPod Touch G3, iPod Nano G3, and iPod Nano G2
Did you repair permissions and restart your computer prior to and after the OS update? Not sure on how serious it is, but try repairing disk permissions using Disk Utility. If it won't repair you may need to repair disk permissions using the original installation disk. If you are worried about the integrity of your disk, run verify disk, again from Disk Utility. If it was me I'd run them both from your installation disk just to be sure. Sometimes these things just happen - maybe you've had a hard shutdown or two or it's been a while since you did a restart - gremlins just seem to creep into the system over time.
What I meant was that if you only sleep your computer each night, over a period of time things seem to get corrupted. After a month or so of just sleeping my machines, I usually shut them down and reboot just to get things humming again. I always repair permissions and then reboot prior to any software install. It's a good idea to repair permissions again after any major software install. Repairing Permissions from the original installation disk has always fixed my machines after a kernel panic. Good luck!
What I mean William, is that machines do become corrupted over time while they are running, not necessarily just while they are sleeping. It's why so many problems can be solved with a simple reboot. I believe you would be one of the very few people who have "never had any issues". Never had an incorrect permission, corrupt preference file, a peripheral or application crash? Yeah right!
I have the same issue. Installing 10.6.5 seems to cause kernel panic on my MacBook Pro (Mid 2009).
I restarted/reinstalled a few times, with all the repairs/permission fixes (can some expert tell me if this is really necessary?). Even replaced the hard drive. But the only trigger to Kernel Panic seems the installation of 10.6.5. Installing 10.6.4 combo now.
I have the same issue with MBP mid 09. Kernel panics on restart with 10.6.5 update via both Software Update and Combo update. Going back to 10.6.4 until I hear this issue is resolved.
For you also, if the update's causing the KPs, then something's amiss that is only triggered by more stringent requirements, usually associated with RAM. Run the AHT and Rember.
Today I found my first Kernel Panic. My MBP 13" came with the stock standard 4GB DDR3 memory. I upgraded the memory to Corsair DDR3 - 2x 4GB modules. All has been going fine, until today I brought the computer out of sleep model and suddenly I get the Kernel Panic box for the first time. I ran multiple diagnostics with the power button and Command keys, etc but nothing seem to fix it. I got home ran the Diagnostic disc and within a few seconds I got this message:
Alert! Apple Hardware Test has detected an error. 4MEM/1/40000000 0xa9f73618. I then swapped the RAM that was in that slot with another of the same - re-ran the diagnostic no issues. Put the original module back in and the error re-appeared. Suffice to say this indicates one of the memory modules is faulty. In now running on 4GB and will be sending the faulty module back under its lifetime warranty.
This thread has been closed by the system or the community team.
You may vote for any posts you find helpful, or search the Community for additional answers.
Kernel Panic In Mac OS 10.6.5
Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.