panic(cpu 2 caller 0xffffff80002a742e): "TLB invalidation IPI timeout: " "CPU(s) failed to respond to interrupts, unresponsive CPU bitmap: 0x1, NMIPI acks: orig: 0x0, now: 0x0"@/SourceCache/xnu/xnu-1699.22.73/osfmk/x86_64/pmap.c:2224
An interrupt was delivered to a core and it failed to respond (probably because it was coping with another interrupt) and the system gave up on waiting. This could mean your hardware is going bad, or it could mean a driver is shoddily written. If you can reproduce it consistently doing whatever you did, then it's the latter. If it keeps happening randomly, it's the former.
You see a blank, gray screen: http://support.apple.com/kb/TS1411#symp3
It seems fairly consistent for me. It is really easy to recreate the crash if I try to build a slide in Keynote for example. trailers.apple.com in Safari will cause a panic, as will ms powerpoint, Preview, Qt etc Hard to imagine everybody's hw started going bad as of the Lion GA.
I am now running with only the Intel graphics chipset enabled, but am still experiencing crashes. I am thinking of falling back to 10.6.x but am a little worried I am going to have issues with xcode...
Yeah - happening to me as well - maybe with a slight difference. I'm currently adding some new CDs to my library -the machine a quad core with 12gbs memory bought last year- is still running!
I can eject each finished CD and then put in a new one - bizarre!
As I know the only way I'll get the screen back is a hard reset.
I am also have the same problem. I have had to restart my iMac more then seven times. One thing I have noticed is five of my gray screens occurred when I played video in flash. Three gray screens occurred when played videos in silver light and one gray screen when I was just web browsing. The crash I had wile browsing, my flash was disable.
I dont think this helps but thought I should at least try.
The most annoying thing about this all is that I've been completely unable to find any way to directly notify Apple of this issue online. The closest I can get is to request a phone call back from support, not at all what's needed for this. If we were all able to simply email a support request referencing this forum thread, they'd realise very quickly that this is a major issue. As it is, I'm going to have to track down an official Apple store sometime tomorrow (there's none convient, I know that), and point them to this thread and see what they say. Pointless trying to reproduce an intermittent crash while in-store. And then what are the chances of the issue ever bubbling up to anyone who is in a position to actually log a real fault?
Luckily I installed Lion onto a second partition on my machine, and kept my Snow Leopard install safe and sound--back to that now, and of course all is working 100% there. I'll keep an eye on this thread, and hopefully a solution will arise at some point.
ugh - another black screen failure (note: it's not a blank screen we're all seeing, it's as if the power just goes off of the monitor completely).
I'm glad to hear Apple's working on it, but I've downloaded gfxCardStatus and am forcing my MBP to use the integrated Intel graphics only. I'm theorizing that since it seems to be an nVidia driver issue, maybe the Intel graphics will be stable until Apple fixes this mess.
I have the same MBP as it seems everyone else here does 15" Core i7 2010. and it was crashing all day yesterday, every ten minutes or so. enough that I was contemplating buying a new laptop so I could do my work.
I installed gfxCardStatus last night and set it to Integrated Intel Only and it hasn't crashed since. I've been using it all day today pretty intensely. It really ***** though because I usually use an external monitor and the integrated doesn't work with monitors.
It's hugely dissappointing that apple didn't test this thorougly. It seems pretty clear that there is a defect in the nVidia drivers for this particular laptop.
I think the problem maybe googlechrome.
We have a number of macs and the one that is a problem was running google chrome.
We removed the googlechrome folder and the components from library/launchagents and library/launchdaemons and for the last few hours everything seems good.
Also when looking at activity monitor we found that we had some blackberry components that were responsible for a chunk of process activity. We haven't had a blackerry for years.
Have you got googlechrome installed? If so, is it your default browser?
We have two MBP i7s, one has googlechrome installed, one doesn't. The one with the black screen problem had googlechrome installed the other didn't. We haven't had a crash since uninstalling chrome.
I noticed that there were two system processes in ( Activity Monitor ) of the same name (cvm) running one Intel (64bit) one Intel , both were associated with googlechrome - is it normal to have two processes by the same name running at the same time?
I'm unable to reproduce the similar behavior on my brother's MacBook Pro 2010 15" model. Before upgrading to Lion, I ran software update and it is up to date. However I applied latest EFI firmware update again (didn't check whether it's already contains or not) - However you can manually download the firmware from here: http://support.apple.com/kb/TS3423 - I'm not sure whether this update fixes that issue. But it's better to check existing EFI firmware by referring this article: http://support.apple.com/kb/HT3706 - After that I upgraded his system to Lion and it's working fine.
If you unable to boot MacBook Pro, please follow these steps:
- Shutdown your Mac entirely by holding the power button for 5 seconds.
- Hook up your Mac to another one with a FireWire cable. (You have one, right?)
- Hold the T key on your mac's internal keyboard and press the power button. When your MBP's disk will shows up as an external firewire disk on your HelperMac, release the T button.
- Open finder and go to the /private/var/vm folder on your MacBook's hard drive. You may need to use Command-Shift-G in Finder, because this folder is hidden by default. Once in /private/var/vm remove thesleepfile you find there.
- Next, go to /System/Library on you MBP's disk and removeExtensions.mkext.
- Now, eject your MBP drive and shutdown your MBP by hitting its power button.
After these steps, you should be able to boot your MBP as normal again.
Thanks to Ariejan for this tip!