<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Sat, May 21, 2016 at 10:33 AM, René J.V. <span dir="ltr"><<a href="mailto:rjvbertin@gmail.com" target="_blank">rjvbertin@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="aBn" tabindex="0"><span class="aQJ">May 21 16:20:08</span></span> Portia kernel[0]: CODE SIGNING: cs_invalid_page(0x105ead000): p=98132[kioslave] final status 0x0, allowing (remove VALID) page</blockquote></div><br>So what I'm seeing is that this indicates that something is corrupted and making the kernel think it needs to look for code signing info, and then finding that the memory page recorded as having the code signing data is invalid. This can be as simple as /private/etc/authorization being corrupt (restore from backup), up to disk firmware problems in a few cases. (Re)signing may work around it temporarily, or move the problem somewhere else.<br><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>