And no business should be providing patches without properly testing them before release. This is a pattern with Apple, and it's pretty lame. They need to spend some of their $ on QA.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Thunderbolt Software Update 1.2 Causing Boot Failures for Some Users
- Thread starter MacRumors
- Start date
- Sort by reaction score
And no business should be providing patches without properly testing them before release. This is a pattern with Apple, and it's pretty lame. They need to spend some of their $ on QA.
I chose to do the Reinstall Mac OS X option from the recovery tool (Command+R at boot) and everything is fine. Reinstalled OS X without messing with my data at all. Took a little bit and have to reinstall some updates/java/etc but its all working. Im gonna hold off on any thunderbolt updates for the time being (I don't use it anyway, just the display port chunk.)
Happened to my early 2011 MBP when I tried updating early this morning. I didn't read about reinstalling Lion though, instead I went straight to a time machine backup. That's when I found out that part of my backup is corrupt (it's a backup I made the night before, and I have never received an error message from time machine).
So yeah, fun times. The failed restore wiped my drive so I couldn't try a Lion reinstall. I just finished installing Lion and am using migration assistant to see if it has better luck than restore.
Lessons learned:
-Can no longer blindly trust Apple updates. Like Windows, I will wait a few days before applying new updates.
-Cannot trust time machine backups. Will need to make a secondary backup for critical data.
-Update-
Migration assistant worked, back to old self. *sigh* That was scary for a while.
So yeah, fun times. The failed restore wiped my drive so I couldn't try a Lion reinstall. I just finished installing Lion and am using migration assistant to see if it has better luck than restore.
Lessons learned:
-Can no longer blindly trust Apple updates. Like Windows, I will wait a few days before applying new updates.
-Cannot trust time machine backups. Will need to make a secondary backup for critical data.
-Update-
Migration assistant worked, back to old self. *sigh* That was scary for a while.
Last edited:
Count me in this camp with an early 2011 MBP. KP on boot.
Same, got one on my Mac Mini
THANK YOU THANK YOU THANK YOU! You saved my ass and many calls to clueless support, this worked! And thanks to the other poster who put up the link too, here's it is: http://support.apple.com/kb/DL1524?viewlocale=en_US&locale=en_US
Follow this above and it worked for me, macbook pro late 2011 came back to life, still shows i have the software updated needed on what killed it last night, but i'll try, at least i know what to do if it happens again.
I downloaded the thunderbolt update this morning, installed it, but I didn't reboot.
After I read that some people may have problems after the installation, I downloaded the 10.7.4 combo update, installed it, and then I rebooted my computer. I had no problem.
I can't say if I was going to have a problem rebooting after the thunderbolt update, but if my solution works for anybody else, I'm glad.
After I read that some people may have problems after the installation, I downloaded the 10.7.4 combo update, installed it, and then I rebooted my computer. I had no problem.
I can't say if I was going to have a problem rebooting after the thunderbolt update, but if my solution works for anybody else, I'm glad.
The easier solution to the problem is to simply restore from TimeMachine
I ran into it myself and wasted a good day trying to get the acpi driver up alive otherwise but even with the kext present there is something deeper down the road that breaks it.
I ran into it myself and wasted a good day trying to get the acpi driver up alive otherwise but even with the kext present there is something deeper down the road that breaks it.
Nonsense, Software Update checks the downloaded file/verifies the package.
If that is the problem then if you have a recent backup and can start up from that backup then it can be fixed even faster than applying the combo update.
Start up from back up, log into root(must be enabled) and copy over the TB kext from the backup to the corrupted install, restart and it should be fixed.
That's a reason why I always have a recent backup(Non Timemachine) and be able to fix things much faster.
If I had this installer I would open it with Pacifist and look what was actually installed and then copy all the old files on backup back to the main install, problem fixed.
5 minute fix! Instead of complete Reinstall or Combo update.
Especially when on a slow internet connection.
Last edited:
This worked for me, too, on my mid-2011 iMac, with the exception that since I'm actually booting from my TB drive but still have the OS installed on the internal HD, I didn't have to mess with a second Mac. Instead, I option-booted from the internal drive and from there downloaded and installed the 10.7.4 combo updater package onto the external TB drive.
So this could be interesting. I never checked for any updates since the Keynote, nor after hearing about the Thunderbolt problem, I never had time with work. I just checked it this morning, no update for Thunderbolt. Just iTunes, Java and Air Port Utility.
Did the late 2011 MBP's get the update? Or did Apple pull the update due to the problems?
Did the late 2011 MBP's get the update? Or did Apple pull the update due to the problems?
I have a mid-2011 MBA 13. My TB gigabit adapter will be delivered today. Been reading all this info this morning, and I guess as of right now I need to wait to even try it (since Apple pulled the questionable update).
Also, a very unscientific metric, but scanning threads and comments on this issue makes it look like it's folks with MBP's mostly having the issue ?
In any case, I'm going to keep watching this thread. Hopefully they will QA the driver a bit more on a wider range of machines (how on earth do they NOT do this in the first place ?) and get a newer version out soon.
Also, a very unscientific metric, but scanning threads and comments on this issue makes it look like it's folks with MBP's mostly having the issue ?
In any case, I'm going to keep watching this thread. Hopefully they will QA the driver a bit more on a wider range of machines (how on earth do they NOT do this in the first place ?) and get a newer version out soon.
I've fixed the problem without needing a second Mac running Lion (target disk mode) or reinstalling altogether:
http://www.alexhutnik.com/2012/06/13/how-to-fix-kernel-panic-from-thunderbolt-update-1-2-without-reinstalling-os-x-lion-or-booting-from-another-mac/
Short version:
1. In recovery mode, grab 10.7.4 combo update. Save to an external USB drive.
2. Mount it from the Terminal.
3. Install the .pkg file contained therein.
4. Reboot.
http://www.alexhutnik.com/2012/06/13/how-to-fix-kernel-panic-from-thunderbolt-update-1-2-without-reinstalling-os-x-lion-or-booting-from-another-mac/
Short version:
1. In recovery mode, grab 10.7.4 combo update. Save to an external USB drive.
2. Mount it from the Terminal.
3. Install the .pkg file contained therein.
4. Reboot.
I noticed that when I ran SWU on my iMac and MBA - not that I was going to install them until I heard Apple had issued a new version.
Can we now officially retire the "it just works" tagline?
Again, it DID work for me...but perhaps we should start using the same taglines YOU love to employ for Windows 7, Aiden:
"BSODs don't exist in Windows 7; they only happen if you [fill the blank with lame excuses]"
I have the last pre-Thunderbolt MBP, so I won't be bitten by this, but my best guess at this point is something like the Tiger(?) upgrade issue, where there is some reasonably widespread, but not terribly common piece of hardware or software which includes a driver or something which is the root cause of the issue. Unfortunately, there's no way Apple can test their upgrades with every third-party driver out there, so these will happen some times. Based on the info Apple receives from bug reports and peoples' trips to the Genius Bar, they'll isolate the cause, and update the patch with a fix before releasing it again.
But, it's just a guess.
But, it's just a guess.
So does iTunes, and I've gotten bad iTunes tracks before. [Granted they could have been bad uploads that were fixed by the time CS gave me a credit to re-download]