Aw: Re: Re: new module to check constant memory for corruption

2014-04-13 Thread Alexander . Kleinsorge
1. KERN_EMERG is now KERN_INFO or ALERT (depending on ftrace_enabled). 2. there is no trigger for real ram errors possible! (only for out of bound writes) Therefore it is checked periodically and can also be triggered by /proc/ramcheck Alex  On Sun, 13 Apr 2014 03:33:10 +0200, Alexander.Kleinsor

Aw: Re: Re: new module to check constant memory for corruption

2014-04-13 Thread Alexander . Kleinsorge
Hi Andi,   1. I build in a check if ftrace is enabled. (like: cat /debug/tracing/tracing_enabled != 1) 2. Main goal is to detect: real ram errors (non crc systems = normal pc). This happens more often than you think: DRAM Errors in the Wild: A Large-Scale Field Study, Mai 2009 (http://www.cs.to