Apple update 10.6.8 and Lion (10.7) cause Kernel Panics on MacPro 1,1

I bought my MacPro (MacPro 1,1) in September 2006 and nearly 5 years down the line it’s still going strong, or at least it was.

Some recent projects I’ve been involved in have required some serious processing power to render gigapixel images and the original 2xDual Core XEONs weren’t up to it. I found a matching pair of cheap E5345 QUAD core processors on eBay and fitted them (that’s another post that will be on here soon along with photos of the CPU swap out process). I threw some SSD’s in a RAID array in there for good measure too and the combination of those two things made a phenomenal difference to the rendering times. My Snow Leopard 10.6.7 install was nice and stable, not a single crash/hang/kernel panic or reboot.

Then Apple released a Snow Leopard update 10.6.8 to “ready you for Lion” so I dutifully upgraded the 10.6.7 I had installed on my SSD’s and it all went terribly wrong. The system now erratically rebooted itself and a look at the logs showed Kernel Panics all over the place. I have a second OS X 10.6.7 for emegency situations, booted into that and ran that for a few days and it was all fine. I rolled back my 10.6.8 to 10.6.7 using a TimeMachine backup and everything was stable again.

I thought it might just be a *glitch* with 10.6.8 and patiently waited for Lion. When Lion was released I decided to not take a chance upgrading my stable 10.6.7 and so I wiped 2 of the drives I had in a RAID array and installed a fresh copy of Lion which I downloaded from the App Store (if you want to know how to create a bootable Lion install from Apples Lion download leave a comment and I’ll post that soon). Even the fresh install of Lion was showing a random kernel panic every 5minutes to an hour and rebooting the system.

I thought it might be that 10.6.8 and Lion didn’t like the SSD drives that were still mounted even though they weren’t the boot drives. The MacPro 1,1 came with 4x drive sled bays for SATA hard drives but there were also another 2x hidden SATA ports on the motherboard that I connected the SSD drives to and mounted them in the spare optical bay. So I unplugged the SSD drives from the 2 hidden SATA ports and set about using 10.6.8 and Lion (each OS on a different RAID partition) but still both were rebooting because of a kernel panic. This is why everyone needs a data recovery professional friend, just like you need that plumber friend too!

I’ve opened up a report at http://bugreport.apple.com/ and they’ve requested my kernel crash logs which are in /Library/Logs/Diagnostic….

These from 10.6.8

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
Interval Since Last Panic Report: 2280 sec
Panics Since Last Report: 1
Anonymous UUID: E1843A0F-F5B9-45FC-B85E-C95CEE78EB4E

Wed Jul 20 23:29:44 2011
Machine-check capabilities (cpu 3) 0x0000000000000006:
family: 6 model: 15 stepping: 7 microcode: 0
Intel(R) Xeon(R) CPU E5345 @ 2.33GHz
6 error-reporting banks
Machine-check status 0x0000000000000005:
restart IP valid
machine-check in progress
MCA error-reporting registers:
IA32_MC0_STATUS(0x401): 0xb200004000000800 valid
MCA error code: 0x0800
Model specific error code: 0x0000
Other information: 0x00000040
Status bits:
Processor context corrupt
Error enabled
Uncorrected error
IA32_MC1_STATUS(0x405): 0x0000000000000000 invalid
IA32_MC2_STATUS(0x409): 0x0000000000000000 invalid
IA32_MC3_STATUS(0x40d): 0x0020000000000000 invalid
IA32_MC4_STATUS(0x411): 0x0000000000000011 invalid
IA32_MC5_STATUS(0x415): 0xb200120020080400 valid
MCA error code: 0x0400
Model specific error code: 0x2008
Other information: 0x00001200
Status bits:
Processor context corrupt
Error enabled
Uncorrected error
panic(cpu 3 caller 0x2aaf41): Machine Check at 0x7a03bd03, thread:0x1821c000, trapno:0x12, err:0x0,registers:
CR0: 0x8001003b, CR2: 0x01000c98, CR3: 0x00100000, CR4: 0x00000660
EAX: 0x39fe7615, EBX: 0x000005b0, ECX: 0x79fe7344, EDX: 0x00000592
ESP: 0x79c4bb70, EBP: 0x79c4bc68, ESI: 0x00000004, EDI: 0x00000003
EFL: 0x00000006, EIP: 0x7a03bd03

Backtrace (CPU 3), Frame : Return Address (4 potential args on stack)
0x7a036fb8 : 0x21b837 (0x5dd7fc 0x7a036fec 0x223ce1 0x0)
0x7a037008 : 0x2aaf41 (0x59dfe4 0x59e0d1 0x7a03bd03 0x1821c000)
0x7a0370f8 : 0x2a29f2 (0x1 0x0 0x0 0x0)
0x79c4bc68 : 0x2ad0c5 (0xffffffff 0x7fffffff 0x79c4bc98 0x7a07a000)
0x79c4bc88 : 0x225bba (0x7a07a49c 0x22e1262c 0x25e 0x7a07a488)
0x79c4bce8 : 0x22698c (0x1 0x1821c000 0xbac30dc 0x6)
0x79c4bd58 : 0x2275b0 (0x1821c01c 0x292af75d 0x25e 0xbf1a3f4)
0x79c4bdc8 : 0x227631 (0x47a699 0xbf1a3c0 0x0 0x479039)
0x79c4bde8 : 0x47a0c3 (0x47a699 0xbf1a3c0 0x2 0x292af75d)
0x79c4be68 : 0x47a58f (0xbf1a3c0 0x479039 0x479082 0xe8b408c)
0x79c4bf38 : 0x47a697 (0x0 0x0 0x0 0x380e20)
0x79c4bf78 : 0x4f82fb (0xe3f9d20 0x18200188 0xe8b4044 0x1)
0x79c4bfc8 : 0x2a251d (0x18200184 0x0 0x10 0xbde5b84)

BSD process name corresponding to current thread: Software Update

Mac OS version:
10K540

Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacPro1,1 (Mac-F4208DC8)

System uptime in nanoseconds: 2606564782259
unloaded kexts:
com.apple.driver.AppleFileSystemDriver 2.0 (addr 0x8368b000, size 0x12288) - last unloaded 99435637120
loaded kexts:
com.vara.driver.VaraAudio 1.0.3
com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 35352506056
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleBluetoothMultitouch 54.3
com.apple.driver.AudioAUUC 1.57
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.CHUDUtils 364
com.apple.iokit.CHUDProf 366
com.apple.driver.AppleUpstreamUserClient 3.5.7
com.apple.driver.AppleMCCSControl 1.0.20
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.AppleHDA 2.0.5f13
com.apple.GeForce 6.3.6
com.apple.driver.AppleIntel8254XEthernet 2.1.3b1
com.apple.driver.AppleUSBDisplays 289
com.apple.driver.AppleIntelMeromProfile 19.1
com.apple.driver.AppleMCEDriver 1.1.9
com.apple.driver.AirPortBrcm43224 428.42.4
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1
com.apple.driver.AppleLPC 1.5.1
com.apple.iokit.SCSITaskUserClient 2.6.8
com.apple.driver.AppleRAID 4.0.6
com.apple.BootCache 31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.driver.AppleUSBHub 4.2.4
com.apple.iokit.IOAHCIBlockStorage 1.6.4
com.apple.driver.AppleFWOHCI 4.7.3
com.apple.driver.AppleUSBEHCI 4.2.4
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleAHCIPort 2.1.7
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleUSBUHCI 4.2.0
com.apple.driver.AppleACPIButtons 1.3.6
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.3.6
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.12
com.apple.driver.AppleIntelCPUPowerManagement 142.6.0
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.IOBluetoothHIDDriver 2.4.5f3
com.apple.driver.AppleMultitouchDriver 207.11
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOBluetoothSerialManager 2.4.5f3
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.CHUDKernLib 365
com.apple.driver.DspFuncLib 2.0.5f13
com.apple.iokit.IOAudioFamily 1.8.3fc2
com.apple.kext.OSvKernDSPLib 1.3
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.AppleProfileFamily 41.4
com.apple.driver.AppleHDAController 2.0.5f13
com.apple.iokit.IOHDAFamily 2.0.5f13
com.apple.iokit.IO80211Family 320.1
com.apple.iokit.IONetworkingFamily 1.10
com.apple.driver.AppleSMC 3.1.0d5
com.apple.driver.IOPlatformPluginFamily 4.7.0a1
com.apple.nvidia.nv40hal 6.3.6
com.apple.NVDAResman 6.3.6
com.apple.iokit.IONDRVSupport 2.2
com.apple.iokit.IOGraphicsFamily 2.2
com.apple.driver.CSRUSBBluetoothHCIController 2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController 2.4.5f3
com.apple.iokit.IOBluetoothFamily 2.4.5f3
com.apple.driver.AppleUSBHIDKeyboard 141.5
com.apple.iokit.IOUSBHIDDriver 4.2.0
com.apple.driver.AppleHIDKeyboard 141.5
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8
com.apple.iokit.IOUSBMassStorageClass 2.6.7
com.apple.driver.AppleUSBMergeNub 4.2.4
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6.1
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOATAPIProtocolTransport 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.8
com.apple.iokit.IOUSBUserClient 4.2.4
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOAHCIFamily 2.0.6
com.apple.iokit.IOATAFamily 2.5.1
com.apple.iokit.IOUSBFamily 4.2.4
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.6
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.TMSafetyNet 6
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.3
com.apple.driver.AppleACPIPlatform 1.3.6
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily 1.3.0
System Profile:
Model: MacPro1,1, BootROM MP11.005C.B08, 8 processors, 2.33 GHz, 7 GB, SMC 1.7f10
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.131.42.4)
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce 7300 GT, sppci_displaycontroller, Slot-1
Serial ATA Device: WDC WD1001FALS-00J7B1, 931.51 GB
Serial ATA Device: WDC WD1001FALS-00J7B1, 931.51 GB
Serial ATA Device: ST3500630AS, 465.76 GB
Serial ATA Device: ST3500630AS, 465.76 GB
Serial ATA Device: OCZ-VERTEX2, 55.9 GB
Serial ATA Device: OCZ-VERTEX2, 55.9 GB
Parallel ATA Device: PIONEER DVD-RW DVR-111D
USB Device: Hub, 0x05ac (Apple Inc.), 0x9132, 0xfd400000 / 3
USB Device: USB2.0 Card Reader, 0x090c (Silicon Motion, Inc. - Taiwan), 0x6107, 0xfd410000 / 5
USB Device: Apple Cinema HD Display, 0x05ac (Apple Inc.), 0x9232, 0xfd420000 / 4
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd300000 / 2
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0xfd320000 / 6
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8206, 0x5d200000 / 2
FireWire Device: built-in_hub, Up to 800 Mb/sec

another

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
Interval Since Last Panic Report: 13732 sec
Panics Since Last Report: 1
Anonymous UUID: E1843A0F-F5B9-45FC-B85E-C95CEE78EB4E

Fri Jul 22 17:19:50 2011
Panic(CPU 0): Unresponsive processor, TLB state:1
EAX: 0x48e39244, EBX: 0x0000367c, ECX: 0xd3a1c3c0, EDX: 0x0000365f
CR2: 0x00138000, EBP: 0x0010bee8, ESI: 0x0b8c6000, EDI: 0x00000001
EFL: 0x00000002, EIP: 0x7a040884, CS: 0x00000008, DS: 0x00810010
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x10bd78 : 0x2b32c3 (0x10be20 0x732a70e4 0x10bdf8 0xcb797a8)
0x10bda8 : 0x2ab423 (0x2 0x10be20 0xc68795c 0x2a0577)
0x10be08 : 0x2a1da5 (0x10be20 0x22aeb4ec 0x10be38 0x2314da)
0x10bee8 : 0x7a3665bb (0xbb14d00 0x0 0xbaefb80 0x1)
0x10bf18 : 0x7a09b213 (0xbacc700 0x0 0x0 0x48)
0x10bf38 : 0x7a0a6911 (0x48 0x0 0x10bf78 0x0)
0x10bf58 : 0x580d96 (0xb62da80 0x0 0xb62de00 0x48)
0x10bf78 : 0x2ab432 (0x48 0xc7a2d84 0x718 0x1)
0x10bfd8 : 0x2a1c2e (0xc7a2d84 0x0 0x0 0x2a2a5b)
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AppleAPIC(1.4)@0x7a365000->0x7a367fff
com.apple.driver.AppleACPIPlatform(1.3.6)@0x7a099000->0x7a0dbfff
dependency: com.apple.iokit.IOACPIFamily(1.3.0)@0x79ddc000
dependency: com.apple.iokit.IOPCIFamily(2.6.5)@0x79fe2000
Kernel Extensions in backtrace (with dependencies):
com.apple.driver.AppleIntelCPUPowerManagement(142.6.0)@0x7a038000->0x7a05bfff

BSD process name corresponding to current thread: AddressBookSync

Mac OS version:
10K540

Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacPro1,1 (Mac-F4208DC8)

System uptime in nanoseconds: 25669750561727
unloaded kexts:
com.apple.driver.AppleFileSystemDriver 2.0 (addr 0x836b0000, size 0x12288) - last unloaded 82630225324
loaded kexts:
com.vara.driver.VaraAudio 1.0.3
com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 20643849442
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AppleBluetoothMultitouch 54.3
com.apple.driver.AudioAUUC 1.57
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.CHUDUtils 364
com.apple.iokit.CHUDProf 366
com.apple.driver.AppleUpstreamUserClient 3.5.7
com.apple.driver.AppleMCCSControl 1.0.20
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.AppleHDA 2.0.5f13
com.apple.GeForce 6.3.6
com.apple.driver.AppleIntel8254XEthernet 2.1.3b1
com.apple.driver.AppleUSBDisplays 289
com.apple.driver.AppleIntelMeromProfile 19.1
com.apple.driver.AppleMCEDriver 1.1.9
com.apple.driver.AirPortBrcm43224 428.42.4
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1
com.apple.driver.AppleLPC 1.5.1
com.apple.iokit.SCSITaskUserClient 2.6.8
com.apple.driver.AppleRAID 4.0.6
com.apple.BootCache 31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.driver.AppleUSBHub 4.2.4
com.apple.iokit.IOAHCIBlockStorage 1.6.4
com.apple.driver.AppleFWOHCI 4.7.3
com.apple.driver.AppleUSBEHCI 4.2.4
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleAHCIPort 2.1.7
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleUSBUHCI 4.2.0
com.apple.driver.AppleACPIButtons 1.3.6
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.3.6
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.12
com.apple.driver.AppleIntelCPUPowerManagement 142.6.0
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.IOBluetoothHIDDriver 2.4.5f3
com.apple.driver.AppleMultitouchDriver 207.11
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOBluetoothSerialManager 2.4.5f3
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.CHUDKernLib 365
com.apple.driver.DspFuncLib 2.0.5f13
com.apple.iokit.IOAudioFamily 1.8.3fc2
com.apple.kext.OSvKernDSPLib 1.3
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.AppleProfileFamily 41.4
com.apple.driver.AppleHDAController 2.0.5f13
com.apple.iokit.IOHDAFamily 2.0.5f13
com.apple.iokit.IO80211Family 320.1
com.apple.iokit.IONetworkingFamily 1.10
com.apple.driver.AppleSMC 3.1.0d5
com.apple.driver.IOPlatformPluginFamily 4.7.0a1
com.apple.nvidia.nv40hal 6.3.6
com.apple.NVDAResman 6.3.6
com.apple.iokit.IONDRVSupport 2.2
com.apple.iokit.IOGraphicsFamily 2.2
com.apple.driver.CSRUSBBluetoothHCIController 2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController 2.4.5f3
com.apple.iokit.IOBluetoothFamily 2.4.5f3
com.apple.driver.AppleUSBHIDKeyboard 141.5
com.apple.iokit.IOUSBHIDDriver 4.2.0
com.apple.driver.AppleHIDKeyboard 141.5
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8
com.apple.iokit.IOUSBMassStorageClass 2.6.7
com.apple.driver.AppleUSBMergeNub 4.2.4
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6.1
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOATAPIProtocolTransport 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.8
com.apple.iokit.IOUSBUserClient 4.2.4
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOAHCIFamily 2.0.6
com.apple.iokit.IOATAFamily 2.5.1
com.apple.iokit.IOUSBFamily 4.2.4
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.6
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.TMSafetyNet 6
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.3
com.apple.driver.AppleACPIPlatform 1.3.6
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily 1.3.0
panic(cpu 4 caller 0x28fc2e): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x1, NMIPI acks: orig: 0x0, now: 0x1"@/SourceCache/xnu/xnu-1504.15.3/osfmk/i386/pmap.c:3572
Backtrace (CPU 4), Frame : Return Address (4 potential args on stack)
0x837fbaf8 : 0x21b837 (0x5dd7fc 0x837fbb2c 0x223ce1 0x0)
0x837fbb48 : 0x28fc2e (0x59a47c 0x1 0x0 0x1)
0x837fbbb8 : 0x29480b (0x11f5aae0 0x11f5ab2c 0x837fbbf8 0x2aa1a6)
0x837fbce8 : 0x29555c (0x11f5aae0 0x707000 0x1 0x7a274838)
0x837fbd58 : 0x2615b0 (0x11f5aae0 0x707000 0x1 0x789000)
0x837fbe88 : 0x261b4b (0x789000 0x1 0x0 0x0)
0x837fbec8 : 0x283c4f (0x11f47ae4 0x706000 0x1 0x789000)
0x837fbf28 : 0x4d4007 (0x11f47ae4 0x706000 0x1 0x83000)
0x837fbf78 : 0x4f82fb (0x19ffdd20 0xcf1c068 0xc4d4234 0xffffffff)
0x837fbfc8 : 0x2a251d (0xcf1c064 0x1 0x10 0xcf1c064)

BSD process name corresponding to current thread: AddressBookSync
System Profile:
Model: MacPro1,1, BootROM MP11.005C.B08, 8 processors, 2.33 GHz, 7 GB, SMC 1.7f10
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.131.42.4)
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce 7300 GT, sppci_displaycontroller, Slot-1
Serial ATA Device: WDC WD1001FALS-00J7B1, 931.51 GB
Serial ATA Device: WDC WD1001FALS-00J7B1, 931.51 GB
Serial ATA Device: ST3500630AS, 465.76 GB
Serial ATA Device: ST3500630AS, 465.76 GB
Serial ATA Device: OCZ-VERTEX2, 55.9 GB
Serial ATA Device: OCZ-VERTEX2, 55.9 GB
Parallel ATA Device: PIONEER DVD-RW DVR-111D
USB Device: Hub, 0x05ac (Apple Inc.), 0x9132, 0xfd400000 / 3
USB Device: USB2.0 Card Reader, 0x090c (Silicon Motion, Inc. - Taiwan), 0x6107, 0xfd410000 / 5
USB Device: Apple Cinema HD Display, 0x05ac (Apple Inc.), 0x9232, 0xfd420000 / 4
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd300000 / 2
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0xfd320000 / 6
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8206, 0x5d200000 / 2
FireWire Device: built-in_hub, Up to 800 Mb/sec

another

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
Tue Jul 26 04:17:41 2011
panic(cpu 4 caller 0x2b0571): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x8, NMIPI acks: orig: 0x0, now: 0x0"@/SourceCache/xnu/xnu-1699.22.73/osfmk/i386/pmap.c:3078
Backtrace (CPU 4), Frame : Return Address (4 potential args on stack)
0x8458bce8 : 0x22032e (0x6abf4c 0x8458bd08 0x229ef0 0x0)
0x8458bd18 : 0x2b0571 (0x6b46d0 0x8 0x0 0x0)
0x8458bd68 : 0x2b3e71 (0xd7012e8 0xfe14000 0x1 0xfe15000)
0x8458bde8 : 0x2b457c (0xd7012e8 0xfe14000 0x1 0x7b1f50a0)
0x8458be28 : 0x2786fa (0xd7012e8 0xfe14000 0x1 0xfe15000)
0x8458bee8 : 0x279715 (0x1 0xfe15000 0x1 0x0)
0x8458bf18 : 0x2a30eb (0xd6b3ea0 0xfe14000 0x1 0xfe15000)
0x8458bf48 : 0x566b0d (0xd6b3ea0 0xfe14000 0x1 0x1000)
0x8458bf78 : 0x5f015a (0xd6e2660 0xd535fd4 0xceba6b0 0x2355db)
0x8458bfc8 : 0x2e3977 (0xd535fd0 0x0 0x10 0x0)

BSD process name corresponding to current thread: mds

Mac OS version:
11A511

Kernel version:
Darwin Kernel Version 11.0.0: Sat Jun 18 12:57:44 PDT 2011; root:xnu-1699.22.73~1/RELEASE_I386
Kernel UUID: F8596E5D-0966-3091-AA8D-6E11CA68386F
System model name: MacPro1,1 (Mac-F4208DC8)

System uptime in nanoseconds: 5796570600972
last loaded kext at 383918076483: @filesystems.smbfs 1.7.0 (addr 0x1a77000, size 249856)
last unloaded kext at 97865579831: >PioneerSuperDrive 3.0.0 (addr 0x1fbf000, size 12288)
loaded kexts:
@filesystems.smbfs 1.7.0
>!AHWSensor 1.9.4d0
>!A!BMultitouch 66.3
@filesystems.autofs 3.0
>!AUpstreamUserClient 3.5.9
>!AMCCSControl 1.0.24
>AudioAUUC 1.59
>!AHDA 2.1.1f11
@GeForce7xxx 7.0.0
>!UDisplays 302.1.2
|IOUserEthernet 1.0.0d1
@Dont_Steal_Mac_OS_X 7.0.0
>AudioIPCDriver 1.2.0
>!AMCEDriver 1.1.9
>ACPI_SMC_PlatformPlugin 4.7.0b2
>!ALPC 1.5.1
|SCSITaskUserClient 3.0.0
>!ARAID 4.0.6
@!AFSCompression.!AFSCompressionTypeDataless 1.0.0d1
@!AFSCompression.!AFSCompressionTypeZlib 1.0.0d1
@BootCache 32
|IOAHCIBlock!S 2.0.0
>!UHub 4.4.0
>!AFWOHCI 4.8.6
>!A!I8254XEthernet 2.1.3b1
>!AAHCIPort 2.1.8
>!A!IPIIXATA 2.5.1
>AirPortBrcm43224 500.36.11
>!AEFINVRAM 1.5.0
>!UEHCI 4.4.0
>!UUHCI 4.4.0
>!AACPIButtons 1.4
>!ARTC 1.4
>!AHPET 1.6
>!ASMBIOS 1.7
>!AACPIEC 1.4
>!AAPIC 1.5
>!A!ICPUPowerManagementClient 166.0.0
@nke.applicationfirewall 3.0.30
$quarantine 1
>!A!ICPUPowerManagement 166.0.0
>!AMultitouchDriver 220.62
>IO!BHIDDriver 2.5f17
@kext.triggers 1.0
>!AAVBAudio 1.0.0d11
>DspFuncLib 2.1.1f11
@nvidia.nv40hal.G7xxx 7.0.0
@NVDAResman.G7xxx 7.0.0
|IONDRVSupport 2.3
|IOSurface 80.0
|IO!BSerialManager 2.5f17
|IOSerial!F 10.0.5
|IOAVB!F 1.0.0d22
|IOEthernetAVB!C 1.0.0d5
|IOFireWireIP 2.2.3
|IOAudio!F 1.8.3fc11
@kext.OSvKernDSPLib 1.3
>!AHDA!C 2.1.1f11
|IOGraphics!F 2.3
|IOHDA!F 2.1.1f11
>!ASMC 3.1.1d2
>IOPlatformPlugin!F 4.7.0b2
>CSRUSB!BHCI!C 2.5f17
>!U!BHCI!C 2.5f17
|IO!B!F 2.5f17
>!UHIDKeyboard 152.3
>!AHIDKeyboard 152.3
|IOUSBHIDDriver 4.4.0
>!UMergeNub 4.4.0
|IOSCSIBlockCommandsDevice 3.0.0
|IOUSBMass!SClass 3.0.0
>!UComposite 3.9.0
|IOSCSIMultimediaCommandsDevice 3.0.0
|IOBD!S!F 1.6
|IODVD!S!F 1.6
|IOCD!S!F 1.7
>XsanFilter 403
|IOATAPIProtocolTransport 3.0.0
|IOSCSIArchitectureModel!F 3.0.0
|IOFireWire!F 4.4.3
|IOUSBUserClient 4.4.0
|IOAHCI!F 2.0.6
|IOATA!F 2.5.1
|IO80211!F 400.40
|IONetworking!F 2.0
|IOUSB!F 4.4.0
>!AEFIRuntime 1.5.0
|IOHID!F 1.7.0
|IOSMBus!F 1.1
$sandbox 165
@kext.!AMatch 1.0.0d1
$TMSafetyNet 7
>DiskImages 326
|IO!S!F 1.7
>!AKeyStore 28.18
>!AACPIPlatform 1.4
|IOPCI!F 2.6.5
|IOACPI!F 1.4

another

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
Interval Since Last Panic Report: 24896 sec
Panics Since Last Report: 1
Anonymous UUID: E1843A0F-F5B9-45FC-B85E-C95CEE78EB4E

Tue Jul 26 04:27:15 2011
panic(cpu 0 caller 0x2a0663): "Spinlock acquisition timed out: lock=0xbb1701c, lock owner thread=0xcbc6b7c, current_thread: 0xbb17000, lock owner active on CPU 0x2"@/SourceCache/xnu/xnu-1504.15.3/osfmk/i386/locks_i386.c:374
Backtrace (CPU 0), Frame : Return Address (4 potential args on stack)
0x8379bde8 : 0x21b837 (0x5dd7fc 0x8379be1c 0x223ce1 0x0)
0x8379be38 : 0x2a0663 (0x59ccb0 0xbb1701c 0xcbc6b7c 0xbb17000)
0x8379be78 : 0x2269b0 (0xbb1701c 0xbb17000 0xb5cac58 0x1)
0x8379bee8 : 0x2275b0 (0xbb1701c 0x0 0x1 0x506ad1)
0x8379bf58 : 0x227631 (0x23014c 0x863ea0 0x0 0x2a45c9)
0x8379bf78 : 0x2302e6 (0x23014c 0x863ea0 0x0 0x0)
0x8379bfc8 : 0x2a179c (0x863ea0 0x0 0x10 0x0)

BSD process name corresponding to current thread: kernel_task

Mac OS version:
10K540

Kernel version:
Darwin Kernel Version 10.8.0: Tue Jun 7 16:33:36 PDT 2011; root:xnu-1504.15.3~1/RELEASE_I386
System model name: MacPro1,1 (Mac-F4208DC8)

System uptime in nanoseconds: 480903285383
unloaded kexts:
com.apple.driver.AppleFileSystemDriver 2.0 (addr 0x8369a000, size 0x12288) - last unloaded 91858845287
loaded kexts:
com.vara.driver.VaraAudio 1.0.3
com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 25624275223
com.apple.filesystems.autofs 2.1.0
com.apple.driver.AudioAUUC 1.57
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.iokit.CHUDUtils 364
com.apple.driver.AppleUpstreamUserClient 3.5.7
com.apple.iokit.CHUDProf 366
com.apple.driver.AppleMCCSControl 1.0.20
com.apple.GeForce 6.3.6
com.apple.driver.AppleBluetoothMultitouch 54.3
com.apple.driver.AudioIPCDriver 1.1.6
com.apple.driver.AppleHDA 2.0.5f13
com.apple.driver.AppleIntel8254XEthernet 2.1.3b1
com.apple.driver.AppleUSBDisplays 289
com.apple.driver.AppleIntelMeromProfile 19.1
com.apple.driver.AppleMCEDriver 1.1.9
com.apple.driver.AirPortBrcm43224 428.42.4
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0a1
com.apple.driver.AppleLPC 1.5.1
com.apple.iokit.SCSITaskUserClient 2.6.8
com.apple.driver.AppleRAID 4.0.6
com.apple.BootCache 31.1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.driver.AppleUSBHub 4.2.4
com.apple.iokit.IOAHCIBlockStorage 1.6.4
com.apple.driver.AppleFWOHCI 4.7.3
com.apple.driver.AppleUSBEHCI 4.2.4
com.apple.driver.AppleEFINVRAM 1.4.0
com.apple.driver.AppleAHCIPort 2.1.7
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleUSBUHCI 4.2.0
com.apple.driver.AppleACPIButtons 1.3.6
com.apple.driver.AppleRTC 1.3.1
com.apple.driver.AppleHPET 1.5
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.3.6
com.apple.driver.AppleAPIC 1.4
com.apple.driver.AppleIntelCPUPowerManagementClient 142.6.0
com.apple.security.sandbox 1
com.apple.security.quarantine 0
com.apple.nke.applicationfirewall 2.1.12
com.apple.driver.AppleIntelCPUPowerManagement 142.6.0
com.apple.driver.AppleProfileReadCounterAction 17
com.apple.driver.AppleProfileTimestampAction 10
com.apple.driver.AppleProfileThreadInfoAction 14
com.apple.driver.AppleProfileRegisterStateAction 10
com.apple.driver.AppleProfileKEventAction 10
com.apple.driver.AppleProfileCallstackAction 20
com.apple.iokit.IOSurface 74.2
com.apple.iokit.IOBluetoothSerialManager 2.4.5f3
com.apple.iokit.IOSerialFamily 10.0.3
com.apple.iokit.CHUDKernLib 365
com.apple.driver.IOBluetoothHIDDriver 2.4.5f3
com.apple.driver.AppleMultitouchDriver 207.11
com.apple.driver.DspFuncLib 2.0.5f13
com.apple.iokit.IOAudioFamily 1.8.3fc2
com.apple.kext.OSvKernDSPLib 1.3
com.apple.nvidia.nv40hal 6.3.6
com.apple.NVDAResman 6.3.6
com.apple.iokit.IONDRVSupport 2.2
com.apple.iokit.IOFireWireIP 2.0.3
com.apple.iokit.AppleProfileFamily 41.4
com.apple.driver.AppleHDAController 2.0.5f13
com.apple.iokit.IOGraphicsFamily 2.2
com.apple.iokit.IOHDAFamily 2.0.5f13
com.apple.iokit.IO80211Family 320.1
com.apple.iokit.IONetworkingFamily 1.10
com.apple.driver.AppleSMC 3.1.0d5
com.apple.driver.IOPlatformPluginFamily 4.7.0a1
com.apple.driver.CSRUSBBluetoothHCIController 2.4.5f3
com.apple.driver.AppleUSBBluetoothHCIController 2.4.5f3
com.apple.iokit.IOBluetoothFamily 2.4.5f3
com.apple.driver.AppleUSBHIDKeyboard 141.5
com.apple.iokit.IOUSBHIDDriver 4.2.0
com.apple.driver.AppleHIDKeyboard 141.5
com.apple.driver.AppleUSBMergeNub 4.2.4
com.apple.iokit.IOSCSIBlockCommandsDevice 2.6.8
com.apple.iokit.IOUSBMassStorageClass 2.6.7
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.8
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.6.1
com.apple.driver.XsanFilter 402.1
com.apple.iokit.IOATAPIProtocolTransport 2.5.1
com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.8
com.apple.iokit.IOUSBUserClient 4.2.4
com.apple.iokit.IOFireWireFamily 4.2.6
com.apple.iokit.IOAHCIFamily 2.0.6
com.apple.iokit.IOATAFamily 2.5.1
com.apple.iokit.IOUSBFamily 4.2.4
com.apple.driver.AppleEFIRuntime 1.4.0
com.apple.iokit.IOHIDFamily 1.6.6
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.TMSafetyNet 6
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 289
com.apple.iokit.IOStorageFamily 1.6.3
com.apple.driver.AppleACPIPlatform 1.3.6
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily 1.3.0
Model: MacPro1,1, BootROM MP11.005C.B08, 8 processors, 2.33 GHz, 7 GB, SMC 1.7f10
Graphics: NVIDIA GeForce 7300 GT, NVIDIA GeForce 7300 GT, PCIe, 256 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.131.42.4)
Bluetooth: Version 2.4.5f3, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: NVIDIA GeForce 7300 GT, sppci_displaycontroller, Slot-1
Serial ATA Device: WDC WD1001FALS-00J7B1, 931.51 GB
Serial ATA Device: WDC WD1001FALS-00J7B1, 931.51 GB
Serial ATA Device: ST3500630AS, 465.76 GB
Serial ATA Device: ST3500630AS, 465.76 GB
Serial ATA Device: OCZ-VERTEX2, 55.9 GB
Serial ATA Device: OCZ-VERTEX2, 55.9 GB
Parallel ATA Device: PIONEER DVD-RW DVR-111D
USB Device: Hub, 0x05ac (Apple Inc.), 0x9132, 0xfd400000 / 4
USB Device: Apple Cinema HD Display, 0x05ac (Apple Inc.), 0x9232, 0xfd420000 / 5
USB Device: Keyboard Hub, 0x05ac (Apple Inc.), 0x1006, 0xfd300000 / 3
USB Device: Apple Keyboard, 0x05ac (Apple Inc.), 0x0221, 0xfd320000 / 6
USB Device: U3 Titanium, 0x0781 (SanDisk Corporation), 0x5408, 0xfd200000 / 2
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8206, 0x5d200000 / 2
FireWire Device: built-in_hub, Up to 800 Mb/sec

The following is a crash log from a completely clean and fresh install (not upgrade) of Lion on a new RAID array

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
Tue Jul 26 02:39:33 2011
panic(cpu 4 caller 0x2b0571): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0xc, NMIPI acks: orig: 0x0, now: 0x0"@/SourceCache/xnu/xnu-1699.22.73/osfmk/i386/pmap.c:3078
Backtrace (CPU 4), Frame : Return Address (4 potential args on stack)
0x836bba58 : 0x22032e (0x6abf4c 0x836bba78 0x229ef0 0x0)
0x836bba88 : 0x2b0571 (0x6b46d0 0xc 0x0 0x0)
0x836bbad8 : 0x2b3e71 (0x8674a0 0xa4c000 0x0 0xa4d000)
0x836bbb58 : 0x2b457c (0x8674a0 0xa4c000 0x0 0xfe805260)
0x836bbb98 : 0x2786fa (0x8674a0 0xa4c000 0x0 0xa4d000)
0x836bbc58 : 0x279715 (0x0 0xa4d000 0x0 0x1)
0x836bbc88 : 0x27214d (0x28c9f3c 0xa4c000 0x0 0xa4d000)
0x836bbcb8 : 0x32e09c (0x28c9f3c 0xa4c000 0x14 0x6c1a08)
0x836bbd68 : 0x32f109 (0x0 0x4ece90 0xddee004 0x0)
0x836bbdf8 : 0x32f47c (0x0 0x0 0x1 0x1)
0x836bbe38 : 0x5163aa (0xc11ec00 0x0 0x0 0xddee004)
0x836bbe58 : 0x51046c (0xddee004 0x0 0x0 0xc164c20)
0x836bbec8 : 0x327622 (0xdbc8c50 0x2 0xbc6776c 0x2261da)
0x836bbef8 : 0x30efad (0xdbc8c50 0x2 0xbc6776c 0xdbc8c50)
0x836bbf18 : 0x306ed4 (0xdbc8c50 0x0 0x836bbf78 0x559de2)
0x836bbf58 : 0x31a1f2 (0x1 0x30ef70 0x0 0xda5d0e0)
0x836bbf78 : 0x5f015a (0xc164c20 0xbc6d914 0xbc676b0 0x0)
0x836bbfc8 : 0x2e3977 (0xbc6d910 0x1 0x10 0xdb657d0)

BSD process name corresponding to current thread: launchd

Mac OS version:
11A511

Kernel version:
Darwin Kernel Version 11.0.0: Sat Jun 18 12:57:44 PDT 2011; root:xnu-1699.22.73~1/RELEASE_I386
Kernel UUID: F8596E5D-0966-3091-AA8D-6E11CA68386F
System model name: MacPro1,1 (Mac-F4208DC8)

System uptime in nanoseconds: 4308560877706
last loaded kext at 434363271217: com.apple.driver.AppleUSBEthernetHost 2.1.2 (addr 0xdae000, size 28672)
last unloaded kext at 536590398665: com.apple.driver.AppleUSBEthernetHost 2.1.2 (addr 0xdae000, size 28672)
loaded kexts:
com.apple.filesystems.smbfs 1.7.0
com.apple.driver.AppleBluetoothMultitouch 66.3
com.apple.driver.AppleHWSensor 1.9.4d0
com.apple.filesystems.autofs 3.0
com.apple.driver.AudioAUUC 1.59
com.apple.iokit.IOUserEthernet 1.0.0d1
com.apple.driver.AppleUpstreamUserClient 3.5.9
com.apple.driver.AppleMCCSControl 1.0.24
com.apple.GeForce7xxx 7.0.0
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHDA 2.1.1f11
com.apple.driver.AppleUSBDisplays 302.1.2
com.apple.driver.AppleIntel8254XEthernet 2.1.3b1
com.apple.driver.AudioIPCDriver 1.2.0
com.apple.driver.AppleMCEDriver 1.1.9
com.apple.driver.AirPortBrcm43224 500.36.11
com.apple.driver.ACPI_SMC_PlatformPlugin 4.7.0b2
com.apple.driver.AppleLPC 1.5.1
com.apple.iokit.SCSITaskUserClient 3.0.0
com.apple.driver.AppleRAID 4.0.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 32
com.apple.iokit.IOAHCIBlockStorage 2.0.0
com.apple.driver.AppleFWOHCI 4.8.6
com.apple.driver.AppleAHCIPort 2.1.8
com.apple.driver.AppleIntelPIIXATA 2.5.1
com.apple.driver.AppleUSBHub 4.4.0
com.apple.driver.AppleUSBEHCI 4.4.0
com.apple.driver.AppleEFINVRAM 1.5.0
com.apple.driver.AppleUSBUHCI 4.4.0
com.apple.driver.AppleACPIButtons 1.4
com.apple.driver.AppleRTC 1.4
com.apple.driver.AppleHPET 1.6
com.apple.driver.AppleSMBIOS 1.7
com.apple.driver.AppleACPIEC 1.4
com.apple.driver.AppleAPIC 1.5
com.apple.driver.AppleIntelCPUPowerManagementClient 166.0.0
com.apple.nke.applicationfirewall 3.0.30
com.apple.security.quarantine 1
com.apple.driver.AppleIntelCPUPowerManagement 166.0.0
com.apple.driver.AppleMultitouchDriver 220.62
com.apple.driver.IOBluetoothHIDDriver 2.5f17
com.apple.kext.triggers 1.0
com.apple.driver.AppleAVBAudio 1.0.0d11
com.apple.iokit.IOSurface 80.0
com.apple.iokit.IOBluetoothSerialManager 2.5f17
com.apple.iokit.IOSerialFamily 10.0.5
com.apple.iokit.IOAVBFamily 1.0.0d22
com.apple.iokit.IOEthernetAVBController 1.0.0d5
com.apple.driver.DspFuncLib 2.1.1f11
com.apple.nvidia.nv40hal.G7xxx 7.0.0
com.apple.NVDAResman.G7xxx 7.0.0
com.apple.iokit.IONDRVSupport 2.3
com.apple.iokit.IOFireWireIP 2.2.3
com.apple.iokit.IOAudioFamily 1.8.3fc11
com.apple.kext.OSvKernDSPLib 1.3
com.apple.driver.AppleHDAController 2.1.1f11
com.apple.iokit.IOGraphicsFamily 2.3
com.apple.iokit.IOHDAFamily 2.1.1f11
com.apple.iokit.IO80211Family 400.40
com.apple.iokit.IONetworkingFamily 2.0
com.apple.driver.AppleSMC 3.1.1d2
com.apple.driver.IOPlatformPluginFamily 4.7.0b2
com.apple.driver.CSRUSBBluetoothHCIController 2.5f17
com.apple.driver.AppleUSBBluetoothHCIController 2.5f17
com.apple.iokit.IOBluetoothFamily 2.5f17
com.apple.driver.AppleUSBHIDKeyboard 152.3
com.apple.driver.AppleHIDKeyboard 152.3
com.apple.iokit.IOUSBHIDDriver 4.4.0
com.apple.iokit.IOSCSIBlockCommandsDevice 3.0.0
com.apple.iokit.IOUSBMassStorageClass 3.0.0
com.apple.driver.AppleUSBMergeNub 4.4.0
com.apple.driver.AppleUSBComposite 3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.0.0
com.apple.iokit.IOBDStorageFamily 1.6
com.apple.iokit.IODVDStorageFamily 1.6
com.apple.iokit.IOCDStorageFamily 1.7
com.apple.driver.XsanFilter 403
com.apple.iokit.IOATAPIProtocolTransport 3.0.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.0.0
com.apple.iokit.IOFireWireFamily 4.4.3
com.apple.iokit.IOAHCIFamily 2.0.6
com.apple.iokit.IOATAFamily 2.5.1
com.apple.iokit.IOUSBUserClient 4.4.0
com.apple.iokit.IOUSBFamily 4.4.0
com.apple.driver.AppleEFIRuntime 1.5.0
com.apple.iokit.IOHIDFamily 1.7.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 165
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet 7
com.apple.driver.DiskImages 326
com.apple.iokit.IOStorageFamily 1.7
com.apple.driver.AppleKeyStore 28.18
com.apple.driver.AppleACPIPlatform 1.4
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily 1.4

and the latest Lion one after upgrading my graphics card to a 5770.

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
<pre>Interval Since Last Panic Report:  1582 sec
Panics Since Last Report:          3
Anonymous UUID:                    E2136363-5BC1-4084-A8AF-11F77F401A2E

Fri Aug  5 15:25:22 2011
panic(cpu 6 caller 0x2c3692): "Spinlock acquisition timed out: lock=0xc8af028, lock owner thread=0xd4a57f0, current_thread: 0xd52e7f0, lock owner active on CPU 0x3"@/SourceCache/xnu/xnu-1699.22.73/osfmk/i386/locks_i386.c:375
Backtrace (CPU 6), Frame : Return Address (4 potential args on stack)
0x84be3c78 : 0x22032e (0x6abf4c 0x84be3c98 0x229ef0 0x0)
0x84be3ca8 : 0x2c3692 (0x6b71dc 0xc8af028 0xd4a57f0 0xd52e7f0)
0x84be3cd8 : 0x22b91b (0xc8af028 0xffffff81 0x0 0x863120)
0x84be3d18 : 0x22e2b5 (0xc8b0000 0x0 0x1 0x23f626)
0x84be3d68 : 0x22f5f2 (0xd52e80c 0x2 0x84be3da8 0x240ba7)
0x84be3dc8 : 0x22f720 (0x5583b0 0xcc8b020 0x0 0x0)
0x84be3de8 : 0x5582b4 (0x5583b0 0xcc8b020 0x2 0x73fb78aa)
0x84be3e38 : 0x559c33 (0xcc8b020 0x5596c0 0x559710 0xd2864b4)
0x84be3f28 : 0x559de2 (0x0 0x0 0x0 0x580538)
0x84be3f78 : 0x5f015a (0xd7bc3a8 0xd2a0194 0xd28646c 0xd2a0190)
0x84be3fc8 : 0x2e3977 (0xd2a0190 0x0 0x10 0xc934090)

BSD process name corresponding to current thread: mdworker

Mac OS version:
11A511

Kernel version:
Darwin Kernel Version 11.0.0: Sat Jun 18 12:57:44 PDT 2011; root:xnu-1699.22.73~1/RELEASE_I386
Kernel UUID: F8596E5D-0966-3091-AA8D-6E11CA68386F
System model name: MacPro1,1 (Mac-F4208DC8)

System uptime in nanoseconds: 894143239841
last loaded kext at 391233202475: com.apple.filesystems.smbfs   1.7.0 (addr 0x1352000, size 249856)
last unloaded kext at 87273937308: net.digitaldj    1.0 (addr 0x1352000, size 16384)
loaded kexts:
com.apple.filesystems.smbfs 1.7.0
com.apple.driver.AppleBluetoothMultitouch   66.3
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleHDA   2.1.1f11
com.apple.driver.AppleUpstreamUserClient    3.5.9
com.apple.driver.AppleMCCSControl   1.0.24
com.apple.driver.AudioAUUC  1.59
com.apple.kext.ATIFramebuffer   7.0.2
com.apple.driver.AppleUSBDisplays   302.1.2
com.apple.iokit.IOUserEthernet  1.0.0d1
com.apple.driver.AppleMCEDriver 1.1.9
com.apple.ATIRadeonX3000    7.0.2
com.apple.driver.ACPI_SMC_PlatformPlugin    4.7.0b2
com.apple.driver.AppleLPC   1.5.1
com.apple.Dont_Steal_Mac_OS_X   7.0.0
com.apple.driver.AudioIPCDriver 1.2.0
com.apple.iokit.SCSITaskUserClient  3.0.0
com.apple.driver.AppleRAID  4.0.6
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 32
com.apple.iokit.IOAHCIBlockStorage  2.0.0
com.apple.driver.AppleFWOHCI    4.8.6
com.apple.driver.AppleIntel8254XEthernet    2.1.3b1
com.apple.driver.AppleAHCIPort  2.1.8
com.apple.driver.AppleIntelPIIXATA  2.5.1
com.apple.driver.AppleUSBHub    4.4.0
com.apple.driver.AirPortBrcm43224   500.36.11
com.apple.driver.AppleUSBEHCI   4.4.0
com.apple.driver.AppleEFINVRAM  1.5.0
com.apple.driver.AppleUSBUHCI   4.4.0
com.apple.driver.AppleACPIButtons   1.4
com.apple.driver.AppleRTC   1.4
com.apple.driver.AppleHPET  1.6
com.apple.driver.AppleSMBIOS    1.7
com.apple.driver.AppleACPIEC    1.4
com.apple.driver.AppleAPIC  1.5
com.apple.driver.AppleIntelCPUPowerManagementClient 166.0.0
com.apple.nke.applicationfirewall   3.0.30
com.apple.security.quarantine   1
com.apple.driver.AppleIntelCPUPowerManagement   166.0.0
com.apple.driver.AppleMultitouchDriver  220.62
com.apple.driver.IOBluetoothHIDDriver   2.5f17
com.apple.kext.triggers 1.0
com.apple.driver.DspFuncLib 2.1.1f11
com.apple.driver.AppleAVBAudio  1.0.0d11
com.apple.iokit.IOFireWireIP    2.2.3
com.apple.iokit.IOSurface   80.0
com.apple.iokit.IOBluetoothSerialManager    2.5f17
com.apple.iokit.IOSerialFamily  10.0.5
com.apple.driver.AppleHDAController 2.1.1f11
com.apple.iokit.IOHDAFamily 2.1.1f11
com.apple.iokit.IONDRVSupport   2.3
com.apple.iokit.IOAVBFamily 1.0.0d22
com.apple.iokit.IOEthernetAVBController 1.0.0d5
com.apple.driver.IOPlatformPluginFamily 4.7.0b2
com.apple.driver.AppleSMC   3.1.1d2
com.apple.kext.ATI5000Controller    7.0.2
com.apple.kext.ATISupport   7.0.2
com.apple.iokit.IOGraphicsFamily    2.3
com.apple.iokit.IOAudioFamily   1.8.3fc11
com.apple.kext.OSvKernDSPLib    1.3
com.apple.driver.CSRUSBBluetoothHCIController   2.5f17
com.apple.driver.AppleUSBBluetoothHCIController 2.5f17
com.apple.iokit.IOBluetoothFamily   2.5f17
com.apple.driver.AppleUSBHIDKeyboard    152.3
com.apple.driver.AppleHIDKeyboard   152.3
com.apple.iokit.IOUSBHIDDriver  4.4.0
com.apple.iokit.IOSCSIBlockCommandsDevice   3.0.0
com.apple.iokit.IOUSBMassStorageClass   3.0.0
com.apple.driver.AppleUSBMergeNub   4.4.0
com.apple.driver.AppleUSBComposite  3.9.0
com.apple.iokit.IOSCSIMultimediaCommandsDevice  3.0.0
com.apple.iokit.IOBDStorageFamily   1.6
com.apple.iokit.IODVDStorageFamily  1.6
com.apple.iokit.IOCDStorageFamily   1.7
com.apple.driver.XsanFilter 403
com.apple.iokit.IOATAPIProtocolTransport    3.0.0
com.apple.iokit.IOSCSIArchitectureModelFamily   3.0.0
com.apple.iokit.IOFireWireFamily    4.4.3
com.apple.iokit.IOAHCIFamily    2.0.6
com.apple.iokit.IOATAFamily 2.5.1
com.apple.iokit.IOUSBUserClient 4.4.0
com.apple.iokit.IO80211Family   400.40
com.apple.iokit.IONetworkingFamily  2.0
com.apple.iokit.IOUSBFamily 4.4.0
com.apple.driver.AppleEFIRuntime    1.5.0
com.apple.iokit.IOHIDFamily 1.7.0
com.apple.iokit.IOSMBusFamily   1.1
com.apple.security.sandbox  165
com.apple.kext.AppleMatch   1.0.0d1
com.apple.security.TMSafetyNet  7
com.apple.driver.DiskImages 326
com.apple.iokit.IOStorageFamily 1.7
com.apple.driver.AppleKeyStore  28.18
com.apple.driver.AppleACPIPlatform  1.4
com.apple.iokit.IOPCIFamily 2.6.5
com.apple.iokit.IOACPIFamily    1.4
Model: MacPro1,1, BootROM MP11.005C.B08, 8 processors, Quad-Core Intel Xeon, 2.33 GHz, 7 GB, SMC 1.7f10
Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
Memory Module: DIMM Riser A/DIMM 1, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x802C, 0x3138484632353637324A4436363745314434
Memory Module: DIMM Riser A/DIMM 2, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x802C, 0x3138484632353637324A4436363745314434
Memory Module: DIMM Riser B/DIMM 1, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x830B, 0x4E543147543732553850413642442D334320
Memory Module: DIMM Riser B/DIMM 2, 1 GB, DDR2 FB-DIMM, 667 MHz, 0x830B, 0x4E543147543732553850413642442D334320
Memory Module: DIMM Riser A/DIMM 3, 512 MB, DDR2 FB-DIMM, 667 MHz, 0x802C, 0x39485446363437324A592D36363742344433
Memory Module: DIMM Riser A/DIMM 4, 512 MB, DDR2 FB-DIMM, 667 MHz, 0x830B, 0x4E54353132543732553839413842442D3343
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.131.36.11)
Bluetooth: Version 2.5.0f17, 2 service, 19 devices, 1 incoming serial ports
Network Service: Ethernet 2, Ethernet, en1
PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
PCI Card: ATI Radeon HD 5770, ATY,HoolockParent, Slot-1
Serial ATA Device: WDC WD1001FALS-00J7B1, 1 TB
Serial ATA Device: WDC WD1001FALS-00J7B1, 1 TB
Serial ATA Device: ST3500630AS, 500.11 GB
Serial ATA Device: ST3500630AS, 500.11 GB
Serial ATA Device: OCZ-VERTEX2, 60.02 GB
Serial ATA Device: OCZ-VERTEX2, 60.02 GB
Parallel ATA Device: PIONEER DVD-RW  DVR-111D
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd500000 / 3
USB Device: Apple Keyboard, apple_vendor_id, 0x0221, 0xfd520000 / 6
USB Device: hub_device, apple_vendor_id, 0x9132, 0xfd300000 / 2
USB Device: USB2.0 Card Reader, 0x090c  (Silicon Motion, Inc. - Taiwan), 0x6107, 0xfd310000 / 5
USB Device: Apple Cinema HD Display, apple_vendor_id, 0x9232, 0xfd320000 / 4
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8206, 0x5d200000 / 2
FireWire Device: built-in_hub, 800mbit_speed
FireWire Device: unknown_device, unknown_speed</pre>

This post will continue to get updated as and when there is a cause or solution found to my crashing.

3rd August 2011 – Have heard from others who have upgraded a MacPro 1,1 like me and running Lion without a problem. They all seem to have upgraded their graphics card to Apple’s ATI 5700 card so I ordered one of these from Apple today for a whopping £203 which should hopefully arrive tomorrow. Once installed I shall boot back into my fresh Lion installation for a few hours and see if there are any more crashes.

4th August 2011 –  I received  the new 5770 Apple upgrade kit and will set about installing this later on this evening and report back……..
…the 5770 was installed without a hitch and the MacPro booted up first time with no errors. I logged into my stable 10.6.7 and tinkered around playing 1080p videos full screen on my 30″ ACD and lots of GPU intensive tasks and it seemed much smoother at HD video playback etc. After a few hours I decided the card was working as it should so crossed my fingers and booted into my Lion installation. Again all seemed ok, nice smooth 1080p playback, I even tried some 4k video playback and it was smooth full screen. After about half an hour I thought maybe it was all stable so I thought I’d do a bit of housekeeping and repair any disk permission errors using Disk Utility. However, Disk Utility still refuses to verify or repair permissions of RAID arrays in Lion. There’s a lot of info on the Apple discussion forums about this so I opted to try verifying permissions from Terminal and it found some errors. So I then tried to repair those errors via terminal and left that running and went to bed. About 2 mins later I heard the tell-tale “boing” of the Apple start-up chime…it had crashed and rebooted whilst trying to repair permissions.

5th August 2011 – I went back to the machine this morning and sure enough I was presented with the log in screen as it had rebooted after a kernel panic. I logged in but there was no prompt to submit a crash report to Apple as there normally is and there is nothing logged in /Library/Logs/Diagnostic/ where the kernel panic reports normally live. So I can rule out my graphics card as the KP (Kernel Panic) happens with both original 7300GT and brand new Apple ATI 5770 cards. Time to start eliminating other items. Next on my hit list is RAM. I only have 7GB installed and it all seems ok when I’m booted in 10.6.7 and the Apple Hardware Test that comes on the OS X install CD returned no errors but for completeness I thought I’d run some extensive memory tests. I downloaded two programs Rember and Memtest, the former is a GUI for the latter. I tried running Rember from within OS X and it returned no errors but as some of the memory is not accessible whilst booted into the OS I installed Memtest and rebooted my computer into single user mode (hold down CMD+S when you reboot). Once in single user mode I typed

1
memtest all 2

to run memtest tests on all memory sectors twice. I’ve left that running and come to work but I’ll report back later if it found any errors. If there are no RAM errors I might take half the modules out anyway, boot Lion and see if it KPs and if it does swap with the other half of the RAM and see if that KPs. If it does it KPs with every single module then I doubt it’s a RAM issue. I’ll then look to install a non-RAID drive and install a fresh copy of Lion on that to see if the KP still happen on a non-RAID drive. I still think this is an Apple induced issue with 10.6.8 and Lion, I’m going to start looking into whether 64bit EFI might be to blame (the MacPro only has a 32bit EFI but 64bit capable processors).

Memtest completed two complete thorough RAM module checks and all passed without a fault so RAM ruled out.

 

19th August 2011 – Right I’m still getting KPs on my Lion test install and am sticking with 10.6.7 for now so I can keep working but I’ve now pretty much ruled out any hardware faults.

  • I bought a new ATI 5770 to replace my 7300GT and still KP.
  • I removed my SSD RAID array on the 5th and 6th SATA Ports and still KP.
  • I tried booting with only Lion HDDs in and removed the 2nd RAID array and still KP.
  • I bought another 8GB RAM and ran with just that in on its own and still get KP so RAM ruled out.
  • I ran fans at near full speed and COU core temps stayed below 40°C and still KP.
  • I ran fans at default speed and cranked my CPU usage to 100% for about 4 hours and no KP in LION so I doubt the CPUs are bad. Once I stopped the CPU stress test I opened Safari and browsed the web a little and it KP’d.
  • I’ve run with WiFi and Bluetooth disabled to see if those were a cause but still got KP. I might try removing them from the motherboard completely though just to check but they are genuine Apple modules.

I also tried tinkering around copying IOPCI kexts and IOPLatformFamily kexts and copying copies of these from a working 10.6.7 installation over the Lion versions but that didn’t work either.

Where does this leave me? Basically nowhere. I’m still buggered if I use 10.6.7 or 10.7.0 or 10.7.1 and get regular KPs. I’ve not managed to go more than 1 hour without a KP, except funnily enough when I was stress testing the CPU and it could happily sit there all day at 800% CPU usage. Having now bought another 8GB of RAM and run with just that in and the original 7GB removed I can rule out having bad RAM, plus the fact it works in 10.6.7 for days without a KP means it definitely software related.

I still haven’t got around to breaking apart one of my RAID arrays and trying to install Lion on just a single non-RAIDed drive. I do still think RAID could be part of the cause, since in Lion I still cannot verify or repair disk permissions on a RAID array using disk utility but I can using diskutil command in terminal but most of the time I get a KP about 90% through….suspicious. But then my hopes are dashed by people like @poo in the comments who has the same issue but doesn’t have any RAID arrays. But then again his problems may be something completely different.

For now I’m sticking with 10.6.7 and every so often trying Lion and some tweaks but having now spent £203 on an ATI 5770 and £180 on another 4GB RAM I’m reluctant to waste much more time or money on this and just hope Apple find a solution/cure soon?

1st September – I’m still running 10.6.7 and had no time to do any more experimenting to resolve my KPs but I have just had a reply from Apple Tech via bugreport.apple.com (some 6 weeks later) and they now need a complete Kernel Core Dump which I’ve never heard of before and they’ve included some complex instructions on how to setup a 2nd Mac running OS X as a Kernel Dump Server which has to be connected via ethernet to my MacPro and then modify the nvram of my MacPro so that all kernel dumps are sent to the IP address of the 2nd computer. That way they grab every single kernel instruction and upload that to them. The file could be up to 1GB in size so they’ve given me ftp details to upload the file. So it seems Apple are investigating this which is promising. I’ll update once I hear any more.

13th September – I eventually found time to copy clone the contents of 2 of my drives that were in a RAID array to my Mac Mini Server and pulled them out. I installed an old 80GB Seagate Barracuda drive in HDD Bay 3, booted into my good 10.6.7 and used Disk Utility to format it as HFS with a GUID partition. I then downloaded the latest Lion installation package (10.7.1) from the App store and installed that on the newly formatted drive. Once booted I ran the terminal commands as instructed by Apple Tech Support so that any crash logs will now be saved across the network to my Mac Mini Server and am currently waiting for a kernel panic. Sod’s law it won’t bloody KP now! I’ve unmounted the other remaining drives in the MacPro so that to all intents and purposes this is now just a MacPro with a single 80GB (non-raid) drive installed. Guess I’ll just have to keep playing in Lion to see if it’s become any more stable. NOTE – Disk Utility now lets me verify and repair permissions on the Lion disk which it didn’t before when I had Lion installed on a RAID array. Watch this space.

14th September – Dammit! After using it for several hours last night it seemed fine, went to bed, woke up and it had kernel panic in the night and rebooted, the crash log for submission to Apple mentioned “spinlock acquisition timed out” or similar I’ve seen that many now I don’t take much notice to them. I checked my MacMini Server which is meant to collect the core kernel dumps and there was nothing. Even though I had changed the nvram settings as per Apple’s request so my MacMini Server would collect all the core kernel dumps, I’d forgotten to restart the computer after making nvram changes. So I restarted again, and then forced a test kernel panic (if you want to read up more on how to setup a 2nd machine to collect your core kernel dumps read this) to check if the core dumps were now going through to my MacMini Server but they still weren’t. I’ve left a message with Apple tech for help on this matter but in the interim I’m going to try and setup a MacBook Pro as a dump server and see if that works. Anyway, we can rule out RAID as being the cause of any KPs. I know one or two commenters below said they get KP and don’t use RAID, not that I didn’t believe them, I just had to run through all my elimination processes. RAM replaced, new HDD (non-RAID), new 5770 Graphics card….erm I’m running out of replaceable hardware items that could be to blame. I really hope it is an Apple bug with 10.6.8 and Lion (10.7 and 10.7.1) and not faulty CPU. I’ve now accepted that I’m going to have to try eliminating the CPU in all this and need to roll back to stock CPUs. I’d like to get the CoreDump working properly first and submit them to Apple so that can hopefully see somthing that I can’t. Sorry to say this again, but watch this space…

NOTE – It is becoming more and more apparent that only people with upgraded CPU are suffering from kernel panics and crashes in Lion. From the comments below you will see people with X5355, X5365, E5345 etc. Did the MacPro 1,1 ever ship with 8-cores and if so what was the factory OEM 8-core CPU that it shipped with?

15th September – Right so I’ve not had a Kernel panic for nearly 2 days. What did I do to accomplish this, I wish I could say for sure. First things first, I tried setting up my MacMini Server to be a core kernel dump so when i did have a KP 1GB+ of crucial logs would be logged on there for me to upload to Apple. I had problems with this, if I tried to force a kernel panic by typing:

sudo dtrace -w -n “BEGIN{ panic();}”

at the command prompt it would begin connecting to my MacMini Server’s IP, correctly find it and retrieve it’s MAC address and then timeout trying to send the logs. After hours and hours trying to figure it out, including setting up a Macbook Air and Pro as a core dump server I finally figured out that by default the kernel dumps go out over ethernet EN0 which is ethernet port 1 and I had my cable plugged into EN1 (ethernet port 2). Once I switched ports and triggered a kp manually the core dumps were sent correctly to my remote machine. OK so all I needed now was to wait for it to kernel panic. Didn’t take long, mouse froze and then poof it rebooted without any kernel core dump going to my remote server. WTF! That didn’t work then. Normally I get a kernel panic screen or the terminal prompt scrolling across the top of my desktop image. Right I’ll just keep using it until I get a proper kernel panic I thought.

So carried on using it for a day with basic core apps, safari, chrome and that’s about it. No crashes. I left it playing full screen streaming HD from the NASA site all night to see if overheating GPU or similar could be the cause, nothing. Now here’s some things I did do

but I’m sure I’d done before.

  1. I had to update my flash when I went to NASA website I think so I downloaded latest Flash.
  2. I removed my ethernet port 2 from Network pane in System preferences and I mean removed not just turned off.
  3. I removed my Airport from Network pane in System preferences and I mean removed not just turned off. There have been others with iMacs reporting Airport cards causing KPs and to roll back kexts, since I’m hardwired to my TimeCapsule I just thought fuck it and removed it from the list.
  4. I normally have an Apple iSight camera connected to the Firewire port on my Apple 30″ cinema display, I have unplugged that.
  5. I normally have a USB multi-card reader connected to the USB ports on my 30″ ACD, I have disconnected that.

I’ve now been up for 1 day 22 hours. In that time I’ve setup two email accounts in Mail app and downloaded 30,000+ emails and I’ve installed iLife 11 and run software update to bring all the iLife apps up to date.

Recent queries:

  • tlb invalidation ipi timeout
  • cpu 0: failed to update microcode from version 0x0
  • spinlock acquisition timed out kernel panic
  • apple 6
  • Oh My General site=114la com
  • macpro 1 1 crash installation 10 7

80 Replies to “Apple update 10.6.8 and Lion (10.7) cause Kernel Panics on MacPro 1,1”

  1. I am not sure this will help but on my Hackintosh DX58SO with XeonW3530 identified as MacPro4,1 I have been abble to remove KP occuring at boot process.

    From me the main difference is 10.6.7 doesn’t have trim function this is why you don’t have issues with that release.

    Let me explain I added in my rig a PCIe Sata3 card with Sata3 compatible SSD’s and started to have KP’s like yours
    (with exactly the same logs as yours).

    I only have add KP’s with 10.6.8 on 10.7.5 and 10.8.2 no KP’s at all.

    When I disabled trim functionality (you can do that patching IOBlockStorage kext) I don’t get any KP on 10.6.8.

    Now after updating to the latest SSD’s firmware 10.6.8 is working fine also.

  2. This issue might only be affecting Intel processors that were not used in production Macs.

    I’m having the same problem in Lion with a pair of E5350 processors, going to install 10.6.7 and see if things stabilize.

  3. Hi All

    I have just installed two e5435s in a 1,1 MacPro also has a ati HD4650 due to the failure of the expen$ive 8800 Mac$ Nvidia.

    I was wondering…

    a. what is the benefit of going 2,1 upgrade of EFI and how do i do that.
    b. is there a way under Lion 10.7.3 to get it to recognize CPU as 8 cores (now only shows one as compared with previous 4)

    thanks

  4. After 6 months trouble free with my MacPro 1.1 upgded to 2.1 and 2x Xeon x5365 (super procs) i moved to 10.6.8 form my former snow leo version and 1 month later first kernel panic (after a sleep). In more than 6 years of use of this machine it’s probably the first time i see something like that happen …

    So i do onot think that moving from 1.1 to 2.1 will solve the issue but who knows ?

    Tell us if you found a solution to this.

  5. I have upgraded the CPUs in my MacPro 1,1 to X5355, had no problems at all in Leopard, and after updating to Lion after 1 month I had a first KP, so what is the solution for me?

    to use Mac Pro 2006-2007 Firmware Tool to go to 2,1?

    thanks, I will read all the posts if I had another KP.

  6. I’m also waiting for approval from netkas for a long time. I upgraded processors to x5345 and have KP often.

    Is anyone willing to share utility 1.1 to 2.1?

    Thanks

    joomlajATgmailDOTcom

  7. I guess with over a month and no one writing anything that their computers have been running strong since the firmware update. I’m tapping my toe with for netkas to approve me so I can download this. I’m really curious, no problems?

  8. I’ve just upgraded my Mac Pro 1,1 with 2xE5345 Xeons, and thanks to the information on this blog, and on the Netkas forums, my system is running totally fine.

    I first upgraded my boot rom to the 2,1 version, then replaced the CPUs. I did some stress tests on my system with 10.6.8, and then upgraded to 10.7.1.

    My machine has been running totally fine for about a week now, and I’ve done loads of media encoding with x264encoder, as well as spending a lot of time playing Arkham Asylum (which is superb).

    I’ve also upgraded my graphics card from an X1900 to a Radeon 5770, thanks to the BIOS mod information from Netkas. This made a huge improvement. Almost as worthwhile as upgrading the processors.

    One important thing to remember is using the correct procedure for applying the heat sink compound when replacing the CPUs. Check out: http://www.arcticsilver.com/pdf/appmeth/int/hl/intel_app_method_horizontal_line_v1.1.pdf

    for more information.

  9. UPDATE:

    Well, someone on this forum was kind enough to send me the firmware. I read it closely and carefully, and to be honest, was a big leery of doing it since I knew at this moment I had a very stable environment, and I was thinking I should just leave well-enough alone.
    My curiosity got the best of me, and I just performed the firmware upgrade. It worked perfectly, and while I haven’t moved up to 10.6.8 OR Lion at this point, I know the firmware did something, because where I used to see “2.66 Unknown” for the Processors inside the System Profiler, I now see “2.66 Ghz Quad-Core Intel Xeon”. I’m VERY happy that there are such intelligent people out there that can make magic happen for us! Thanks again to everyone who helped get this issue resolved before Apple helped us. I think I’m still going to wait a little while longer before I run my upgrade path, because I need a stable work environment this week, but look out next weekend! hehee

    Take care!

  10. Thank you SO much for allowing me to keep my sanity. I have been struggling with kernel panics for the past week, and I did all kinds of my own “troubleshooting” (basically process of elimination) and was getting NOWHERE in a hurry. I must have typed at least 20 nasty comments that get sent to Apple with the bug reports during the course of all this, because it’s ridiculous that they haven’t fixed this issue yet.
    All I can say is thanks to all of you, I’m SAFELY at 10.6.7 right now, and my computer has been up for a solid 12 hours now without a single glitch. The only thing that I lost (for the time being) is my iPhoto library, because apparently I have to be at 10.6.8 in order to run whatever version my library was updated to at the time. It’s a bummer, but I’d rather have a functioning computer right now!
    For the record, or whatever it’s worth to others, here is my setup:

    MacPro1,1
    2 x 2.66Ghz quad core processors
    12 gigs of RAM
    MP11.005C.B08 Boot ROM version

    I have a RocketRAID 2314 card
    2 SANS Digital TR8M-B
    16 Seagate 1.5 TB ST31500341AS 7200RPM drives
    NVidia GeForce 8800 GT

    So you can see I had a lot of things I was troubleshooting. hehehe I took everything apart, blew the dust out, reseated things. It was a mess!

    Now maybe if the Netkas forum dudes would approve me for their website, I could download that altered firmware and maybe get myself back to Lion, or at the very least, 10.6.8. But again, I’m just happy to have a stable system.

    Thanks again!

  11. Hey guys,

    Khai back for some reporting. I’m up to 5 days uptime. Not much, but before, I couldn’t even get more than a day of uptime before a crash.

    Previously, I RMA’ed my OCZ SSD. It turns out that there was a SERIOUS bug that caused the SSD to spontaneously disconnect itself (not physically of course) from the SATA controller. This happened on my Mac AND on my Dell.

    I received a new SSD with a firmware fix for the bug and have been fine since.

    Now running 2 x 5355 CPUs on 2,1 Firmware with the SSD as the boot drive running 10.7.2. Also running hacked 5770. So far, I’ve experienced ZERO problems. Lion + SSD is super fast.

    I realized that the group of people who upgrade their CPUs are probably more likely to get upgrade graphics cards and SSDs to breathe new life into their aging Mac Pros. I’m no exception and i expect there’s quite a number with the particular SSD firmware problem. I’m not saying that is the only cause, but my problems have vanished… for now!

  12. Did you update the firmware as described further up? Mines been faultless. Just rebooted after 26 days up due to installing some software. Touch wood it’s fine.

  13. Mhm, got the same problem. The kernel panics occured after I upgraded the CPUs of my macpro1,1 and most likely after upgrading to 10.6.8. I also run the Radeon 5770. Interestingly I have noticed that the KPs only happen when one of my external Firewire drives is running. The KPs only happen once in a while, but still bothersome.

  14. $ uptime
    20:14 up 11 days, 19:10, 2 users, load averages: 4.70 4.45 3.86

    Doing good so far. I only had to reboot because of the earlier iTunes issue else it’d be like 20 days.

  15. Just got back my Vertex 3 240 GB OEM from OCZ via RMA. Gonna rebuild the system to this disk and see. Currently on 10.7.1 for 10 days now without a crash. Will send more updates as I can. Long live Steve Jobs.

  16. Just updated my Mac Pro 1,1… About this Macs shows a 2,1 so I’m really hoping this is successful. I’m still on 10.6.8 — anyone have any advice on upgrading to Lion? While I’m at it, how do you even downgrade to 10.6.7? This thread has really been a lifesaver so far.

  17. Pretty sure all posting here are talking about genuine Mac Pros Ron.

    So any news guys? Been quiet for a little while, does that mean more people have found the firmware upgrade solves their problems?

    I’ve completed all my upgrades listed in previous posts, including a flashed 5770, firmware from 1,1 to 2,1 , an Intel SSD and finally updating system to Lion (10.7.1) and all is still well and stable over a week later. I still get much higher than usual temps in comparison to my stock system (discussed this in some of my first posts here), but use SMC fan control to set most fans to 1000rpm and have the system idling around 40°C-45°C. I now seem to be able to run the system without running the fans quicker (no longer overheats and restarts), but since the temps still get high, I’ve decided higher RPMs and a cooler system is not going to hurt.

  18. are you all talking E5345’s on a real Mac?, I tried to install iPC 10.5.6 on to HP XW6400 with 2x E5345 for 8 cores, and get KP upon reboot, installing had no issues, prior to that I had 2x 5160 4 cores and iPC 10.5.6 installed and booted fine, but if I do the update, upon reboot get KP, did anyone ever get Snow Leopard or Lion to work on XW6400 with either 5160’s or E5345’s,
    Thanks
    Ron

  19. Mine didn’t crash but stupidly iTunes started using my OS drive to store it’s music for some reason and then I ended up with a filled up hard drive after importing loads of tunes and not realising. That kinda screwed the computer up and I couldn’t clear the trash.

    Prior to that I had 8 days trouble free…

  20. Scoops, latest firmware for your SSD is 1.35 according to OCZ http://www.ocztechnology.com/ssd_tools/OCZ_Vertex_2,_Vertex_LE,_Agility_2/

    The easiest way to update it (I’m not even sure you should right now as OCZ has been releasing some pretty buggy firmware) is to plug it into a PC.

    So check this: I noticed during my stable 10.7.1 system, I also had my SSD plugged into a drive bay. After about 4 days of uptime, when I went to System Report to check out my system, the SSD that used to show up as Vertex 3, showed up as UNKNOWN and was no longer mounted on my desktop.

    It was at this moment when I shut down and rebooted that I experienced crashing again. Eventually, my computer wouldn’t even boot while the SSD was plugged in. Both my Mac AND my PC had problems booting while the SSD was plugged in. Highly suspect a defective SSD (Never buying a Vertex again… it’s so hit or miss). The only way I could even detect it was hotplugging it into the SATA port after the OS started up. Not something I advise doing. I suspect that my crashes were the result of the drive miscommunicating with the storage controller. It’s a known problem that random OCZ SSD drives will BSOD a Windows PC, and in this case, KP my Mac.

    Anyway, I received an RMA for the SSD. I’ll try again when I get a replacement.

    Long story short, keep an eye out for behavior patterns with your mass storage. Thanks for everyone’s update. I’m really hoping we can all rest easy when this is all said and done!

  21. ^ Yeah no issues at all, in fact I was a little surprised, kinda expected problems but the 5770 has been fine since installation. Installed after 2,1 update and am still running Snow Leopard so will have to see what happens once I get my SSD and install Lion (should be today).

    My drives are presently:
    1 x 500 Gb WDC WD5000AAKS (Western Digital Caviar Blue) as primary install drive
    1 x 1.5Tb ST31500341AS (Seagate Barracuda)
    2 x 2Tb WDC WD20EARS (Western Digital Caviar Green)

    Will be adding:
    1 x 120Gb SSDSA2CW120G3K5 (Intel 320s SSD) running firmware version 1.92 (also known as 0362) as primary install drive.

    Planning to remove all drives from system, perform a fresh Lion install on SSD, then if all runs smoothly will add all other drives.

  22. @khai @Sam – Here’s my HDD setup

    • Bay 1 – 1TB WD caviar
    • Bay 2 – 1TB WD caviar
    • Bay 3 – 0.5TB WD Caviar
    • Bay 4 – 0.5TB WD Caviar
    • Bay 5* – 60GB OCZ Vertex 2
    • Bay 6* – 60GB OCZ Vertex 2

    *Note Bay 5 and 6 are the two spare sata ports on the motherboard, the 2x SSD drives are connected to these are screwed into the spare optical drive bay.

    Bay 1+2 are in a RAID 0 array – My main SL 10.6.7

    Bay 2+3 are in a RAID 0 array – Backup data and Lion 10.7.1

    Bay 5+6 are in a RAID 0 array – Stock SL 10.6.7 install with just Lightroom and some rendering software, I boot into this purely for rendering and speed.

    I’m not sure what firmware version my SSD have on them but I guess I should check. I did try upgrading to SSD SL install to Lion but as it kept crashing I rolled back to 10.6.7 on that drive.

    I took out the Bay 3 and Bay 4 RAID array and stuck a basic 80GB non-RAID drive in there and installed Lion onto that fresh, I even used Lion’s Disk Utility to erase and format the drive. That Lion installation would KP, I noticed spotlight was spending a lot of time indexing the other RAID arrays that it could see so I unmounted them in case that was an issue and it used to still KP. This is all pre-2,1 firmware update btw.

    After 2,1 update and still just running on a spare 80GB drive I’d decided things were stable enough and put my bay 3 and 4 drives back in. I wasn’t sure if you could safely remove RAID 0 drives, put other drives in and then put the original RAID 0 drives back in but turns out you can which was a nice bonus but now that’s got me thinking, where does it store the RAID array info? Even when my bay 3 and 4 drives were out, the RAID array still showed up in Disk Utility but was greyed out as the disks weren’t present. I decided to wipe the array and recreate it anyway just in case Lion re-creates in a different way.

    Anyway as i think i said in an earlier comment, I installed a fresh Lion on this RAID array and then used CCC to copy the data back over but forgot to tell it to ignore system files so I quickly borked my fresh Lion install that I was hoping to test with for a few days.

    I’m still not brave enough to touch my 10.6.7 main install, I think I’ll check the firmware on my Vertex 2 though and if necessary update that (which I’ve never done before) but from what others have said I’ll have to bring them in to work and hook up to Windows PC. Then I might try installing Lion on them and see how that goes.

    Until some crucial software that I need comes out that is Lion only I’m playing it safe and sticking with 10.6.7 and dipping my toe into Lion on spare drives to test for myself/you guys.

    Off to Florida tomorrow for over a week so there’ll be no updates from me but I’ll keep an eye on comments (and evil spam comments) as much as I can.

    @poo – you got a flashed 5770 working with a MacPro 1,1? That’s impressive, lots of people have struggled with that. Is that before or after the MacPro2,1 update, wonder if that helped? I played it safe and bought an Apple branded 5770 last month and that works ok.

    Scoopz (admin)

  23. So I’m at:
    20:34 up 7 days, 20:03, 2 users, load averages: 4.38 3.78 3.60

    Used to just bail at 5/6 days so touch wood, fine so far.

    I am running 2 OCZ Vertex 2’s in RAID0 (yes yes I know)…

  24. OK, I have a small clue over what’s happening:

    Since i’ve booted with my “Dirty” 1TB drive (leopard=>snow leopard=>lion, bunch of apps, kernel extensions), no crashes. other than the normal sluggishness of a non-SSD drive at startup, it’s actually running great. So great, that I’d rule out bad RAM as a problem.

    My SSD with Lion was a clean Lion… meaning I did not have Snow Leopard on there prior to install. This one crashes.

    I have another 1TB drive that cloned the SSD from Lion onto. This one crashes too. I cloned it using Time Machine.

    So now, I suspect:

    • Corrupt file from SSD (which carried over to the spare HD via Time Machine), possibly firmware related
    • Problems having a “clean” Lion vs. Snow Leopard upgraded to Lion

    The SSD is a 240 GB VERTEX 3 OEM. I kept the latest firmware and just installed one that came out 2 days ago. (2.11 and 2.13). I haven’t tried the 2.13 yet, but I’m planning on doing a secure erase and reinstalling with JUST Lion and no other apps and seeing how long it can run. Upgrading firmware involves shoving the SSD into a PC for me.

    If that works, then I’ll start to rebuild and reinstall my apps from scratch and continue my wait-and-see pattern.

    If that fails, I’ll repeat the process, but install Snow Leopard on the SSD drive first and THEN upgrade to Lion. I personally think it’s a shot in the dark, but at this point, I’ll try anything.

    I’m very thankful I still have my “Dirty” Lion drive that works perfectly. If not, I’d have to do more hardware troubleshooting (Pull out CPUs, ditch the SSD, replace all the Memory).

    Could everyone post what model HD/SSD your Lion is running and firmware version of the drive if possible?

    1. @khai – in answer to your question, about my mac shows the following about my 2xVertex 2 SSD

      Model: OCZ-VERTEX2
      Revision: 1.29

      So I assumed the 1.29 is the firmware revision. Not sure where this sits with latest version, it’s what was on them when they arrived and seems ok.

  25. All still up and running smoothly for me. I shut down today for the first time since upgrade to 2,1 firmware (intentionally, no KP) so that I could upgrade my video card. Replaced my ATI Radeon XT1900 with an XFX Radeon HD5770 (non Apple version flashed) which seems to be running very nicely. Worthwhile upgrade so far.

    Have purchased an Intel 320 series SSD which (all going well) I will install over the weekend in the second optical bay (after insuring latest firmware revision is updated for the drive – very important in case anyone is reading this and planning to do similar). Once SSD is in I will finally upgrade to Lion and cross everything.

    Sorry to hear about your recent problems Khai, hope things are sorted? What sort of SSD do you have? Depending on model (actually almost regardless of model TBH) it’s really important to run the most up to date firmware available. There’s a few serious issues out there for those who don’t, for example: http://forums.anandtech.com/showthread.php?t=2178373

  26. Of note:

    I experienced the crashes only after booting
    On my SSD drive.

    After the firmware update, I was running fine on my spinning disk HD containing my snow leopard-upgraded-to-Lion system. No crashes.

    When I booted off the SSD, crashes again. I’m restored a time
    Machine backup from the SSD to another blank HD and that one
    Crashed too.

    So now, I either have something
    Corrupt in my clean lion system or something else wrong… Or both.

    Also noteworthy, after my big fans ablazing
    Crash, 4 GB of Ram is not being recognized. I show 12 out of 16 GB. It could be that it overheated and malfunctioned. Now I have to Troubleshoot the memory risers and the ram modules. While I was testing, I did notice
    2 modules run hotter than others by using Temperature Monitor. Could this be related to the crash? Well it definitely doesn’t help!

    I’m back running the snow leopard-upgraded-to-Lion drive now that didn’t
    Have crashes. Gonna wait and see now. In the meantime, I will try updating the firmware on my SSD and reinstallin a plain vanilla lion to it. Will keep you posted.

    Oh lastly, I actually got KP reports now, buy
    Both reports show different crash reasons.

  27. Confirmed crash again. 🙁 This is with the 2.1 Firmware on 2 x Xeon X5355 CPUs. This time, I set Sleep to NEVER and Dim Screen to NEVER

    I left the house at 6:00PM and came back at 9:30PM. The screen stayed frozen at 6:30PM. So far, the only pattern I notice is that the system will crash ONLY when I’m not using the computer.

    1. @khai – Oh dear, any more crashes? Could they be other software you have installed that aren’t Lion compatible (things like LittleSnitch were causing lots of crashes in the early days for some people) or do you still think there’s an underlying issue with a MacPro 1,1 with upgraded CPU?

      I have now applied the MacPro 2,1 firmware hack to my MacPro 1,1 and was a little concerned when I first rebooted and my screen was flickering and un-readable at the login screen. I rebooted and held down CMD+ALT+P+R to reset the P-Ram and all seemed ok. I then removed the single 80GB test hdd I had in bay 3 and put back my 2x1TB RAID drives, wiped them clean and re-created the RAID and then tried to install Lion onto them and it kept hanging at the “installing” stage and until the 3rd or 4th reboot when eventually it started to install. Once in a fresh Lion install I had a good poke around and everything seemed good, about this mac correctly reported 2xQuad core CPU and system profiler showed me as a MacPro 2,1 [I’ll probably create another post with screenshots of the MacPro firmware updater]. I then ran software update until I was all up to date, installed iLife 11 and ran software update again to update all the iLife apps and it seems ok. I then tried using Carbon Copy Cloner to copy back the “data” files that I used to keep on that drive but screwed up my CCC settings and managed to over-write some important Lion files so when I came back to my machine Lion had frozen but not because of KP, because I over-wrote the system folder and a few other things. School-boy error so I need to rinse and repeat the whole process again. So that I’m back with a Lion install with all my data files and important apps and see how that goes.

      Once in Lion I still couldn’t use Disk Utility app to Verify and Repair my RAID array, it just does nothing.

      I have not (and probably will not) get rid of my other 2xRAID drives that have my all important 10.6.7 install on with all my iPhoto, music, etc files on until I’ve had at least a month in Lion without any major issues. Even then for the sake of 2x 1TB drives I might keep them as an emergency backup in my firesafe.

      How is everybody else getting on with Lion after applying the MacPro 2,1 firmware hack?

      Scoopz (Admin)

  28. Uh Oh.

    Got my first crash today but it was unusual. My computer console log shows that the last activity was at 8:41 AM and then nothing until 8:31PM (which was when I did a hard reset and turned it back on). When I came home today the Mac couldn’t be woken up and the fans were running full blast. Other than that, nothing meaningful shown in the logs.

  29. I’ve installed my X5355’s and updated to 2,1 now. It was fine for 24 hours then randomly I got a spinner up in the middle of the desktop and the screen went blank. I assumed it put itself to sleep somehow but I couldn’t wake it up so had to hard reset it.

    So far though, I’ve been up 2.5 days and it’s been fine.

    I’ll keep this updated though with my progress.

  30. Hey Scoopz,

    All smooth sailing for me, no issues in over a week, my system has been running smoothly the whole time. I’ve even uninstalled/upgraded a few apps, screen shared to/from a number of devices, transferred a bunch of network data and otherwise continued to put it through its paces, all without a hiccup. Remember how that used to be?! Hell it was probably the reason you bought a Mac in the first place!

    Again, I’m not suggesting this will necessarily work for you, your processors are different so will have to suck it and see.

  31. @Khai – thanks for all the info regarding the firmware upgrade being reversible and the links to http://www.xlr8yourmac.com/.

    I’ve not updated my firmware yet s9truggling to find enough hours in the day) but for everyones information my current, stock, Boot ROM version is:

    Boot ROM Version: MP11.005C.B08

    which according to your post on http://www.xlr8yourmac.com/ is the same as yours prior to upgrade. Here’s all the info listed in my stock MacPro 1,1 with upgraded CPU
    Hardware Overview:

    Model Name: Mac Pro
    Model Identifier: MacPro1,1
    Processor Speed: 2.33 GHz
    Number Of Processors: 2
    Total Number Of Cores: 8
    L2 Cache (per processor): 8 MB
    Memory: 14 GB
    Bus Speed: 1.33 GHz
    Boot ROM Version: MP11.005C.B08
    SMC Version (system): 1.7f10
    Serial Number (system): CK631xxxxxx
    Hardware UUID: 00000000-0000-1000-8000-001xxxxxxxx

    @poo – how is the MacPro 2,1 firmware doing, any crashes at all now after a few more days?

    @Jim – thanks for the heads up about only one CPU being recognised first time round and doing an SMC reset http://support.apple.com/kb/ht3964 that’s handy to know. I’d have probably freaked out if I rebooted and only saw 1CPU after the firmware upgrade.

    @Sam, @tragnar, @Manolo_ender and any others I’ve forgotten once again thanks for the feedback. If you have upgraded to MacPro 2,1 firmware and you’ve not had any more kernel panics please drop a quick comment back with number of days you’ve been KP free in an alcoholics-anonymous sytle

    “Hi my name is xxx and since applying Firmware 2,1 to my MacPro 1,1 I’ve been Kernel Panic free for xx days now”.

    Thanks everyone

    Scoopz (Admin)

  32. More info is being posted over at http://www.xlr8yourmac.com regarding this matter (linked back to this blog too).

    Sounds like some peeps are having some trouble updating their firmware.

    My firmware version PRIOR to the update is: MP11.005C.B08

    Another reader whose update failed has firmware: MP11.005D.B00, which seems to be the shipping firmware on some refurb MP 1,1 from 2007.

    The official firmware for 2,1 is MP21.007F.B06

    See this Apple article for more info:

    http://support.apple.com/kb/TS3029

    and then

    http://support.apple.com/kb/DL206

    Khai

  33. I installed the Firmware utility downloaded from netkas.org.

    Note that the first time you reboot after installing the firmware update, it will only recognize 1 of your processors. I reset the SMC and rebooted and both processors were recognized.

    I installed Lion on a different drive. Ran all the updates. 10.7.1 now.

    No “about this mac.pkg” to get the processors reporting correctly in Lion. That’s nice!

    No problems so far. I set the computer not to sleep or spin down the hard drives. Left it run over night.

    Before when I did this, I would come back to the computer at the login screen, indicating that it had restarted due to a KP.

    I am keeping my fingers crossed on this solution because it would be great to get a couple more years worth of use out of my upgraded Mac Pro.

    Just for reference, I’m running x5365 processors and a 5770 Apple Authorized video card in my Mac Pro 1,1.

    I will report back if I experience any problems.

  34. I also installed the Mac Pro 1,1 to 2,1 Firmware utility from netkas.org.

    I’m going to do a fresh reinstall of Lion and do all the updates and see how things go.

    I am really hoping this does the trick.

    I do not want to be stuck at 10.6.7 forever with this machine.

  35. Screw it, I’m confident enough to say that the 2,1 firmware update has done the magic. Stable for a week having left loads of apps running throughout that time and periodically stress testing via methods mentioned above. Can’t tell you how good it is to finally have my Mac back to good health! Hope this is the solution for others also. Planning to finally continue my upgrade path of buying new 5770, SSD and installing Lion. Scoopz, looking forward to hearing from you in particular and really hope it does the job for you! Your CPUs are different of course so won’t know until you try I guess.

  36. The firmware upgrade will be applied to the firmware on the machine, not the software of the startup disk. After the upgrade, ALL your boot volumes will say 2,1 instead of 1,1 in System Profiler (or whatever it’s called in Lion now).

  37. The EFI upgrade is entirely reversible.

    The app has two buttons: Upgrade to 2,1 and Downgrade to 1,1.

    If you originally had a 2,1 machine, you will get a warning against downgrading to 1,1. Otherwise, it works fine either way. You will have to go through the standard process of holding down the power button on startup to enter the firmware upgrade mode.

    The ONLY difference in hardware between the Mac Pro 1,1 and 2,1 is the CPU difference. All other components are EXACTLY the same including the use of EFI32. When the CTO dual-quadcore X5365 Xeons were officially introduced, Apple had it use 2,1 firmware. I presume that since there’s no other difference EXCEPT quad-core microcode support in 2,1 that Apple ONLY included that firmware if you CTO’ed the X5365. To have ALL Mac Pros use the 2,1 firmware would require dedicating engineering and testing resources for a firmware that offered no benefit for existing double-duo-core X51x0 CPUs.

    Now that we’ve all upgraded our CPUs, the changes in this firmware are now beneficial (actually, seems NECESSARY) to use Lion.

    lastly, EFI32 seems to be an artificial limitation as well. Seems like there’s a hack for that now to allow Mac Pro 1,1 (and 2,1) to book EFI64 by treating the machine as a REALLY compatible Hackintosh. Oh Joy!

    3 days and no crashes in Lion. I just beat my Mac Pro 1,1 record.

  38. @everyone – Right this firmware hack to make MacPro 1,1 appear as a MacPro 2,1 looks like it could be a winner. I’ve not tried it yet but I have been to the Netkas forum and downloaded it (you need to register to see the download). I was going to upload it to my server so you could download it from there but want to check with the creator first so for now if anybody needs it please download it from http://forum.netkas.org/index.php/topic,1094.0.html

    @poo – frequent updates aren’t bothering me at all, appreciate the regular feedback from everybody, should help others in the same situation find a solution quicker. How’s it going with the 2,1 firmware mask?

    Now I’ve not looked in depth at the difference between the 1,1 and the 2,1 original machines, was it literally that the 2,1 was a 1,1 with special built to order 2×4 core CPU? I know the 1,1 still uses a 32-bit EFI so the kernel task still runs in 32-bit whereas most of the recent Apple’s that can run Lion all have 64-bit EFI. What did the 2,1 have, was that 32 or 64 bit EFI? Even with a 32 bit EFI you can still run 64-bit processes it’s simply the core kernel tasks that run in 32-bit so may be a bit limiting but I’ve never come across any RAM intensive kernel processes that would benefit from 64-bit EFI so shouldn’t be too much of a problem. I just thought it could be a problem if the 2,1 had a 64-bit EFI and Lion tried to make use of this somehow thinking our 1,1 which now shows as a 2,1 had 64 bit too.

    Since I’ve not run the app yet to change to a MacPro 2,1, can anybody tell me if it’s a reversible process and whether it’s specific to a boot drive or a global setting? Since I still have a good Snow Leopard 10.6.7 installation on a different set of drives, if I apple the 2,1 patch to my Lion install will my MacPro show as a 2,1 in my Snow Leopard too or just the Lion install?

    I did notice the guy said he’s working on an EFI/SMC upgrader? Not sure if that could help us too?

    Scoopz (admin)

  39. Hope my frequent updates aren’t annoying anyone, if so just tell me to shut up! Figured any additional info is helpful at this stage from as many owners having these issues as possible.

    Have tried as many things as I can think of to trigger a KP, but so far system is stable post 2,1 firmware. Have run my CPU cores at 100% (as per Scoopz tutorial here), run every app I can at the same time, loaded both screens with HD and high bitrate video whilst playing lossless audio and opening a ton of RAW files in Camera RAW with Bridge, Lightroom etc processing files and XLD encoding FLAC to ALAC. All handled very nicely (slowly as you’d expect with so many processes running concurrently, but no issues). These tasks brought my system temps up to twice the highest temps I have been able to sustain in the past weeks/months. During prior efforts I saw cores peak around 48°C before triggering KP, now I can reach 98°C (the highest I could push system to) with no issues (not that I’d want to do it long term!)

    I’m still not 100% that my problems are solved until I’ve survived a week or so with no restarts, but all good so far…

  40. I’m also having issues on E5345 cpu’s in an 06/1,1 Mac Pro. I get a KP every week or so of running. You can almost predict it.

    I’ve been pulling my hair out for ages over the issue but have resorted to buying some X5355’s to try. They should be here tomorrow. I’ll also try the 2,1 firmware update that’s on the netkas forum tonight.

  41. The 2,1 supposedly has some
    Undocumented quad-core CPU fixes
    in the microcode which Lion might be utilizing.

    Previously, I assume the 2,1 firmware was not
    necessary and there’s a thread on macrumors.com chronicling this. Well, at least until now. 2 days an no crashes now…

  42. Hi Guys,

    I had the same problem – updated my MacPro 1,1 with 2 Quad Cores and everything worked perfect up 10 10.6.7 – with 10.6.8 and all Lion I had up to 4 or 5 panics a day. Now updated the Firmware with the tool from netkas forum to 2,1 and my Pro is rock solid again – no panics for 2 days now.

    And as a plus – since the firmware update my Plex Media Center setup (MacPro is the server, a mini is the client) works again without any stuttering during playback. Somehow the Pro had network stutter every 5-10 minutes. This is also solved.

    I am so happy you won’t believe it 😉
    Thanks for the tip!

    Tragnar

  43. Well Khai/Scoopz the firmware tool has worked for me in terms of my machine now being recognised as 2,1, so will be interesting to see if the fixed system identifier has any impact on my KP issues. Fingers crossed I guess, though TBH I’m not expecting it to. Appreciate the link/advice regardless Khai, thanks.

  44. Sounds awesome Khai, thanks for the link! I had been trying to find a way to do this on non hackintoshes (for which this sort of tool seems in abundance) with no luck, so your comment is very well timed. Will try it out shortly and post back with any results.

  45. Hi,

    Sorry for my English. I also think that the problem could be in firmware. My system has 2 x quad core xeon 5320. I’ve had no crashes since Thursday at noon. Before my system would crash every 5-7 hours

  46. Okay, make sure you register on the netkas.org forum to actually get the download link to the firmware tool. It’s easy. Only two buttons: Upgrade to 2007 2,1 firmware or downgrade to 2006 1,1 firmware.

    My X5355 Xeon is now officially recognized in Lion instead of showing as Unknown CPU. It shows as 2.66 GHz Quad-Core Intel Xeon now. Previously in Snow Leopard, I would have to install a software tool for the OS to report as the right CPU type but that Tool no longer works in Lion. Now I’ll just sit and wait for a crash!

  47. So I can verify crashes with Lion on a clean from scratch Lion on SSD and also an upgraded from Snow Leopard on a 1TB drive. I guess that likely rules out the mass storage as the problem.

    Only thing left are the CPUs… 🙁

    Here’s an unsupported tool, but reversible tool that upgrades the Mac Pro 1,1 to a Mac Pro 2,1. The Mac Pro 2,1 supported dual quad-core Xeon X5365 CPUs, which were 3.0 GHz OEM CPUs from Apple.

    Perhaps this might help? I’m going to try it myself.

    http://forum.netkas.org/index.php/topic,1094.0.html

  48. Yeah perhaps that’s part of the problem then. Mine is listed as 1,1 as you’d expect. Your 5345’s aren’t standard issue either I suppose? But then neither is 5355 and others seem to be running 5365 and 5355 with no KPs. You’d expect it to be all or nothing.

  49. @Poo – You’ve been reading the same page as me lol but what stands out to me is that the MacPro 1,1 was only ever a quad core machine. Further down the page you linked to if you expand all boxes it says

    “*The custom configuration of the original Mac Pro with two 3 GHz Quad Core Xeon X5365 processors identifies itself as MacPro2,1. It has a variety of different characteristics in addition to a different model identifier and EveryMac.com has documented it as its own model.”

    So a MacPro 1,1 customised with 2xquad core CPU (X5365) was no longer known as a MacPro 1,1 and was designated a MacPro 2,1.

    So at the moment with your X5365 installed if you go to About this Mac is it listed as a MacPro 1,1 or MacPro2,1?

    This could be part of the problem? Perhaps we need to look at changing the system identifier from MacPro 1,1 to MacPro 2,1 after upgrading from Quad to Octo core?

    Don’t worry, I’ll keep pursuing this for as long as possible, or at least until Thunderbolt enabled MacPro’s are released.

    Might be time to have a look on eBay and see how much MacPro2,1 are going for.

    Scoopz (admin)

  50. The first Intel-based tower Mac, the Mac Pro “Quad Core” 2.66 is powered by two 2.66 GHz dual core Intel Xeon 5150 processors with 4 MB of shared level 2 cache per processor, a 128-bit SSE3 vector engine, and 1.33 GHz “64-bit dual independent frontside buses.” Also offered, via custom configuration, were two 2 GHz Dual Core Xeon 5130 processors, two 3 GHz Dual Core Xeon 5160 processors, or starting April 4, 2007, two 3 GHz Quad Core Xeon X5365 (Clovertown) processors.

    http://www.everymac.com/systems/apple/mac_pro/stats/mac-pro-quad-2.66-specs.html

    And more detail: http://www.everymac.com/systems/apple/mac_pro/faq/mac-pro-different-configuration-options.html

    Frustrating as it all is, It’s encouraging to see some of us are still pushing Apple for an answer. My understanding from the info above is that my current system is identical to that from April 4, 2007 when Apple began offering a system via custom configuration with two 3 GHz quad core Xeon X5365 processors (eight cores total) for an additional US$1498.

  51. @Khai – welcome to the “Lion causes kernel panic” club, it’s a small club but growing everyday 🙂

    I have 2xVertex 2 SSD in a RAID array which run 10.6.7 perfectly (and blazing fast) but it’s interesting that you say you can run 10.6.8 without issues?! I have the same kernel panic with 10.6.8 as I do with Lion.

    What is becoming more and more apparent is that everybody having KP with Lion have upgraded CPU. So it might be something Apple won’t fix.

    Scoopz (admin)

  52. @Jim – glad (if that’s the right word) to have you onboard as another user with the same problem. I’m still rocking 10.6.7 all nice and stable whilst experimenting with 10.6.8 and Lion on spare internal drives. Even a fresh install of 10.7.1 downloaded from the App store on an non-RAID drive kernel panics. Do you still have your original CPU to reinstall and test? I also suspected RAM could be a cause so bought brand new 8GB and ran with just the new stuff installed and kept the older stuff out and it still KPs. I also tried running with just my original 1GB RAM that came from the factory and still KP.

    Scoopz (admin)

  53. I am also having KP, crashing issues after I upgraded my Mac Pro 1,1.

    I have x5365s installed.
    Also, upgraded the video card to ATi 5770 (apple authorized card)

    Stable in 10.6.7
    KPs in 10.7 and 10.7.1
    KP in 10.6.8, come back to computer…it’s asleep. Wake it up. It’s at login screen. Computer set not to sleep.

    Rolling back to 10.6.7 fixes all issues.

    It’s got to be something in 10.6.8. I remember years back when Apple tightened their RAM specs and that caused problems. They must have put something in.

    Which sucks because I really liked running 10.7.x.

    I tend to get bored and like upgrading. Sitting with a perfectly fine running machine at 10.6.7 might be great for some but not for me.

  54. Thanks for this post. I’m going nuts in a similar way:

    Mac Pro 1,1
    Apple 30″ Cinema Display
    2 x Xeon 5355 2.66 GHz CPU Upgrade
    240 GB Vertex 3 SSD (Lion 10.7.1 Boot Volume)
    16 GB Memory
    ATI Radeon 5770 (Sapphire Flashed PC Card)

    Stable in 10.6.7 AND 10.6.8 (Running on a 1 TB Seagate Drive)

    I installed a fresh Lion install onto my SSD. I had problems with that (stuck beach balls on IO operations) and upgraded my SSD firmware which fixed it.

    However, I have an assortment of crashes:

    Leave computer on overnight/couple of hours and come back only to find that it’s back at the login screen because it had rebooted (No message of previous unexpected reboot).

    System is set to never sleep

    Sometimes, I will come back the computer and it becomes completely unresponsive. Nothing on the screen either. Unresponsive caps locks light is a sign that something went wrong.

    I don’t know if it was because of Lion, the CPU upgrade, or the SSD…. or all of the above.

    Putting back in my SL 10.6.8 HD runs well..

    Gonna run a series of stress tests now. I REALLY don’t want to put back in my stock CPUs and reformat my SSD but that may be my last bet.

    Next up is upgrading my SL HD to Lion and see if I still have the same problems. Would love to hear an update when you are able and hope that 10.7.2 fixes it all.

    In the past, all the 10.x.2 releases have always fixed my problems. 🙂

  55. Still on 10.7.1, no KPs for 11days, 10hours, 35minutes. I believe in part my issue was related to Mail not liking AOL’s mail server.

    I’ve also re-installed Flash 11 Beta as of 11days ago.

    Also knocking on wood.

    ~TitanNode

  56. Umm nothing really doesn’t say say in the box TBA obviously fr=or To be Annouce but i would assume so because i have zero Kp’s thus far “knock on wood” Temp run any where from 30 to 40 c . But i would try it if i were you download a torrent of it. But, to be honest all the KP’s i see people have or report on are usually with the E5345. But not all with those CPU’s i got my pair of X5355’s for only 265. So i would first try to install 10.7.2 and see if that fixes it but if not try to sell the E5345 and get the x5355’s. Idk though.

    So on the stability part i have run my machine for 2 days straight and didn’t turn it offf and still no signs of KP’s.

  57. STATUS UPDATE! So i have finanally done the upgrade i got the cpu’s today and all is well more then excpected so far i am running 10.7.2 11C40 and have a RAID, Little Snitch, and all other things i am running that may have caused a KP. So far so good but the only problem i see potentially is the Artic Silver #5 and the heat temp is idling at 36 C and 97 F hopeflly this changes soon. Otherwise all is well “knock on wood” for no KP’s. But was wondering is this tempeture normal? With the X5355’S

    1. @klaus38585 – Congrats on the upgrade. Hopefully you might not experience any KPs. So I take it you are running the developer seed of 10.7.2 as the current consumer seed is 10.7.1. What is new in 10.7.2, anything to do with “stability” or “bug fixes”?

      I don’t know what the idle temp is for your X5355 but my E5345 idle at around 37°C to 40°C when my ambient air temp is 20°C and when I stress test my CPUs (http://blog.scoopz.co.uk/2011/08/17/stress-test-your-cpu-on-an-apple-mac-running-os-x-and-monitor-core-cpu-temperatures/) the CPU core temps go up to 68°C at most which from what I can tell is perfectly acceptable for my E5345.

      I’m starting to wish I’d gone for X5355 or X5365 now rather than an E5345. I don’t have the time at present to install my original dual core CPUs and see if that stops my KPs. It’s frustrating that some people with upgraded CPU run Lion fault-free whilst some have KPs.

      Keep us updated if it remains stable over the next few days.

      Scoopz (Admin)

  58. Hi Scoop,

    An update for all:

    As I promised, I updated to 10.7.1 on the 19 Aug. and the my system crashed about 9 hours ago. I’ve attached my system profile and note that Im’ running SMC 1.7f10, is that the latest? Also, does anybody see any issues with the ATI 4870?

    One other item to note that every time it’s been crashing, I’ve been seeing these errors in the system log, see any correlation or any significance? NOTE: I’ve done a find/replace on my hostname and username, they were replaced with “SystemName” and “myusername” and I know AOL sucks, it’s my partner’s account. 😉

    ==============================
    Aug 22 11:31:04 SystemName iCal Helper[7025]: WARNING: moveItemAtPath:/Users/myusername/Library/Calendars/Calendar Cache toPath:/Users/myusername/Library/Calendars/Calendar Cache~1 failed: Error Domain=NSCocoaErrorDomain Code=513 ““Calendar Cache” couldn’t be moved because you don’t have permission to access “Calendars”.” UserInfo=0x7fee458294e0 {NSUserStringVariant=(
    Move
    ), NSDestinationFilePath=/Users/myusername/Library/Calendars/Calendar Cache~1, NSFilePath=/Users/myusername/Library/Calendars/Calendar Cache, NSUnderlyingError=0x7fee4598e190 “The operation couldn’t be completed. Permission denied”}
    {
    NSDestinationFilePath = “/Users/myusername/Library/Calendars/Calendar Cache~1”;
    NSFilePath = “/Users/myusername/Library/Calendars/Calendar Cache”;
    NSUnderlyingError = “Error Domain=NSPOSIXErrorDomain Code=13 \”The operation couldn\U2019t be completed. Permission denied\””;
    NSUserStringVariant = (
    Move
    );
    }
    Aug 22 11:31:04 SystemName iCal Helper[7025]: WARNING: CalCalendarStore: remove persistent store failed
    Aug 22 11:31:04 SystemName com.apple.launchd.peruser.502[1093] ([0x0-0x39d39d].com.apple.iCal.helper[7025]): Exited with code: 1
    Aug 22 11:31:11 SystemName PubSubAgent[7034]: EntryCore: Multiple authors not supported yet (ignoring subsequent ones)
    Aug 22 11:31:39 SystemName Mail[1107]: Error writing to /Users/myusername/Library/Mail/V2/[email protected]/.mboxCache.plist: Error Domain=NSCocoaErrorDomain Code=513 “You don’t have permission to save the file “.mboxCache.plist” in the folder “[email protected]”.” UserInfo=0x7ff1adde5d40 {NSFilePath=/Users/myusername/Library/Mail/V2/[email protected]/.mboxCache.plist, NSUnderlyingError=0x7ff1add93140 “The operation couldn’t be completed. Permission denied”}
    Aug 22 11:46:14 SystemName Mail[1107]: Error writing to /Users/myusername/Library/Mail/V2/[email protected]/.mboxCache.plist: Error Domain=NSCocoaErrorDomain Code=513 “You don’t have permission to save the file “.mboxCache.plist” in the folder “[email protected]”.” UserInfo=0x7ff1b1b1e040 {NSFilePath=/Users/myusername/Library/Mail/V2/[email protected]/.mboxCache.plist, NSUnderlyingError=0x7ff1abeeada0 “The operation couldn’t be completed. Permission denied”}
    Aug 22 11:54:52 SystemName LKDCHelper[7050]: Starting (uid=501)
    Aug 22 11:55:14 SystemName Mail[1107]: Error writing to /Users/myusername/Library/Mail/V2/[email protected]/.mboxCache.plist: Error Domain=NSCocoaErrorDomain Code=513 “You don’t have permission to save the file “.mboxCache.plist” in the folder “[email protected]”.” UserInfo=0x7ff1af1e45f0 {NSFilePath=/Users/myusername/Library/Mail/V2/[email protected]/.mboxCache.plist, NSUnderlyingError=0x7ff1af1bae40 “The operation couldn’t be completed. Permission denied”}
    Aug 22 11:59:22 localhost bootlog[0]: BOOT_TIME 1314039562 0

    ==============================

    System Profile:
    Model: MacPro1,1, BootROM MP11.005D.B00, 8 processors, 2.66 GHz, 16 GB, SMC 1.7f10
    Graphics: ATI Radeon HD 4870, ATI Radeon HD 4870, PCIe, 512 MB
    Memory Module: DIMM Riser A/DIMM 1, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, 0x4B494E4753544F4E00000000000000000000
    Memory Module: DIMM Riser A/DIMM 2, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, 0x4B494E4753544F4E00000000000000000000
    Memory Module: DIMM Riser B/DIMM 1, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, 0x4B494E4753544F4E00000000000000000000
    Memory Module: DIMM Riser B/DIMM 2, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, 0x4B494E4753544F4E00000000000000000000
    Memory Module: DIMM Riser A/DIMM 3, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, 0x4B494E4753544F4E00000000000000000000
    Memory Module: DIMM Riser A/DIMM 4, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, 0x4B494E4753544F4E00000000000000000000
    Memory Module: DIMM Riser B/DIMM 3, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, 0x4B494E4753544F4E00000000000000000000
    Memory Module: DIMM Riser B/DIMM 4, 2 GB, DDR2 FB-DIMM, 667 MHz, 0x0198, 0x4B494E4753544F4E00000000000000000000
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.11)
    Bluetooth: Version 2.5.0f17, 2 service, 19 devices, 1 incoming serial ports
    Network Service: Ethernet 1, Ethernet, en0
    PCI Card: ATI Radeon HD 4870, sppci_displaycontroller, Slot-1
    Serial ATA Device: Hitachi HDS721050CLA362, 500.11 GB
    Serial ATA Device: Hitachi HDS721050CLA362, 500.11 GB
    Serial ATA Device: Hitachi HDS721010CLA332, 1 TB
    Serial ATA Device: Hitachi HDS721010CLA332, 1 TB
    Parallel ATA Device: PIONEER DVD-RW DVR-112D, 1.52 GB
    USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd400000 / 2
    USB Device: Razer Imperator, 0x1532, 0x0017, 0xfd430000 / 4
    USB Device: Apple Keyboard, apple_vendor_id, 0x0220, 0xfd420000 / 3
    USB Device: Polycom CX300, 0x0e0f (VMWare, Inc.), 0x0001, 0x3d100000 / 2
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8206, 0x5d200000 / 2
    USB Device: Smart Card Reader USB, 0x0e0f (VMWare, Inc.), 0x0001, 0x1d200000 / 2
    FireWire Device: iSight, Apple Computer, Inc., 200mbit_speed
    FireWire Device: built-in_hub, 800mbit_speed
    FireWire Device: LaCie Rugged LUN 0, LaCie Group SA, 400mbit_speed

  59. Hi,

    I used to have the E5320 with BSEL mod @ 2.33Ghz in my Mac Pro 1.1, KP happened a lot in 10.6.8 or even 10.7.1

    Without the BSEL mod, E5320 @ 1.8 Ghz ran fine under 10.6.8 but KP in Lion all the time.

    I have tried to remove my RAID and OWC Mercury Pro SSD, but it did not help, still KP.

    Now I am with E5345 @ 2.33ghz in 10.6.7, no KP at all. IF i boot into 10.7.1 or 10.6.8, there is a ton of KP.

    Oh mi god. it is driving me crazy. Guess that I am gotta stick with 10.6.7 for a while.

  60. @scoopz yes using Disk Utiliy to create the RAID. Also, when i do or choose to upgrade i have the X5355’s and how do those fair with Mac OS X Lion or Disk Utility Software RAIDS. Also if you know any other KP’s that may be involved please tell me asap loved to know some more things i have to look out for thx

  61. @poo – first update 10.7.1 did nothing to help as suspected. Still lots of KPs

    @Bee – bookmark this post, if I find a solution I will post it here, likewise, if you find out a cause or a fix please update me.

    @TitanNode – How did the 10.7.1 update go, I bet it hasn’t stopped the KPs? I thought this problem may have been limited to those upgrading to E5345, I know some with X5355’s have had no issues.

    @klaus385385 – Just so you know, I am getting KP’s with my E5345 on a clean Lion install. I have also never used Little Snitch although I do know that Little Snitch *did* cause KPs for some users so check for an updated version if you use it. When you say Software RAID, are you referring to RAIDs setting up using Disk Utility in OS X or are you referring to SoftRAID software http://www.softraid.com/faq.html which I think was known to cause problems with Lion?

    I’ve also updated the post above with my latest findings.

  62. TitanNode and Bee quick question. Either of u know why u r having kp’s? Does it have any relation to Mac OS X Lion or Little Snitch or finally Software RAIDs? If not loved to know what because i am getting my CPU’son Wed according to the tracking and want to know what not to do to cause KP’s after the upgrade. K Thx

  63. Hi Scoop,

    I have the same issue as you and I wanted to thank you and poo for doing such an outstanding job of documenting this. I did the same thing by upgrading my Mac Pro 1,1 with 2 Xeon x5355’s thinking all should be fine with this.

    I’m updating my Mac Pro to 10.7.1 right now. Since upgrading to Lion, the 1st KP took 13 days, the 2nd took only 7. I’ll let you know if the 10.7.1 update changes anything.

    And again, THANK YOU!

    Cheers!

  64. Hi scoop,
    I got the same Mac Pro 1.1 and E5345s like your. After I replaced the CPUs, I got a ton of KP on 10.6.8 and even Lion 10.7.1 . I was too frustrated. I just rolled back to 10.6.7 today and see how it goes in the coming days. Hope things go well for both of us.
    Cheers,

  65. wow thx for this article without i feel like 10.6.7 is the best bet with x5355’s hope fully its not the software raid or the cpus’s in general cannot wait for an update.

  66. Hey again. I think you mentioned that you don’t have little Snitch installed (I do) but just thought worth mentioning that they have updated to version 2.4.2 because of issues with KPs. From their site: Little Snitch 2.4.2 – August 8, 2011 Improves OS X Lion compatibility, fixes a kernel panic. Had an ‘old style’ KP earlier today with the report and data log info, rather than the random restarts I’ve been experiencing lately. Will be interesting to see how the next few days pan out after my update, almost expect to go back to the random no report restarts! Starting to think I have 2 issues happening at once: Little Snitch whatever this unknown issue is. Any hint of problems after I update LS and I’ll be uninstalling.

  67. Thanks for the reply. Interesting to hear you aren’t getting the logs/reports now either! Seems that’s happened to both of us around the same time as well, surely not just a coincidence?

  68. @poo – I’ve not done anything since my last update in the post on 5th August. I’ve got too much work on at the moment to risk having an unusable machine so I’m waiting for a gap in the work to progress with investigations, for now I’ve just been cloning all my data onto my MacMini Server ready for recovery later.

    After changing my GPU I did notice that the system just reboots and nothing is logged in the /Library/Logs/ and no prompt to submit a report to Apple. Not sure why that is though.

    Since the Hackintosh people have been having the same problem and are blaming the ACPI_SMC_Platformpligin.kext I did briefly try their method to fix which involved running “multibeast” but after doing that the OS X became unbootable so I gave up on that. What I am going to try though is installing a fresh Lion and then copying the ACPI_SMC_Platformpligin.kext from my 10.6.7 over and replacing the Lion one and see what that does.

    Like you I think I’ll be waiting for an Apple fix on this or putting the old CPU back in (glad I didn’t sell them now) and see if that fixes it. If it does and it’s purely upgraded CPU that cause the issue then I’ll just sell the CPU or keep new CPU in and just sell MacPro with 10.6.7 to somebody and let them deal with the problem (bit harsh though).

    Scoopz (Admin)

  69. Imagine you would have posted if you had anything, but thought I’d ask how things are going for you? My machine seems to just restart without warning now, less frequently than before I think, but no KP reports or anything of the sort. Not sure if that means I had issues with KPs as well as something else or if my machine is just restarting before it has a chance to generate any info. Feeling pretty lost as to what to do other than replace the old CPUs, crossing fingers all’s well and selling the 5365s. Then I guess I’ll be waiting for new Mac Pros to ship, though not keen on the inevitable $$$

  70. @poo – I’ve just checked iStat Nano and my stats are
    CPU A 30ºC
    CPU B 33ºC
    Power Supply 599rpm
    Exhaust 599rpm
    CPU 499rpm
    HD/Expansion 499rpm
    and mine with KP even sat at the login screen sometimes. Ambient air temp in the UK has never really gone above 20ºC so I don’t think it’s temp related in my instance.
    Scoopz (Admin)

  71. @poo – I had installed smcFanControl on my 10.6.8 installation as I too saw CPU temps slightly higher than 10.6.7 but even with them all maxed out and making one hell of a racket I still had KP so I ruled temp out. Having said that, I will try reinstalling smcFanControl in Lion (if it’s compatible) and see what effect if any it has.

    It is 100% an issue with 10.6.8 (and subsequently carried through to Lion) and if you roll back to 10.6.7 I’m almost positive your KP problems with go away.

    I couldn’t believe how easy it was to roll back to 10.6.7 from 10.6.8 just using the original install CD and the 10.6.7 combo updater from Apple. Having had to reinstall Windows on computers before it’s pretty much a wipe and start from scratch with Windows, refreshing change with OS X.

    If my RAM tests are all clear and the RAID isn’t the problem, since you aren’t using RAID, then I’m going to be pretty stumped on this one and have to wait for Apple to pull something out the bag. If you have an Apple account submit a bug report http://bugreport.apple.com and upload your kp logs. I don’t mind sticking with 10.6.7 for a few weeks/months if a fix from Apple is on the horizon, if it’s not then I’ll be sticking the MacPro on eBay running 10.6.7 and get new one but no point in doing that until the refresh model with Thunderbolt is out.
    Scoopz (Admin)

  72. Hey,

    Damn I really had it all crossed that your video card was going to solve things. I replied last night in the Apple forum you had posted in. I’d be very surprised if RAID is the culprit, I’m having the same issues you are and have no RAID devices/drives configured/installed. I agree with your comment that this seems to be something to do with 10.6.8 (I haven’t installed Lion so can’t comment). I also get the impression that (in my system at least) CPU temp could be an issue, which is why I mentioned smcFanControl in the Apple post. I’m currently testing this and will let you know if I find anything. Next step for me will be to roll back to 10.6.7 as you tried and see if I have Kps or if it’s smooth sailing as you experienced.

Leave a Reply to Poo Cancel reply