Mac Pro 1. Generation, Sudden Reboot, Kernel Panics

Discussion in 'Mac Pro' started by icyderguru, Dec 8, 2009.

  1. icyderguru macrumors member

    Apr 20, 2008
    Hi Guys,

    i am having a little trouble with my Mac Pro 1. Generation.

    System Specs

    8 x 3 GHZ, BSEL Mod (2,4 GHZ to 3 GHZ)
    32 GB Ram
    3x Blackmagic Intensity Pro
    ATI 4870, 1GB
    4x 500GB HDD
    OS: 10.5.8

    I believe that the Mac Pro PSU is to weak because after using power from a second psu just for the 4870 i have far less kernel panics and reboots.

    After taking out the 4870 and putting in the 7300 GT, i dont have any Kernel Panics any more and just sudden reboots.

    Here is one of the Kernel panics i got, in another one it says something about simple lock deadlock detection but i didnt save the other one. After sudden reboots i get no log message.
    Mon Nov 30 14:21:53 2009
    panic(cpu 0 caller 0x00194B15): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x542600 cpus_to_respond=0xc"@/SourceCache/xnu/xnu-1228.15.4/osfmk/i386/pmap.c:4582
    Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
    0x9fb6e548 : 0x12b4c6 (0x45f91c 0x9fb6e57c 0x13355c 0x0) 
    0x9fb6e598 : 0x194b15 (0x465c58 0x542600 0xc 0x17f429) 
    0x9fb6e608 : 0x195cc2 (0x542600 0x87a97000 0x0 0x1aa1f8) 
    0x9fb6e6a8 : 0x1750ec (0x1ebcd6 0x0 0x9fb6e6c8 0x1a436f) 
    0x9fb6e748 : 0x16ab90 (0x2ab12b7c 0x0 0x0 0x3000) 
    0x9fb6e868 : 0x16b18d (0x87a9a000 0x0 0x1 0x0) 
    0x9fb6e8a8 : 0x16538f (0x1cede88 0x87a97000 0x0 0x87a9a000) 
    0x9fb6e8e8 : 0x12fe84 (0x1cede88 0x87a97000 0x2130 0x0) 
    0x9fb6e908 : 0x3f39f9 (0x87a97000 0x2130 0x18 0x2d291900) 
    0x9fb6e928 : 0x3f14a4 (0x2cacbaa0 0x0 0x1 0x3f36a7) 
    0x9fb6e948 : 0x3f1571 (0x2cacbaa0 0x0 0x2d291904 0x3f375f) 
    0x9fb6e968 : 0x430cbe (0x2cacbaa0 0x2d3a7700 0x246 0x878c4100) 
    0x9fb6e988 : 0x3f14a4 (0x2d291900 0x0 0x1 0x3f17a4) 
    0x9fb6e9a8 : 0x3f1571 (0x2d291900 0x0 0x2b919d84 0x878c4100) 
    0x9fb6e9c8 : 0x96280879 (0x2d291900 0x0 0x0 0x3ef2c2) 
    0x9fb6e9e8 : 0x96281091 (0x286d2300 0x878c4100 0x9fb6ea28 0x9fcb92c8) 
    	Backtrace continues...
          Kernel loadable modules in backtrace (with dependencies):
    BSD process name corresponding to current thread: Wirecast
    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: MacPro1,1 (Mac-F4208DC8)
    System uptime in nanoseconds: 10182788660804
    unloaded kexts:	1.0 - last unloaded 5198851295019
    loaded kexts:
    de.zdnet.kext.overclock	1.0.0d1 - last loaded 5260150978682
    com.parallels.kext.prl_vnic	4.0 3846.436204
    com.parallels.kext.prl_netbridge	4.0 3846.436204
    com.parallels.kext.prl_usb_connect	4.0 3846.436204
    com.parallels.kext.prl_hid_hook	4.0 3846.436204
    com.parallels.kext.prl_hypervisor	4.0 3846.436204
    com.bresink.driver.BRESINKx86Monitoring	3.1
    com.vara.driver.VaraAudio	1.0.2
    com.Cycling74.driver.Soundflower	1.4.3
    com.blackmagic-design.iokit.IntensityDriver	3.3.2
    jp.plentycom.driver.SteerMouse	3.9	1.5.5	9.0.2	4.7.1	2.0.2	2.7.5	199	5.4.8	1.9d0	1.7.1a2	6.0.3	2.1.2b1	1.7.1a2	1.7.7	1.0.6	5.4.8	2.6.4b17	1.1.7	3.4.0a17	1.3.1	3.2.0	3.0.19	2.7.91	2.1.1	2.1.1	1.5.3	3.4.9	1.2.2	3.5.2	3.9.7	1.2.0	3.4.6	1.7.0	2.0.1	3.5.2	1.2.5	1.2.3	1.4	1.2.5	1.4	1.2.5	1.4	107.12	1.6.77	3	76.2.0	30.4	1.7.1a2	1.7.1a2	1.6.1	1.7.3	3.4.0a17	2.3.1d1	1.6.9fc5	1.7.3	9.4	1.1	3.4.6	1.5	2.1.1	1.5	1.5	2.1.1	3.4.9	1.5.6	1.5.0	2.0.1	3.5.2	1.2.0	1.1	1.5.5	1.2.5	1.2.0	2.6
  2. cryingrobot macrumors regular

    Mar 26, 2008
    Not for me

    i dont think it is the 4870 as I have this in my Mac Pro 1.1 with 4 1 terrabyte hds and have not had problems. You might want to check that it is firmly in the slot and both power connectors are secure.
  3. bozz2006 macrumors 68030


    Aug 24, 2007
    I would first suspect your processors, and not just the processors, but specifically the BSEL mod. I have never encountered anyone who has attained a stable machine while employing the BSEL mod.
  4. Dr.Pants macrumors 65816


    Jan 8, 2009
    I would install the latest drivers from Blackmagic for your capture cards if you haven't already and see if that helps any. If not, remove your capture cards and see if you continue to get reboots.

    Furthermore, I would also take the time to run Memtest to see if the memory in your machine was working correctly.

    A quick Google search yielded that there were a good amount of problems with Wirecast on Mac - I would bet that its the problem.

    Also, some more searching put me under the impression that 9L31a is the latest 10.5.8 build, and maybe you should be using that versus 9L30. Probably wouldn't do anything, but always nice to have your machine running with the most updated software.

    Oops. Didn't see that until after I posted. Erm, yeah, that's also a source of problems.
  5. icyderguru thread starter macrumors member

    Apr 20, 2008
    I replaced the 4 x 500 Gigabyte, Raid 0, Hard Drives with 2 x 2 Terrabyte in Raid 1, installed Snow Leopard and migrated all my data, it is rock stable now.

    Still i do not know what exactly was the reason for the kernel panics and sudden reboots. So its either software (Leopard vs Snow Leopard) or hardware (hard drives) related.

    Maybe one of my hard drives was failing, triggering weird panics. I searched quite a lot on the internets regarding my specific kernel panic but i didnt really came up with much.

    Its nice to have a stable system again. :cool:
  6. drrbc macrumors newbie

    Oct 29, 2009
    Bring out your dead....

    Sorry couldn't resist.

    May I suggest that since BSEL mod "fixes" the FSB to one speed, the ZDNet overclock.kext that you were using on a fixed FSB was causing a schizophrenic break in your MCH as it tried to get data in and out of the 3 PCI cards?

    Because SL going from 32 to 64 bit would have fixed that.

    But what I really think is that it's a DTS interrupt. That may have also been fixed with a new HPET.kext from SL. Dunno.

    Also, when trouble shooting remember to pull your PCIe cards and replacing one at a time. Oh, SMC resets too.

    PS- hey bozz, I'm running bsel'd 5350's at 3.3 ghz in a 1,1. Rock solid.

Share This Page