Skip navigation

airportd crashes with segmentation fault

162 Views 2 Replies Latest reply: Jan 18, 2013 7:20 PM by mrfred RSS
mrfred Calculating status...
Currently Being Moderated
Jan 5, 2013 7:35 AM

I've got a MBP 8,2 running 10.6.8 with all the OS X updates.  It runs fine with the exception that Airport doesn't always work as expected.  In particular, it doesn't seem to readily auto-join known networks.  Another issue is that the Airport service is often not running after a reboot.  Looking through the Console logs over the last few weeks, it appears that the airportd is crashing with a segmentation fault.  Here are the typical two lines in a Console log:


1/4/13 6:18:08[1]([114]) Job appears to have crashed: Segmentation fault
1/4/13 6:18:08[84]2013-01-04 18:18:08.563 ReportCrash[84:1407] Saved crash report for airportd[114] version ??? (???) to /Library/Logs/DiagnosticReports/airportd_2013-01-04-181808_localhost.crash


I did a bunch of searching on the internet for answers, and found that there was essentially no reference to the exact issue I'm having.  I did however quickly come across several recommendations of deleting all the airport-related prefs in the SystemConfiguration folder (and rebooting and rebuilding the network interfaces) and resetting the PRAM, so I did those, but it didn't make a difference.


Wondering if anyone has any thoughts on resolving this issue.  I'm happy to post any logs or other info requests to help get to the bottom of this.


More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.