Kernel Panic After Thunderbolt Update

If you have a boot clone (and I highly recommend you do!), - I use Carbon Copy Cloner frequently - it's much faster to restore from that. Plus, you don't need to overwrite your user folder with older information, since that's still intact.

CCC can also clone the recovery partition.

For those who it may help, I've covered this issue at MacFixIt: http://reviews.cnet.com/8301-13727_7-57451440-263/thunderbolt-update-plaguing-ma cbook-pros-with-kernel-panics/

It's essentially as has been made obvious here and elsewhere, a problem with the Thunderbolt update that requires OS X to be reinstalled, restored from a backup, or have the combo updater reapplied. I cover how to do these things in the article.

Same Serious Problem here 😠..my system is :

Modelo: MacBook Pro

Identificador de modelo: MacBookPro8,2

Nome do processador: Intel Core i7

Velocidade do processador: 2,2 GHz

Número de processadores: 1

Número total de núcleos: 4

Cache L2 (por núcleo): 256 KB

Cache L3: 6 MB

Memória: 8 GB

Made the same mistake 2X..had to reinstall..the osx 3X 😟..now updated everynthing,except..the Thunderbolt update of 203kb...😠 and it is fine 🙂

Great news!

....and now just for kicks and giggles, give the Thunderbolt Update a try. (no, dont do it!) 😀

For what it's worth, I applied this update (not knowing about these problems) to a mid-2011 11-inch MacBook Air with no problems at all.

I just got off the phone with applecare and they said are preety sure it was the iTunes update or a combination of the iTunes & Thunderbolt update. They are well aware of the issue, to reinstall os and not update anything. I was also told a new update should roll out within the next few days.

DaZe3 wrote:

I just got off the phone with applecare and they said are preety sure it was the iTunes update or a combination of the iTunes & Thunderbolt update. They are well aware of the issue, to reinstall os and not update anything. I was also told a new update should roll out within the next few days.

The kernel panic here is happening from the kernel's inability to load a referenced driver, which then explicitely mentions IOKit (the input/output system), which is unrelated to iTunes. Perhaps the iTunes update corrupted the Thunderbolt update after it was installed, but iTunes is not loaded at boot like this, and only starts up when you launch it within a user account.

Ok, the combined update 10.7.4 repair the problem an iphoto works, I download and install it from command line on the terminal that provides the Cmd+R method without re-installing complete Lion, if you has some advice with terminal commands, and not fear to it, this is the method that I used to:

first choice the option to launch safari from Cmd+R rescue. connect to an internet, an go to support apple for download the combined update, since you dont have free space on the rescue partition, you have to Ctrl-Click on the link to download and choice download linked file as, and navigate to /Volumes/Macintosh HD/Downloads for example, "Macintosh HD" is the Main HardDisk Partition (that you use normally) of the Mostly Macs.

After download is complete exit Safari, and go to Menu Utilities --> Terminal.

Because it's a rescue system you can't mount and execute the update directly Only need two commands for it on the command line, execute the first one, and once completes, execute the second. Note that the paths can be different for some users so don't make this if you don't understand it.

The first command mount the update as a drive on the /Volumes path:

hdiutil mount "/Volumes/Macintosh HD/Downloads/MacOSXUpdCombo10.7.4.dmg"

(or navigate to "your download location" with "cd" command and execute hdiutil mount name-of-the-update)

Once mounted it, install the update with the next command:

installer -package "/Volumes/Mac OS X 10.7.4 Update Combo/MacOSXUpdCombo10.7.4.pkg" -target "/Volumes/Macintosh HD"

(You can use Tabulator for complete names, and not mistakes on names after initial double quotes and initial characters written, if it not complete names, correct it!).

Afer a while two or three skipped filenames of components appear, forget this, it works, wait until the command complete, it happens when reappear the command line prompt again, because are not screen activity until it,

Next when the command line prompt reappear execute:

reboot

Afer a while, your mac works again, next install updates, but DO NOT INSTALL THE THUNDERBOLT UPDATE AGAIN.

I hope explained myself well.

Thanks for the instructions! Working on it now I hope that is the answer!😕

Mtaksrud wrote:

Does anyone know if Apple has been made aware of this problem?

Yes they do: Although I fixed the kernel panic crash myself by re-installing Lion, I nonetheless used AppleCare just to be sure it was reported.

The techie I spoke with told me Apple hasn't made any announcement about this yet, but that she personally had handled several calls about the same issue.

Perhaps the slow response is due to so many Apple engineers being otherwise occupied at WWDC! (Near the start of his keynote address, Tim Cook said over a thousand were attending to help developers there.)

What is the the best way of going about fixing this problem? I can access recovery mode, haven't check if safe mode works yet. So is the best and easiest the combo update or reinstalling lion from recovery mode? I'm very new to fixing my Mac, 5 years and no problems on 3 models. Currently have a 2011 MacBook pro.

Since I am a fairly new Mac user, I have 2 quick questions if you could help:

1. If Apple knows these updates cause such catastrophic consequences, why don't they immediately take the updates off-line?

2. How/Where can I check that Apple has actually fixed the problem? Is there an official Apple bug fix/bug update page?

Thanks.

If you have another Mac available then the least intrusive option would be the approach with the Combo updater, which I outlined in that article above. If you do not have this then resinstalling using the Recovery HD partition will also suffice, but will require you immediately update after installing (just be sure you do not apply the Thunderbolt Update when it appears in Software Update).

Same problem here with my Late 2011 MacBook Pro. Luckily I had a TimeMachine backup from yesterday and after restoring everything was back to normal.