Just to follow up... I did a md5 hash check of the binary, and found it was different (61592f859c4ccf4a85f706dc361c0e2e) than on another working 10.10.5 system (0e2461bbc5fd5122f6ca0dcbe75ffeb4), so I copied that over and it appears to be running fine now. (awdd and libTelephonyUtilDynamic.dylib were also munged in the same way).
Is this type of data degradation natural (i.e., cosmic rays) or is this an indication of a potential disk failure? -Carl > On Feb 24, 2016, at 10:06 PM, Carl Hoefs <[email protected]> > wrote: > > All of a sudden, com.apple.blued is crashing over & over on 10.10.5 with > signal 42 (SIGRTMIN+8): > > - kernel[0]: CODE SIGNING: cs_invalid_page(0x1037af000): p=31488[blued] final > status 0x3004a00, denying page sending SIGKILL > - kernel[0]: CODE SIGNING: process 31488[blued]: rejecting invalid page at > address 0x1037af000 from offset 0x7d000 in file "/usr/sbin/blued" > (cs_mtime:1438756368.0 == mtime:1438756368.0) (signed:1 validated:1 tainted:1 > wpmapped:0 slid:0) > - com.apple.xpc.launchd[1]: (com.apple.blued[31488]) Binary is improperly > signed. > - com.apple.xpc.launchd[1]: (com.apple.blued) Service only ran for 0 seconds. > Pushing respawn out by 10 seconds. > > How could the binary suddenly be "improperly signed"? I can unload it, but > then coreaudiod goes 100% cpu bound. What could be going on here? > -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
