Kernil Panic every few hours!

Discussion in 'macOS' started by ammami, Jan 7, 2009.

  1. ammami macrumors newbie

    Jan 7, 2009
    My MacBook Pro is giving me a kernel panic every few hours. Here's the log, help please!

    Wed Jan 7 13:22:07 2009
    panic(cpu 0 caller 0x0019EB7E): "simple lock deadlock detection: lock=0x522b20, cpu=0, owning thread=0x52a76b0"@/SourceCache/xnu/xnu-1228.9.59/osfmk/i386/locks_i386.c:317
    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    0x47b87ca8 : 0x12b4f3 (0x45b13c 0x47b87cdc 0x1335e4 0x0)
    0x47b87cf8 : 0x19eb7e (0x462c18 0x522b20 0x0 0x52a76b0)
    0x47b87d18 : 0x13ecf0 (0x522b20 0xf 0xf 0xa)
    0x47b87d58 : 0x860fae (0x5a20000 0x58e1b30c 0xa46 0x5b07000)
    0x47b87db8 : 0x8622fb (0x5b07000 0x57be4250 0xa46 0x3eabf2)
    0x47b87df8 : 0x861cef (0x5b07000 0x47b87e6c 0x47b87e28 0x3dea84)
    0x47b87e38 : 0x86c8c5 (0x5b07000 0x47b87e6c 0x47b87e88 0x1404af)
    0x47b87e98 : 0x6aefce (0x5b07000 0x5b0f8c0 0x1 0x47b87ee0)
    0x47b87f18 : 0x4224ff (0x599d100 0x5b10700 0x1 0x19eb5b)
    0x47b87f68 : 0x42165c (0x5b10700 0x0 0x1 0x136e3e)
    0x47b87f98 : 0x42133e (0x5b104c0 0x47b87fdc 0x47b87fc8 0x1a8ddc)
    0x47b87fc8 : 0x1a017c (0x5b104c0 0x0 0x1a30b5 0x107480e0)
    Backtrace terminated-invalid frame pointer 0
    Kernel loadable modules in backtrace (with dependencies):>0x877fff

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 9.6.0: Mon Nov 24 17:37:00 PST 2008; root:xnu-1228.9.59~1/RELEASE_I386
    System model name: MacBookPro2,1 (Mac-F42189C8)
  2. Mal macrumors 603


    Jan 6, 2002
    Do you have any peripherals connected to the machine? Disconnect everything but the keyboard and mouse and see if the problems stop. Your error log references I/O, so that's a good thing to look at. Also, if this is a tower, check your PCI cards, they may be prompting the errors as well.

    If you can, it's also usually a good idea to start up from another source (external drive, CD, etc) and see if the problems persist. If not, it could be software.


Share This Page