Kernel Panic! Please help, log included

Discussion in 'Mac Pro' started by movvvie, Nov 9, 2012.

  1. movvvie macrumors newbie

    Nov 9, 2012
    I'm working on a very old Mac Pro:
    2,1, Quad Core, 3ghz, Boot ROM Version:MP21.007F.B06 SMC Version (system): 1.15f3, Mac OS 10.5.8

    It started to Kernel Panic today. It's now had to be shut down about 15 times. I've tried reinstalling ram (3rd party), running disk permissions and repair in disk utility, checking the computer firmware, throwing out permissions for final cut studio, and booting up in safe more.
    Nothing has helped, except for unplugging the 4 esata raids I have connected via 2 3rd party Sonnet Tempo Sata E2P cards. So far it has not panicked for about an hour without the drives mounted. But these drives have been working fine several months with this esata card, I've not installed or updated any software recently. So I'm assuming its the drives or the card, but would appreciate any suggestions for what I can do. I'm working on a documentary with hundreds of hours of footage on these drives I need to access. Thanks very much for any advice.

    Interval Since Last Panic Report: 2927 sec
    Panics Since Last Report: 8
    Anonymous UUID: 318341A0-AF0B-48CF-A14A-BB9321F2A18E

    Fri Nov 9 18:24:32 2012
    panic(cpu 5 caller 0x001AB0FE): Kernel trap at 0x00619f95, type 14=page fault, registers:
    CR0: 0x8001003b, CR2: 0x6ffb77bf, CR3: 0x014df000, CR4: 0x00000660
    EAX: 0x6ffb77bf, EBX: 0x6ffb781b, ECX: 0x6ffb77bf, EDX: 0xb892a194
    CR2: 0x6ffb77bf, EBP: 0x83e5bd18, ESI: 0xa8458b00, EDI: 0x30000000
    EFL: 0x00010a87, EIP: 0x00619f95, CS: 0x00000008, DS: 0x00000010
    Error code: 0x00000000

    Backtrace (CPU 5), Frame : Return Address (4 potential args on stack)
    0x83e5baf8 : 0x12b4c6 (0x45f91c 0x83e5bb2c 0x13355c 0x0)
    0x83e5bb48 : 0x1ab0fe (0x469a98 0x619f95 0xe 0x469248)
    0x83e5bc28 : 0x1a1713 (0x83e5bc40 0x80000096 0x83e5bd18 0x619f95)
    0x83e5bc38 : 0x619f95 (0xe 0x48 0x470010 0x10)
    0x83e5bd18 : 0x61efcd (0xa8458b00 0xb892a194 0x30000000 0x83e5bd40)
    0x83e5bd98 : 0x61f138 (0x800a00 0x3000000 0xb892a194 0x30000000)
    0x83e5be08 : 0x61f5b5 (0x6bc6c05c 0xc2114c0 0x1 0x94a192b8)
    0x83e5be98 : 0x6244a6 (0x6bc6c05c 0xc2114c0 0x0 0x83635008)
    0x83e5bef8 : 0x61a69e (0x6bc6c05c 0x2c977ae7 0x0 0xc056b58)
    0x83e5bf18 : 0x426bfb (0xc0d8000 0xc0cc080 0x1 0x19fed4)
    0x83e5bf68 : 0x425d58 (0xc0cc080 0x522b60 0x83e5bfc8 0x13ec8f)
    0x83e5bf98 : 0x425a3a (0xc0e7f80 0xbf5e680 0xc0ad208 0x132386)
    0x83e5bfc8 : 0x1a14fc (0xc0e7f80 0x0 0x1a40b5 0xbee1720)
    Backtrace terminated-invalid frame pointer 0
    Kernel loadable modules in backtrace (with dependencies):

    BSD process name corresponding to current thread: kernel_task

    Mac OS version:

    Kernel version:
    Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386
    System model name: MacPro2,1 (Mac-F4208DA9)

    System uptime in nanoseconds: 644826636626
    unloaded kexts: 2.4.0 - last unloaded 246356948527
    loaded kexts:
    com.SiliconImage.driver.Si3132 1.2.5 1.9d0 - last loaded 34523004256 2.4.0 2.0.2 1.7.1a2 2.1.9f10 2.7.5 5.4.8 1.7.1a2 1.7.1a2 6.0.3 1.7.1a2 1.7.7 1.0.6 1.1.7 3.4.0a17 1.3.1 1.0.0d28 5.4.8 2.1.9f10 1.0 1.0.9b4 2.1.9f10 3.5.2 2.0.9 2.1.1 2.7.91 1.5.3 1.2.2 3.4.9 3.9.7 3.5.2 1.1.0 1.7.0 2.0.1 367.91.22 2.1.2b1 3.4.6 3.5.2 1.2.0 1.2.5 1.2.3 1.4 1.2.5 1.4 1.2.5 1.4 107.12 1.8.77 3 76.2.0 199 30.4 9.4 1.7.1a2 1.7.1a2 1.6.9fc5 1.1 3.4.0a17 2.3.1d1 5.4.8 1.7.3 1.7.3 2.1.9f10 2.1.9f10 3.4.6 3.2.0 2.1.1 2.1.1 1.5 1.5 1.5 1.5.2 2.1.1 3.4.9 1.5.0 2.0.1 216.1 1.6.1 3.5.2 1.2.0 1.1 1.5.6 1.5.5 1.2.5 2.6 1.2.0
  2. Asgorath macrumors 65816

    Mar 30, 2012
  3. movvvie thread starter macrumors newbie

    Nov 9, 2012
    Thanks very much, I can try updating to newer OS, is there anything in particular in the Kernel Panic log that leads you to think that would help, or is it just a general suggestion?
  4. derbothaus macrumors 601


    Jul 17, 2010
    Try to update the silicon image driver for the eSATA cards. Or as stated update the OS to something the manufacturer supports. If already supported, what in your system has changed to make it unstable?
  5. 666sheep macrumors 68040


    Dec 7, 2009
    Silicon driver has crashed and if it was working OK until this time, it could be one of your drives or their enclosures. Connect each one separately and you should trace one causing KP. If each one will cause KP, then problem is the card itself.

Share This Page