Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Flash SWT

macrumors 6502
Original poster
Mar 14, 2009
459
23
Houston, TX
Howdy folks, I ran into a problem when updating my Mac Pro 4,1 tonight that I'm hoping y'all can help with. The first mistake I made was trying to update two things at once, I should have known better (because it makes trouble shooting so much more complicated).

I added an additional 8 GB of OWC RAM (adding 2x4GB sticks alongside the 6x2GB I already had). At the same time I added a Samsung 840 Pro 256 GB SSD into the lower optical bay slot. The drive itself seems to be OK, it is recognized and usable when dropped in a Voyager Q dock.

To make a long story short, after going one stick at a time the RAM all appears to be fine, the computer sees all 20 GB now and seems to be running OK without the SSD plugged in so I don't think the RAM is the problem.

Whenever the empty but formatted SSD is connected the computer starts acting really weirdly. It booted a few times but then the display would go blank after only a couple minutes. When this happened power remained on but I had to hold down the button to power off since I couldn't tell what was happening with the machine. It also restarted on it's own at least once.

The most concerning thing however is that several times when the computer was started up the fans would start "revving." By that I mean they would go full speed, then slow/normal, then full, then slow: VROOM, calm, VROOM, calm, etc. This happened immediately after power on and I never even got a startup chime, eventually just holding down the button to power off.

At first I thought I had damaged something during the upgrade process. I reseated all the RAM and the video card but it still persists. However unplug the SSD and the computer seems to be running like normal again.

Is there a known issue with adding an SSD to the lower optical bay slot? Some sort of jumper or something that I needed to adjust?

Thanks for taking the time to read all this, I appreciate any suggestions y'all might have. I did manage to get two different "system crash logs" when I rebooted and have included parts of them below.

Code:
panic(cpu 8 caller 0xffffff8006cb7bd5): Kernel trap at 0xffffff7f88f450b8, type 0=divide error, registers:
CR0: 0x000000008001003b, CR2: 0x00000001092c8b90, CR3: 0x000000001e658000, CR4: 0x0000000000000660
RAX: 0x000000000009c3ec, RBX: 0xffffff82480cbb38, RCX: 0xffffff7f88fd2200, RDX: 0x0000000000000000
RSP: 0xffffff82480cbb10, RBP: 0xffffff82480cbb20, RSI: 0xffffff7f88fd22d0, RDI: 0x0000000000000000
R8:  0x0000000000000000, R9:  0xffffff7f88fd22f0, R10: 0x0000000012a00200, R11: 0x0000000000000246
R12: 0xffffff7f88fd2490, R13: 0x0000000000000027, R14: 0xffffff82480cbb72, R15: 0xffffff82480cbb38
RFL: 0x0000000000010246, RIP: 0xffffff7f88f450b8, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000001092c8b90, Error code: 0x0000000000000000, Fault CPU: 0x8

Backtrace (CPU 8), Frame : Return Address
0xffffff82480cb7b0 : 0xffffff8006c1d626 
0xffffff82480cb820 : 0xffffff8006cb7bd5 
0xffffff82480cb9f0 : 0xffffff8006cce4ed 
0xffffff82480cba10 : 0xffffff7f88f450b8 
0xffffff82480cbb20 : 0xffffff7f88f45a2a 
0xffffff82480cbbc0 : 0xffffff7f88f422ad 
0xffffff82480cbbf0 : 0xffffff7f88f410bb 
0xffffff82480cbc30 : 0xffffff7f8910f0c7 
0xffffff82480cbc50 : 0xffffff7f89420367 
0xffffff82480cbc80 : 0xffffff7f8941ad33 
0xffffff82480cbcb0 : 0xffffff7f8729c6ce 
0xffffff82480cbd40 : 0xffffff7f87294e00 
0xffffff82480cbd70 : 0xffffff8007033dbb 
0xffffff82480cbdc0 : 0xffffff8007063ff7 
0xffffff82480cbe30 : 0xffffff8006c97d2f 
0xffffff82480cbe80 : 0xffffff8006c20aed 
0xffffff82480cbeb0 : 0xffffff8006c10448 
0xffffff82480cbf00 : 0xffffff8006c1961b 
0xffffff82480cbf70 : 0xffffff8006ca5b16 
0xffffff82480cbfb0 : 0xffffff8006cced53 

Model: MacPro4,1, BootROM MP41.0081.B07, 8 processors, Quad-Core Intel Xeon, 2.26 GHz, 12 GB, SMC 1.39f5
Graphics: ATI Radeon HD 4870, ATI Radeon HD 4870, PCIe, 512 MB
Memory Module: DIMM 2, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314431
Memory Module: DIMM 3, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314631
Memory Module: DIMM 4, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314431
Memory Module: DIMM 6, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314431
Memory Module: DIMM 7, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314631
Memory Module: DIMM 8, 2 GB, DDR3 ECC, 1066 MHz, 0x802C, 0x31384A53463235363732415A2D3147314431
PCI Card: ATI Radeon HD 4870, sppci_displaycontroller, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: Samsung SSD 840 PRO Series, 256.06 GB

Code:
panic(cpu 12 caller 0xffffff801969db1b): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x10, NMIPI acks: orig: 0x0, now: 0x0"@/SourceCache/xnu/xnu-2050.18.24/osfmk/x86_64/pmap.c:2337
Backtrace (CPU 12), Frame : Return Address
0xffffff817b1639d0 : 0xffffff801961d626 
0xffffff817b163a40 : 0xffffff801969db1b 
0xffffff817b163ac0 : 0xffffff80196a2330 
0xffffff817b163b80 : 0xffffff80196a2b65 
0xffffff817b163bd0 : 0xffffff8019666a1c 
0xffffff817b163cc0 : 0xffffff801966cc42 
0xffffff817b163dc0 : 0xffffff801961a50b 
0xffffff817b163e50 : 0xffffff801964f9e0 
0xffffff817b163e80 : 0xffffff8019620aed 
0xffffff817b163eb0 : 0xffffff8019610448 
0xffffff817b163f00 : 0xffffff801961961b 
0xffffff817b163f70 : 0xffffff80196a5b16 
0xffffff817b163fb0 : 0xffffff80196ced53 

BSD process name corresponding to current thread: System Informati
 
Last edited:

Flash SWT

macrumors 6502
Original poster
Mar 14, 2009
459
23
Houston, TX
Hmmm, well I guess chalk this one up to gremlins or a ghost in the machine. It seems to be behaving itself with everything reassembled. I'm gonna wait a few days before migrating my system/applications over to the SSD just to make sure there aren't any other hiccups.

Thanks for taking the time to read if you made it this far.
 

wonderspark

macrumors 68040
Feb 4, 2010
3,048
102
Oregon
I think that if you can shut down and boot up repeatedly with no problems, you're safe to proceed, but I understand erring on the side of caution. :p
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.