Known bugs/issues
Q: Why do I get lots of "Worker submitted share with hash > target:" in my P2Pool logs? It seems to put a large CPU load on P2Pool.
A: If you use cgminer, scrypt and stratum, this is because cgminer and p2pool disagree on how to represent difficulty targets on stratum. p2pool seems to use a sane definition of target difficulty, unfortunately most other pools didn't establishing a de-facto standard that cgminer follows. Current solution: use the "--fix-protocol" parameter of cgminer. It will force it to use getwork (instead of stratum) where both agree on how to communicate difficulty targets.
one of my miners is an ASICMiner Eruptor Blade, which i believe uses getwork, but i am still seeing the hash > target msgs on the cli fly by...
any idea as to why it would still be doing this considering its using getwork? and is there anything that can be done to fix?
Does the Eruptor Blade support variable difficulty? If not then these messages are normal. You might want to ask ASICMINER about how their miner software reacts with difficulties different than 1.