"AM kernel CODE SIGNING: cs_invalid_page: p=2684[ATSServer] clearing CS_VALID
"AM kernel CODE SIGNING: cs_invalid_page: p=4816[lssave] clearing CS_VALID "

Those "code signing" errors fills my logs, anyone got an idea of what it is? Been asking
and googling all night long without any results.

Everything works OK by the way, I'm just a curious perfectionist.

I get the same here in my logs. I've come to the conclusion that it's normal on a leopard hackintosh.

Though i'm happy to be proved wrong... :)

I have also wondered this. If there is a way to clean these errors up, that would be nice. Im starting to think it is normal though.

anyone?????

Which release is this? Can you be a little more specific?

I'm running the first Zephyroth 10.5.2 but had that problem since 10.5.1. So I'm kind of used to that, but if there's a way to avoid that message I'll go for it.

eMatoS
"I'm running the first Zephyroth 10.5.2 but had that problem since 10.5.1. So I kind of used to that, but if there's a way to avoid that message I'll go for it."

Same w/ me. There does not appear to be anything wrong w/the workings of the systm. However, if clearing those errors improves performance, i'm for that.

I want to revive this thread and say that I'm plagued by these messages as well. I tried doing a LaunchServices rebuild as suggested at <a href="http://discussions.apple.com/thread.jspa?threadID=1201327&tstart=60#6080118">th is apple discussion thread</a>, as I believe it is related to a "-10810" error, jerking mouse problems, and other performance issues that I and others are having. However, this didn't help the problems. Zeph, if you're listening, what's your take on this one? There are many of us suffering from these issues and others like it. You can see all of our stories, trials, errors, and more here at <a href="http://osx.kbot.de/comments.php?DiscussionID=753">this thread</a>.

you can try this
This is a general OS issue, not just an OSx86 (hackintosh) issue. here is your fix:

CODE

sudo nano /System/Library/LaunchDaemons/com.apple.syslogd.plist


after line #23 add two additional strings (these make sure that the syslogd logger only write emergency errors to the system log.

CODE

#23 <string>/usr/sbin/syslogd</string>
#24 <string>-c</string>
#25 <string>0</string>


Optionally you can also cap the log file to a certain file size using:

CODE

#23 <string>/usr/sbin/syslogd</string>
#24 <string>-c</string>
#25 <string>0</string>
#26 <string>-db_max 2500000</string>

this is nice, but will turning off reporting actually do anything performance-wise? it seems the general concern is not necessarily that the messages are showing up, but what is actually causing them to show up in the first place. at one point, i thought little snitch was causing many of these code signing messages to occur, but after many hours of running without it, it seems that they just happen whenever i open/close a program or when OSX performs any sort of automatic maintenance/action. so at this point, i don't think it's anything to worry about, and i'm pretty sure the problems i am having (mouse movement, slowdowns, -10810s) are not related. but who knows? i have yet to find the solution to those things :\