I just had ANOTHER kernel panic with 10.9.1. This is ridiculous.
I haven't had a kernel panic in Mac OS X for more years than I can recall. Have you checked your file system and HW to make sure there isn't an issue that can be causing the panic?
This is a brand new MBPro. 10.9.1 is the only thing that will run on it and you can't even do a normal reinstall of the OS. There is no way to download the installer from the App Store and create a bootable USB drive that can be used to do an OS install on this thing.
And with all due respect to those who would want to send some links, or ask if I tried one method or another, or provide suggestions .... Trust Me. I have tried everything. I'm a very experienced Mac user and I know what I'm doing.
I just had ANOTHER kernel panic with 10.9.1. This is ridiculous.
That's typically why I avoid .1 versions of any OS. In Windows or OSX, if I see a kernel panic, it's typically hardware of drivers. Did you check the panic log to see if an external device was referenced, assuming you had one plugged in at the time? Sometimes it takes a little while to uncover unexpected bugs in low level code.
This is a brand new MBPro. 10.9.1 is the only thing that will run on it and you can't even do a normal reinstall of the OS. There is no way to download the installer from the App Store and create a bootable USB drive that can be used to do an OS install on this thing.
And with all due respect to those who would want to send some links, or ask if I tried one method or another, or provide suggestions .... Trust Me. I have tried everything. I'm a very experienced Mac user and I know what I'm doing.
That's odd since claiming you can't do a reinstall of the OS is proof that you haven't "tried everything." You can not only boot into the Recovery partition but you can also DL the OS from the MAS and then create a USB boot drive from it. Or if feel you can't do that you can always take it to an Apple Store or send it to Apple. If you haven't tried checking or wiping the OS even once then you haven't come close to trying everything.
That's odd since claiming you can't do a reinstall of the OS is proof that you haven't "tried everything." You can not only boot into the Recovery partition but you can also DL the OS from the MAS and then create a USB boot drive from it. Or if feel you can't do that you can always take it to an Apple Store or send it to Apple. If you haven't tried checking or wiping the OS even once then you haven't come close to trying everything.
(sigh.... there's always someone....LOL)
It will not allow me to download Mavericks from the MAS. Want proof?
Given that I have access to other Macs, I do have some work-arounds. I was able to download the Installer App and create a bootable USB drive on another Mac. However that would not boot up my new MBPro. I was able to boot my MBPro from a full clone of the internal drive (made using SuperDuper) and then run the Installer App. Then at some point the partition map was damaged and I could not even boot into the Recovery Partition.
I am leaving out many many details and many different attempts, but the end result was that I ended up with a bootable USB drive that would not boot the new Mac, and the new Mac could not even access its recovery partition. I could not even boot the Mac far enough so that it would download a fresh copy of the installer from the 'net. I had to take it to an Apple Store in person.
I believe that the core issue is that the downloadable copy of Mavericks from the MAS has not been updated to work with the newest Macs. This was confirmed by a tech at the Store as well as a 2nd-level tech support guy on the Apple support line. He also told me (off the record) that Apple is trying to shy away from people creating and using things such as "USB Boot Drives" as installers. In fact if you tell them that you used such a method to install your OS, they are instructed to NOT SUPPORT YOU. The ONLY method they will support is for you to grab a new copy of the OS from the 'net each and every time you need to do an install.
IMHO that's ridiculous. I know a family with 4 Macs in their house. Are they expected to download a separate copy directly to each of those Macs? The Apple tech said "yes", and that he could understand my frustration (hey, he just works there, so I'm not going to hassle him).
Anyway, I am hoping that when 10.9.2 gets released, that it will finally be such that I can download an Installer from the MAS that will work with my Mac. Then I'll do a fresh install of the OS. If I still get kernel panics, I'll assume its a hardware problem and take the Mac in and have it swapped for a new one.
Given that I have access to other Macs, I do have some work-arounds. I was able to download the Installer App and create a bootable USB drive on another Mac. However that would not boot up my new MBPro. I was able to boot my MBPro from a full clone of the internal drive (made using SuperDuper) and then run the Installer App. Then at some point the partition map was damaged and I could not even boot into the Recovery Partition.
I am leaving out many many details and many different attempts, but the end result was that I ended up with a bootable USB drive that would not boot the new Mac, and the new Mac could not even access its recovery partition. I could not even boot the Mac far enough so that it would download a fresh copy of the installer from the 'net. I had to take it to an Apple Store in person.
I believe that the core issue is that the downloadable copy of Mavericks from the MAS has not been updated to work with the newest Macs. This was confirmed by a tech at the Store as well as a 2nd-level tech support guy on the Apple support line. He also told me (off the record) that Apple is trying to shy away from people creating and using things such as "USB Boot Drives" as installers. In fact if you tell them that you used such a method to install your OS, they are instructed to NOT SUPPORT YOU. The ONLY method they will support is for you to grab a new copy of the OS from the 'net each and every time you need to do an install.
IMHO that's ridiculous. I know a family with 4 Macs in their house. Are they expected to download a separate copy directly to each of those Macs? The Apple tech said "yes", and that he could understand my frustration (hey, he just works there, so I'm not going to hassle him).
Anyway, I am hoping that when 10.9.2 gets released, that it will finally be such that I can download an Installer from the MAS that will work with my Mac. Then I'll do a fresh install of the OS. If I still get kernel panics, I'll assume its a hardware problem and take the Mac in and have it swapped for a new one.
OK, it definitely sound like you've gone through all the available steps. In my defense, I have heard statements like "There is no way to download the installer from the App Store and create a bootable USB drive that can be used to do an OS install on this thing" many times just to find out they didn't know about the Recovery partition or that you can option/right-click the .app installer to get retrieve the DMG to create a boot drive with Disk Utility.
On the bright side, I think that Apple didn't issue an emergency security update when they released the update to iOS is because 10.9.2 is imminent. I wouldn't be surprised if it dropped today.
Remember that joke about how "Military Intelligence" is a misnomer?
I have a new one.
"Software Quality Assurance".
LOL
With such massive issues like the Gmail or the SSL bug making it into release versions of an OS, I can't help but wonder about the maturity of the Software Development and QA practices at Apple.
E.g, with the SSL bug,
had they employed Pair Programming, the error would most probably have already been caught during the coding phase.
had they employed Code Coverage testing, the error would have certainly been caught during QA phase.
I am sorry to see that such problems impair what are basically innovative and valuable Software products.
I believe that the core issue is that the downloadable copy of Mavericks from the MAS has not been updated to work with the newest Macs. This was confirmed by a tech at the Store as well as a 2nd-level tech support guy on the Apple support line. He also told me (off the record) that Apple is trying to shy away from people creating and using things such as "USB Boot Drives" as installers. In fact if you tell them that you used such a method to install your OS, they are instructed to NOT SUPPORT YOU. The ONLY method they will support is for you to grab a new copy of the OS from the 'net each and every time you need to do an install.
IMHO that's ridiculous. I know a family with 4 Macs in their house. Are they expected to download a separate copy directly to each of those Macs? The Apple tech said "yes", and that he could understand my frustration (hey, he just works there, so I'm not going to hassle him).
I don't doubt your story, however if you are looking for a little ammo to have in your gun belt, Apple advertises a caching feature in OSX Server. Use at your own discretion though, as it is not wise to p*ss-off the person helping you.
I haven't had a kernel panic in Mac OS X for more years than I can recall. Have you checked your file system and HW to make sure there isn't an issue that can be causing the panic?
I have had plenty over the past several months. Most I narrowed down to a USB device, the Countour Shuttle Pro 2. Most of the rest were a single app; though I haven't tried recently, I could repeat the error and cause a panic.
Stopped using the Shuttle Pro, changed how I used the app and no more panics.
I don't know but it would be awesome if they could prevent panics altogether, and also eliminate the need for restarts. I recall the Acorn computers didn't need restarts when installing stuff. I dunno. I am just a simple user so I leave this stuff to others.
What about the MITM exploit? This affects virtually every aspect of the operating system, including Software Update. I have to say, I'm seriously considering downloading the combo updater over a friend's Windows machine and then transferring it to my Macs by USB key.
I have had plenty over the past several months. Most I narrowed down to a USB device, the Countour Shuttle Pro 2. Most of the rest were a single app; though I haven't tried recently, I could repeat the error and cause a panic.
Stopped using the Shuttle Pro, changed how I used the app and no more panics.
I don't know but it would be awesome if they could prevent panics altogether, and also eliminate the need for restarts. I recall the Acorn computers didn't need restarts when installing stuff. I dunno. I am just a simple user so I leave this stuff to others.
1) I'd like to think OS X was smart enough to be able to prevent some wonky external HW in 2014 from bringing down the system.
2) I kind of miss seeing the system failure screen. Bar none Apple has the best looking crash screen. I love how it scrolls in there.
What about the MITM exploit? This affects virtually every aspect of the operating system, including Software Update. I have to say, I'm seriously considering downloading the combo updater over a friend's Windows machine and then transferring it to my Macs by USB key.
You should also change all your important passwords once you've completed the update, or at the very least change your iCloud/iTunes password. This isn't limited to someone on a public WiFi snagging your wireless packets, but any system between you and and the destination that could be captured your packets. Unfortunately Apple doesn't have a way to see an un-editable list of IP addresses and devices have used to access your account.
"This post is a quick recap of work I've been discussing on Twitter in the last few hours. I've just finished putting together a version of mitmproxy that takes advantage of CVE-2014-1266, Apple's critical SSL/TLS bug. We knew in theory that the issue should give access to all SSL traffic using Apple's broken implementation - I can now report that this is also true in practice.
I've confirmed full transparent interception of HTTPS traffic on both IOS (prior to 7.0.6) and OSX Mavericks. Nearly all encrypted traffic, including usernames, passwords, and even Apple app updates can be captured. This includes:
App store and software update traffic iCloud data, including KeyChain enrollment and updates Data from the Calendar and Reminders Find My Mac updates Traffic for applications that use certificate pinning, like Twitter It's difficult to over-state the seriousness of this issue. With a tool like mitmproxy in the right position, an attacker can intercept, view and modify nearly all sensitive traffic. This extends to the software update mechanism itself, which uses HTTPS for deployment.
At the time of writing, Apple still doesn't have a fix deployed for OSX. It took less than a day to get the patched version of mitmproxy and its supporting libraries up and running. I won't be releasing my patches until well after Apple's pending update, but it's safe to assume that this is now being exploited in the wild. Of course, intelligence agencies have no doubt been on top of this for some time - perhaps some of the inflammatory Sochi security horror stories were plausible after all."
If you don't have a Mac I suggest changing at least your iCloud/iTunes password immediately.
If you do have a Mac I suggest changing at least your iCloud/iTunes password once the fix has been administered.
If you use Safari or Mail to access encrypted sites with a username and password I suggest also changing every password once all fixes have been administered.
I have had plenty over the past several months. Most I narrowed down to a USB device, the Countour Shuttle Pro 2. Most of the rest were a single app; though I haven't tried recently, I could repeat the error and cause a panic.
Stopped using the Shuttle Pro, changed how I used the app and no more panics.
I don't know but it would be awesome if they could prevent panics altogether, and also eliminate the need for restarts. I recall the Acorn computers didn't need restarts when installing stuff. I dunno. I am just a simple user so I leave this stuff to others.
I think I've had 5 or 6 in the past five years. The last was like two years ago.
Comments
I haven't had a kernel panic in Mac OS X for more years than I can recall. Have you checked your file system and HW to make sure there isn't an issue that can be causing the panic?
Yes.
This is a brand new MBPro. 10.9.1 is the only thing that will run on it and you can't even do a normal reinstall of the OS. There is no way to download the installer from the App Store and create a bootable USB drive that can be used to do an OS install on this thing.
And with all due respect to those who would want to send some links, or ask if I tried one method or another, or provide suggestions .... Trust Me. I have tried everything. I'm a very experienced Mac user and I know what I'm doing.
Come on Apple, get on with it already.
I just had ANOTHER kernel panic with 10.9.1. This is ridiculous.
That's typically why I avoid .1 versions of any OS. In Windows or OSX, if I see a kernel panic, it's typically hardware of drivers. Did you check the panic log to see if an external device was referenced, assuming you had one plugged in at the time? Sometimes it takes a little while to uncover unexpected bugs in low level code.
That's odd since claiming you can't do a reinstall of the OS is proof that you haven't "tried everything." You can not only boot into the Recovery partition but you can also DL the OS from the MAS and then create a USB boot drive from it. Or if feel you can't do that you can always take it to an Apple Store or send it to Apple. If you haven't tried checking or wiping the OS even once then you haven't come close to trying everything.
That's odd since claiming you can't do a reinstall of the OS is proof that you haven't "tried everything." You can not only boot into the Recovery partition but you can also DL the OS from the MAS and then create a USB boot drive from it. Or if feel you can't do that you can always take it to an Apple Store or send it to Apple. If you haven't tried checking or wiping the OS even once then you haven't come close to trying everything.
(sigh.... there's always someone....LOL)
It will not allow me to download Mavericks from the MAS. Want proof?
Given that I have access to other Macs, I do have some work-arounds. I was able to download the Installer App and create a bootable USB drive on another Mac. However that would not boot up my new MBPro. I was able to boot my MBPro from a full clone of the internal drive (made using SuperDuper) and then run the Installer App. Then at some point the partition map was damaged and I could not even boot into the Recovery Partition.
I am leaving out many many details and many different attempts, but the end result was that I ended up with a bootable USB drive that would not boot the new Mac, and the new Mac could not even access its recovery partition. I could not even boot the Mac far enough so that it would download a fresh copy of the installer from the 'net. I had to take it to an Apple Store in person.
I believe that the core issue is that the downloadable copy of Mavericks from the MAS has not been updated to work with the newest Macs. This was confirmed by a tech at the Store as well as a 2nd-level tech support guy on the Apple support line. He also told me (off the record) that Apple is trying to shy away from people creating and using things such as "USB Boot Drives" as installers. In fact if you tell them that you used such a method to install your OS, they are instructed to NOT SUPPORT YOU. The ONLY method they will support is for you to grab a new copy of the OS from the 'net each and every time you need to do an install.
IMHO that's ridiculous. I know a family with 4 Macs in their house. Are they expected to download a separate copy directly to each of those Macs? The Apple tech said "yes", and that he could understand my frustration (hey, he just works there, so I'm not going to hassle him).
Anyway, I am hoping that when 10.9.2 gets released, that it will finally be such that I can download an Installer from the MAS that will work with my Mac. Then I'll do a fresh install of the OS. If I still get kernel panics, I'll assume its a hardware problem and take the Mac in and have it swapped for a new one.
OK, it definitely sound like you've gone through all the available steps. In my defense, I have heard statements like "There is no way to download the installer from the App Store and create a bootable USB drive that can be used to do an OS install on this thing" many times just to find out they didn't know about the Recovery partition or that you can option/right-click the .app installer to get retrieve the DMG to create a boot drive with Disk Utility.
On the bright side, I think that Apple didn't issue an emergency security update when they released the update to iOS is because 10.9.2 is imminent. I wouldn't be surprised if it dropped today.
Remember that joke about how "Military Intelligence" is a misnomer?
I have a new one.
"Software Quality Assurance".
LOL
Oxymoron.
It would make sense for Apple to hold back on the 10.9.2 release until a fix for the SSL problem can be fixed.
It's more likely the other way around. Apple's holding back releasing the security update because .2 was almost ready.
As others have pointed out, it's a relatively simple fix.
Remember that joke about how "Military Intelligence" is a misnomer?
I have a new one.
"Software Quality Assurance".
LOL
With such massive issues like the Gmail or the SSL bug making it into release versions of an OS, I can't help but wonder about the maturity of the Software Development and QA practices at Apple.
E.g, with the SSL bug,
had they employed Pair Programming, the error would most probably have already been caught during the coding phase.
had they employed Code Coverage testing, the error would have certainly been caught during QA phase.
I am sorry to see that such problems impair what are basically innovative and valuable Software products.
I believe that the core issue is that the downloadable copy of Mavericks from the MAS has not been updated to work with the newest Macs. This was confirmed by a tech at the Store as well as a 2nd-level tech support guy on the Apple support line. He also told me (off the record) that Apple is trying to shy away from people creating and using things such as "USB Boot Drives" as installers. In fact if you tell them that you used such a method to install your OS, they are instructed to NOT SUPPORT YOU. The ONLY method they will support is for you to grab a new copy of the OS from the 'net each and every time you need to do an install.
IMHO that's ridiculous. I know a family with 4 Macs in their house. Are they expected to download a separate copy directly to each of those Macs? The Apple tech said "yes", and that he could understand my frustration (hey, he just works there, so I'm not going to hassle him).
I don't doubt your story, however if you are looking for a little ammo to have in your gun belt, Apple advertises a caching feature in OSX Server. Use at your own discretion though, as it is not wise to p*ss-off the person helping you.
I haven't had a kernel panic in Mac OS X for more years than I can recall. Have you checked your file system and HW to make sure there isn't an issue that can be causing the panic?
I have had plenty over the past several months. Most I narrowed down to a USB device, the Countour Shuttle Pro 2. Most of the rest were a single app; though I haven't tried recently, I could repeat the error and cause a panic.
Stopped using the Shuttle Pro, changed how I used the app and no more panics.
I don't know but it would be awesome if they could prevent panics altogether, and also eliminate the need for restarts. I recall the Acorn computers didn't need restarts when installing stuff. I dunno. I am just a simple user so I leave this stuff to others.
Some fan sites (and news sites) out there are causing something nothing short of a panic over the security flaw.
I doubt it will be long before somebody points to the Mac OS X page on Apple's site where they say boldly:
Security was the first thought.
Not an afterthought.
Somebody will find a way to start a class action over this, I'm sure. To the benefit of a single lawyer.
1) I'd like to think OS X was smart enough to be able to prevent some wonky external HW in 2014 from bringing down the system.
2) I kind of miss seeing the system failure screen. Bar none Apple has the best looking crash screen. I love how it scrolls in there.
You should also change all your important passwords once you've completed the update, or at the very least change your iCloud/iTunes password. This isn't limited to someone on a public WiFi snagging your wireless packets, but any system between you and and the destination that could be captured your packets. Unfortunately Apple doesn't have a way to see an un-editable list of IP addresses and devices have used to access your account.
"This post is a quick recap of work I've been discussing on Twitter in the last few hours. I've just finished putting together a version of mitmproxy that takes advantage of CVE-2014-1266, Apple's critical SSL/TLS bug. We knew in theory that the issue should give access to all SSL traffic using Apple's broken implementation - I can now report that this is also true in practice.
I've confirmed full transparent interception of HTTPS traffic on both IOS (prior to 7.0.6) and OSX Mavericks. Nearly all encrypted traffic, including usernames, passwords, and even Apple app updates can be captured. This includes:
App store and software update traffic
iCloud data, including KeyChain enrollment and updates
Data from the Calendar and Reminders
Find My Mac updates
Traffic for applications that use certificate pinning, like Twitter
It's difficult to over-state the seriousness of this issue. With a tool like mitmproxy in the right position, an attacker can intercept, view and modify nearly all sensitive traffic. This extends to the software update mechanism itself, which uses HTTPS for deployment.
At the time of writing, Apple still doesn't have a fix deployed for OSX. It took less than a day to get the patched version of mitmproxy and its supporting libraries up and running. I won't be releasing my patches until well after Apple's pending update, but it's safe to assume that this is now being exploited in the wild. Of course, intelligence agencies have no doubt been on top of this for some time - perhaps some of the inflammatory Sochi security horror stories were plausible after all."
If you do have a Mac I suggest changing at least your iCloud/iTunes password once the fix has been administered.
If you use Safari or Mail to access encrypted sites with a username and password I suggest also changing every password once all fixes have been administered.
I have had plenty over the past several months. Most I narrowed down to a USB device, the Countour Shuttle Pro 2. Most of the rest were a single app; though I haven't tried recently, I could repeat the error and cause a panic.
Stopped using the Shuttle Pro, changed how I used the app and no more panics.
I don't know but it would be awesome if they could prevent panics altogether, and also eliminate the need for restarts. I recall the Acorn computers didn't need restarts when installing stuff. I dunno. I am just a simple user so I leave this stuff to others.
I think I've had 5 or 6 in the past five years. The last was like two years ago.