Q: Sleep/wake crash OSX Mavericks, Macbook Air 2013

max_volume wrote:

 

Come on Apple!

There's almost certainly nobody from Apple reading this, so you need to find another way of communicating your feedback: http://www.apple.com/feedback/macbookair.html

Hi Shaun7777,

how did you removed the airparrots kexts? A kext is a kernel extension and i read the howto in https://developer.apple.com/library/mac/documentation/Darwin/Reference/Manpages/ man8/kextunload.8.html#//apple_ref/doc/man/8/kextunload but i dont know how to use it.

I used your hint "kextstat | grep -v apple" and found 2 kext that i would remove: se.coolbook.driver2 and com.ncp-e.vpn.driver.ncplbmac

Do you know foo.tun and foo.tap kext?

Thanks, Markus

bonneville77 wrote:

 

how did you removed the airparrots kexts?

As he said he went to the developers web site and followed the instructions there for removing all of airparrots, not just the kext files. That's always the best way to un-install any software, assuming the developer will provide you with an un-installer or at least instructions.  You could simply delete those two .kext files and reboot, but chances are there is additional software installed and perhaps still active and looking for those files.

Do you know foo.tun and foo.tap kext?

http://en.wikipedia.org/wiki/TUN/TAP Commonly used by VPN services.

You could simply delete those two .kext files and reboot, but chances are there is additional software installed and perhaps still active and looking for those files.

Do you know foo.tun and foo.tap kext?

http://en.wikipedia.org/wiki/TUN/TAP Commonly used by VPN services.

I think i've got it! No crashes and no sleep wake failures since fixing:

Look for non-apple kernel extensions:

kextstat | grep -v apple

To delete a kext:

cd /system/library/extensions

sudo mv kextname.kext ~/.

foo.tun and foo.tap are from an Install of "Tunnelblick", a third party VPN Client. I think this the reason, why it crashes..

To remove:

sudo kextunload -b foo.tun

sudo kextunload -b foo.tab

Greetings from Germany..

Markus

foo.tun and foo.tap are from an Install of "Tunnelblick", a third party VPN Client. I think this the reason, why it crashes.

You may still have crashes after you restart your computer or log out and then back in again.

Although "sudo kextunload" may have removed the kexts from the computer's memory, they will be reloaded the next time you launch a very old version of Tunnelblick (which may automatically launch when you log in). If they are from a program other than Tunnelblick (other VPN software also  installed foo.tun and foo.tap), they may be set up to load when you restart your computer.

Versions of Tunnelblick more than about four years old loaded the two kexts when the program launched, and unloaded them when  it quit, so such an old version of Tunnelblick would have to have been running at the time of the crash. Newer versions of Tunnelblick load and unload kexts only as needed, and name them "net.tunnelblick.tun" and "net.tunnelblick.tap". Newer versions also load different versions of the kexts depending on which version of OS X you are running.

If you  have an old version of Tunnelblick installed on your computer, you should either

• Update to the latest version from the Downloads page; just install a new version by double-clicking, there is no need to uninstall the old one first, or
• Completely uninstall it using these instructions.

Update Mavericks yesterday (security update). The first time I woke my MBP from the screensaver it locked up and I had to use the power button to shut it down get it back to life.

So after all these months still no fix for this problem.

Have you considered joining the OS X Beta Seed Program for Mavericks?

I seem to have the same problem and this is an iMac. so it does not seem to be restricted to Macbook Air or Macbook Pro.

I was hoping the recent security update will solve it but did not.

Has anybody found a workaround except preventing the display not to go to sleep?

Holger Lehniger wrote:

 

I was hoping the recent security update will solve it but did not.

Security updates would never solve a problem like this. As I just suggested to the last "Me Too'er", consider joining the OS X Beta Seed Program for Mavericks. That's where all the fixes would be.

I just called Apple Support and received a very competent guideline which seems to have solved the problem on my end:

• Close all programs
• Shutdown your computer
• Unplug your iMac from power
• Keeping it unplugged press the power button at least 5 seconds
• Plug your iMac to power
• Press the power button
• As soon as you release the power button press the keys alt+cmd+p+r until you hear the chime the second time

This includes an SMC reset (see here: http://support.apple.com/kb/HT3964?viewlocale=en_US) and an NVRAM reset (http://support.apple.com/kb/HT1379?viewlocale=en_US)

My display sleep issue seems to be solved by that.

This is a horrible problem. The problem has existed for almost half a year and it's still unresolved after three updates.

<Edited by Host>

I've got a 2010 iMac and started having this problem only after I installed Mavericks.  At first the computer would not wake from sleep once or twice a week, but over the last few months it has devolved into twice a day.

Anyway, I reset the PRAM and NVRAM this past Saturday, and I'm happy to report that so far it appears to have done the job: no wake up problems for 3 days now.  Here's the directions for resetting PRAM and NVRAM:

http://support.apple.com/kb/ht1379

I also did the SMC reset (which is a different process depending on whether you have a desktop or laptop).

http://support.apple.com/kb/HT3964

My MacBook Pro Mid-2010 just started experienceing this issue this weekend.  Never experienced this issue before this weekend.  I reset the PRAM and NVRAM, formatted the HardDrive & re-installed OSX but the problem still persists.  I am switching back to a Windows 7 machines for now because my Mac is just unseable like this.  Hopefully someone (HELP APPLE) fixes this soon.

-andy

andyappel wrote:

 

Hopefully someone (HELP APPLE) fixes this soon.

Hopefully you know that Apple is probably not reading this, so you need to take your computer to them or contact them in some other manner to get yours fixed.

I hear ya and agree but you would hope that Apple would at least be monitoring these channels because its in their best interest if their **** works.