To be safe, I would boot into the recovery partition and reload the entire operating system. Airportd is probably not the only thing damaged, just the first thing you tripped over.
> On Feb 11, 2017, at 11:48 AM, Carl Hoefs <[email protected]> > wrote: > > We suffered a nasty power glitch last night, and now one of the iMacs is > having troubles doing Wi-fi. Seems like the /usr/libexec/airportd file may > have gotten corrupted and now has an incorrect CRC or something. Here's > what's in the system log: > > 2/11/17 11:39:09.000 AM kernel[0]: 2434.634332: createP2PInterface: ERROR: > P2P device interface exists > 2/11/17 11:39:09.000 AM kernel[0]: 2434.634336: setVIRTUAL_IF_CREATE: > createP2PInterface call FAILED > 2/11/17 11:39:09.997 AM airportd[1299]: airportdProcessDLILEvent: en1 > attached (up) > 2/11/17 11:39:10.000 AM kernel[0]: en1: channel changed to 1 > 2/11/17 11:39:10.000 AM kernel[0]: CODE SIGNING: > cs_invalid_page(0x10ca6d000): p=1299[airportd] final status 0x3004a00, > denying page sending SIGKILL > 2/11/17 11:39:10.000 AM kernel[0]: CODE SIGNING: process 1299[airportd]: > rejecting invalid page at address 0x10ca6d000 from offset 0xaf000 in file > "/usr/libexec/airportd" (cs_mtime:1431489060.0 == mtime:1431489060.0) > (signed:1 validated:1 tainted:1 wpmapped:0 slid:0) > 2/11/17 11:39:11.028 AM com.apple.xpc.launchd[1]: (com.apple.airportd[1299]) > Binary is improperly signed. > 2/11/17 11:39:11.028 AM com.apple.xpc.launchd[1]: (com.apple.airportd) > Service only ran for 1 seconds. Pushing respawn out by 9 seconds. > > I have TM backups for the machine. Would restoring /usr/libexec/airportd be > my only option at this point? Or is that a red herring? > > -Carl > > _______________________________________________ > MacOSX-talk mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-talk
_______________________________________________ MacOSX-talk mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-talk
