On Sun, 13 Apr 2014 03:33:10 +0200, alexander.kleinso...@gmx.de said: > printk(KERN_EMERG MODNAME "error: const kernel memory is broken > (%08lx != 0), please reboot!", g_SumLast);
Make a list of all the things that can dynamically modify kernel text while it's running, starting with the alternatives code, and adding in the various tracing and debugging tools, and ask yourself if KERN_EMERG is the right choice here... Also, that printk is in the wrong place - it only fires if somebody reads the /proc file, and it *should* trigger as soon as practical after a problem has been detected. Bonus points for computing what percent of single, double, triple, and other error syndromes your xor detects (hint - what is the behavior of a dead row or column of bits?).
pgpP8CYrFcJH6.pgp
Description: PGP signature
