Forums Search Login Register
New Posts Todays Posts Find Users Posts Unanswered Threads Help Mark Forums as Read

Thread Options  Subscribe to this thread Subscribed Users  Add Reply 
Posts: 2,814
Kernel Panic after updating.

I get following kernel panic message when I updated the Mac v 10.6.4 to v10.6.8.

Error Message.

[SleepEnabler] Registering PowerManagement dispatch table...
Panic (CPU 0 caller<hex value): "Version mis-match between kernel (23) and CPU PM (18)" @/SourceCache/xnu/xnu/-1504.15.3/osfmk/i386/pmcpu.c: 771
Debugger Called:<panic>

I do realize that there is a mismatch between kernel and pm

After going to the safe mode I tried to recover the kernel but no, success.

So, can someone help me with the issue.

Thanks in advance for the suggestions.:apple:
07-28-2011, 02:00 PM
Subscribe to this thread Subscribed Users  Add Reply 

Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  my system is in continous kernel panic wsusannahmccyyy 1 626 02-07-2018 10:47 PM
Last Post: Monday12
  Kernel flaw allowing Full-system compromise orileekidd 0 69 01-02-2018 08:33 PM
Last Post: orileekidd
  Unable to capture kext logs in kernel.log 10.6 (Snow Leopard) MarkC1942 0 255 10-14-2016 11:02 AM
Last Post: MarkC1942
  Kernel panic tintan253 0 178 10-02-2016 07:37 AM
Last Post: tintan253
  2012 MBP - Kernel Panic - Cant find cause bfrankgonzaluuu 0 207 08-25-2016 06:44 PM
Last Post: bfrankgonzaluuu
  Kernel Task Extremely High CPU JerrieKasica 0 197 08-25-2016 09:34 AM
Last Post: JerrieKasica
  Spotify Kernel Panic Bug on OS X (also for web browser/iOS?) Wilma 0 205 05-02-2016 02:37 AM
Last Post: Wilma
  Moving from external to internal, updating paths? vbasilshawh 0 199 12-12-2014 08:00 AM
Last Post: vbasilshawh
  Updating from 10.5.8 JerrieKasica 0 232 09-01-2014 08:57 PM
Last Post: JerrieKasica
  Help Kernel panics lkeridunuuue 0 276 08-01-2014 06:35 AM
Last Post: lkeridunuuue

Forum Jump:

User(s) browsing this thread: 1 Guest(s)

Contact Us Privacy Policy Top RSS
Forum Software By: MyBB, © 2002-2018