Organizing kernel messages

This doesn't nessicarily address the automated tools. Although I do tend to agree with your saying. I don't know if the CRC32 will really be any better, but I'd love to have an automated response system for kernel messages based on som expted ID as opposed to some random text. The nice thing about this system, is that you can dig into the ID's and look for situations you didn't know could happen because you didn't look at a particular peice of source to see what kind of messages it could produce. Although i guess one could grep all of the printks() in the source right now, and get a full list, but that smells funny to me.