Yes, I think you may be right! I can't even launch Safari. It complains about
a code signing error.
Exception Type: EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes: 0x0000000000000032, 0x00007fff7ab2a008
kernel messages:
-3 sec CODE SIGNING: cs_invalid_page(0x7fff7ab2a000):
p=1487[Safari] final status 0x3004a00, denying page sending SIGKILL
-3 sec CODE SIGNING: process 1487[Safari]: rejecting invalid
page at address 0x7fff7ab2a000 from offset 0x10154000 in file
"/private/var/db/*/dyld_shared_cache_x86_64" (cs_mtime:1486524827.0 ==
mtime:1486524827.0) (signed:1 validated:1 tainted:1 wpmapped:0 slid:1)
VM Regions Near 0x7fff7ab2a008:
__DATA 00007fff7ab00000-00007fff7ab08000 [ 32K] rw-/rwx
SM=COW
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS
--> __DATA 00007fff7ab08000-00007fff7abd6000 [ 824K] rw-/rwx
SM=COW
/System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer
__DATA 00007fff7abd6000-00007fff7ac00000 [ 168K] rw-/rwx
SM=COW
/System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/ImageKit.framework/Versions/A/ImageKit
Application Specific Information:
dyld: launch, loading dependent libraries
/System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuartzComposer.framework/Versions/A/QuartzComposer
-Carl
> On Feb 11, 2017, at 12:29 PM, Macs R We <[email protected]> wrote:
>
> 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]
> <mailto:[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] <mailto:[email protected]>
>> http://www.omnigroup.com/mailman/listinfo/macosx-talk
>> <http://www.omnigroup.com/mailman/listinfo/macosx-talk>
_______________________________________________
MacOSX-talk mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/macosx-talk
