Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Kernel Panic Crash Report Reading Help?

Hi all.

Since updating to Lion the other day and plugging my Mac Pro into a CyberPower 1500 SineWave UPS battery backup, I've kernel paniced twice i the last 2 days including just this morning. Can anyone read the resulting crash reports after I restarted. I can't, but notice that the opening lines seem quite similar regarding the panic. Any help deciphering will be much appreciated. In the first panic it seemed that my video card (original) was involved, but in this morning's panic the card isn't referred to, or at least at all like in the first report from this past Saturday:

Interval Since Last Panic Report: 34769 sec

Panics Since Last Report: 1

Anonymous UUID: ACD0641E-663F-43B6-97E8-154AF6A74301

Sat Jun 16 17:51:48 2012

panic(cpu 2 caller 0x2b1391): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x10, NMIPI acks: orig: 0x0, now: 0x0"@/SourceCache/xnu/xnu-1699.26.8/osfmk/i386/pmap.c:3024

Backtrace (CPU 2), Frame : Return Address (4 potential args on stack)

0x7b6eb918 : 0x2203de (0x6afa8c 0x7b6eb938 0x229fb0 0x0)

0x7b6eb948 : 0x2b1391 (0x6b80ac 0x10 0x0 0x0)

0x7b6eb998 : 0x2b44d5 (0x867960 0x6ccc8000 0x0 0x6ccc9000)

0x7b6eb9f8 : 0x28667e (0x16ff84 0x0 0x0 0x0)

0x7b6eba58 : 0x2789a1 (0x15c0b1c8 0x0 0x0 0x3000)

0x7b6ebb18 : 0x279a65 (0x0 0x6cccb000 0x0 0x1)

0x7b6ebb48 : 0x27231d (0x372de04 0x6ccc8000 0x0 0x6cccb000)

0x7b6ebb78 : 0x225e51 (0x372de04 0x6ccc8000 0x2220 0x2263e9)

0x7b6ebb98 : 0x64079d (0x6ccc8000 0x2220 0x7b6ebbb8 0x1ad4f2a)

0x7b6ebbb8 : 0x1adf7a0 (0x6ccc8000 0x2220 0xfa0000 0x1)

0x7b6ebbe8 : 0x1ae0026 (0x6cece000 0x15a085c8 0x15a085cc 0x15a085d0)

0x7b6ebc48 : 0x67e6df (0x6cece000 0xf9d2f6c 0x15a085c8 0x28)

0x7b6ebc78 : 0x67fb0a (0x1b603c8 0x6cece000 0xf9d2f6c 0x28)

0x7b6ebcd8 : 0x68039f (0x6cece000 0xb 0x7b6ebd08 0x0)

0x7b6ebdd8 : 0x2accc0 (0x6cece000 0xb 0xf9d2f68 0x0)

0x7b6ebed8 : 0x222db6 (0xf9d2f40 0x15a085a0 0x7b6ebf0c 0x2c3f24)

0x7b6ebf08 : 0x214063 (0xf9d2f00 0xd6cc3f0 0xe4922a0 0xf9d2f00)

0x7b6ebf48 : 0x21b25b (0xf9d2f00 0x0 0x0 0x0)

0x7b6ebf98 : 0x2b7bb7 (0xdaa4c14 0x7fff 0xdaa4c44 0x8)

0x7b6ebfc8 : 0x2e5d77 (0xdaa4c10 0x1 0x10 0xf3e4250)

Kernel Extensions in backtrace:

com.apple.GeForce7xxx(7.0)[30106D54-20CB-4068-BAC6-665D155441FA]@0x1ad2000->0x1 ba8fff

dependency: com.apple.iokit.IOPCIFamily(2.6.8)[8A2C8EA4-92F9-443B-A6BF-28CCA76A7025]@0xb690 00

dependency: com.apple.iokit.IONDRVSupport(2.3.2)[B62F3896-89EF-4A95-84F9-50181801C2DF]@0xc3 5000

dependency: com.apple.NVDAResman.G7xxx(7.0.0)[19574FFC-E5A6-403D-8077-E25DA1FD6D3E]@0xc4600 0

dependency: com.apple.iokit.IOGraphicsFamily(2.3.2)[8C92F8ED-66CB-43CB-947D-AEF8B0DB06B3]@0 xc03000

BSD process name corresponding to current thread: WindowServer

-------------------------------------------

Interval Since Last Panic Report: 184108 sec

Panics Since Last Report: 2

Anonymous UUID: ACD0641E-663F-43B6-97E8-154AF6A74301

Wed Jun 20 11:54:37 2012

panic(cpu 2 caller 0x2b1391): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x2, NMIPI acks: orig: 0x0, now: 0x0"@/SourceCache/xnu/xnu-1699.26.8/osfmk/i386/pmap.c:3024

Backtrace (CPU 2), Frame : Return Address (4 potential args on stack)

0x97733bb8 : 0x2203de (0x6afa8c 0x97733bd8 0x229fb0 0x0)

0x97733be8 : 0x2b1391 (0x6b80ac 0x2 0x0 0x0)

0x97733c38 : 0x2b4cd1 (0xcbd90dc 0xb0185000 0x0 0xb0186000)

0x97733cb8 : 0x2b53dc (0xcbd90dc 0xb0185000 0x0 0x7b5e3c28)

0x97733cf8 : 0x2789cf (0xcbd90dc 0xb0185000 0x0 0xb0186000)

0x97733db8 : 0x279a65 (0x0 0xb0186000 0x0 0x0)

0x97733de8 : 0x2a3a7b (0xd71f41c 0xb0185000 0x0 0xb0186000)

0x97733e18 : 0x2a46bb (0xd71f41c 0xb0185000 0x0 0x1000)

0x97733e38 : 0x2631ac (0xd71f41c 0xb0185000 0x1000 0x211620)

0x97733e68 : 0x222db6 (0xfcdaa94 0xded3598 0x97733e9c 0x2c3f24)

0x97733e98 : 0x214063 (0xfcdaa00 0xdb13ce0 0xedeff50 0xfcdaa00)

0x97733ed8 : 0x21b25b (0xfcdaa00 0x0 0x0 0x0)

0x97733f28 : 0x2b7e16 (0x97733f50 0x0 0x97733f9c 0x1c)

0x97733fc8 : 0x2e5867 (0xda19ad0 0x0 0x10 0xda19ad0)

Mac Pro 3.0 GHz Quad-Core, iPad WiFi/3G, iPhone4, Mac OS X (10.6.8), 30" HP Display, 22" Cinema Display

Posted on Jun 20, 2012 10:18 AM

Best reply

Grant Bennet-Alder

Level 10

127,165 points

Posted on Jun 20, 2012 10:40 AM

That is the Firmware-related kernel panic some users get when upgrading to quad processors on the Mac Pro 1,1.

Time for the Firmware update readers referred to in your earlier posts.

View in context

37 replies

The hatter

Level 9

60,990 points

Jun 24, 2012 3:45 PM in response to Steven Shmerler

on tablet, so briefly... catch-22 or oxymoron but... 8-core ! not ever 1,1

only 2,1

yes BTO $1400 extra for 3GHZ 8-core

that is WHY those DIYers NEED the 2,1 firmware for their own 8-core upgrade for same reason it exists to begin with

Apple doesvnot share secrets and "level n techs" are hard to reach, not forhcoming, and respond as much to your own level of question & understanding.

look at how long it akes to explain and get to bottom, unfathom, this.

there are rules: 8 cores requires special firmware

if you were running windows there are many good easy tools to show cpu chip details, manuf date, stepping, batch etc

Jun 24, 2012 4:41 PM in response to Steven Shmerler

You participated in this thread:

https://discussions.apple.com/thread/3946954?answerId=18686428022#18686428022

Did you not install that utility?

If you did not, my apologies -- I preumed you had installed it.

Jun 25, 2012 5:21 PM in response to Grant Bennet-Alder

Grant and Hatter!

I have some amazing news!

Based on the Data Capture and crash reports I've submitted to AppleCare, the Apple Engineers have determined that it appears the wrong motherboard (and thus FW) was installed at the Factory. Yup!

Then when I brought my crashing MP into the Apple Store, given Apple's policy of replacing "like with like", they simply assumed I had a failing MB, instead of the more obscure diagnosis that the problem wasn't a failing MB but having the wrong MB installed in the first place. So, unfortunately, the store replaced the wrong MB with the same wrong (but new) MB, and the problem lived on...

WHAT NEXT? Apple is going to replace the motherboard correct for an 8 core machine (versus 4 core), AND they are replacing my video card to be sure AND doing all this on site at my home!

The plan is to keep my software/hard drive "as is" so that if I don't crash after the hardware replacement, then we know it was the hardware/firmware. If it does crash, then we have to press on and look at other hardware and/or software issues.

I am a bit blown away that Apple admitted a mistake of so many years ago and are fixing it to the level they are and at my home to spare me yet another trip to the store 🙂

Hopefully this is the beginning of a happy ending. The repair is set to happen in a few days. I will let you know, if all works out and stablizes.

Thanks so much for all your comments, education and support.

Steven

The hatter

Level 9

60,990 points

Jun 26, 2012 5:31 AM in response to Steven Shmerler

Apple missed and messed up and you had me pulling my hair on this one.

When PowerMac G5's had trouble with their cooling system Apple also stood behind customers and when replaced systems with Mac Pro models.

One of our fellow members here had a crashing Quad G5, not cooling system related, and they had to swap out the logicboard three times to get it right - so CS2 was eventually running stable - on site, right there.

it is an education for us too you realize <g>

Congrat & good luck!

Jul 18, 2012 1:46 PM in response to The hatter

Hatter and Grant,

AppleCare finally determined that Apple Store that worked on my Mac Pro replaced the wrong motherboard which also seemed to be telling the firmware file that is dual purpose and will install the correct FW based on what it thinks is correct. So apparently, my motherboard was telling the FW installer to install the first gen FW and perhaps because my Mac ID said: MacPro1,1, there was no way around this and the install file would always default to MP11 versus MP21 FW.

I decided to allow AppleCare to replace the board and vid card since they promised to stay with me and support me if this didn't work, or if the having the wrong MB in there hurt other components like RAM or the power supply, etc.

They did the repair and then my MP wouldn't start up at all! After that, seeing things were only going from worse to way worse, they said no more repairs and that they were going to replace my 2006 2x3 GHz 8 Core MP with a mid 2012 - 3.2 GHz Quad Core 6 GB RAM which was what my other thread about RAM pertains to that you just answered 🙂

I assume my MP was a bit more computer than what I have now, but then, the components were older, slower and my buss was a real bottoneck so I don't notice any slow down with my new MP over my old MP and I don't do any serious rendering or serious CPU intensive things, so I think I'm OK and now have a new computer!

Thanks for all your help...

The hatter

Level 9

60,990 points

Jul 18, 2012 1:54 PM in response to Steven Shmerler

Yea!

I think you got a better faster system with support for 10.8 if you need to, cheaper better faster memory too, more graphic card options and high end cards if you wish, and 3.2 4-core (8 threads) is more efficient processor. Not sure but check the geekbench score of others and yours.

Not having to deal with FBDIMMs anymore is also nice, esp in hot weather. I hate to say but between the hot exhaust and even my 24" monitor putting heat into the air, anything to reduce heat and keep cool!

Cool new system there for sure.

Jul 18, 2012 3:51 PM in response to The hatter

I thought it was perhaps my old MP running hotter than it should. But you're right. The exhaust is way cooler than my previous MP. Everything you said, the AppleCare pretty much did too as to why and how this new computer was a better and faster one. I'm quite happy. Albeit it was a struggle, but it paid off 🙂

Kernel Panic Crash Report Reading Help?