<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - arbitrary memory access corrupts kernel memory, eventually crashing the kernel" href="https://bugs.freedesktop.org/show_bug.cgi?id=61953#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - arbitrary memory access corrupts kernel memory, eventually crashing the kernel" href="https://bugs.freedesktop.org/show_bug.cgi?id=61953">bug 61953</a> from <a class="email" href="mailto:imirkin@alum.mit.edu" title="Ilia Mirkin <imirkin@alum.mit.edu>"> Ilia Mirkin</a> <pre>Try configuring your kernel with SLUB, and boot with slub_debug=FZPU. See if you get any allocation/usage-related backtraces in dmesg. (This will often prevent crashes from happening, so check dmesg every so often.) Even if you don't, it may be instructive to see dmesg dumps after a crash occurs even if it appears to be due to "random memory corruption". Also, if it got worse in 3.2.42, what was the last "not as bad" version? It may be the case that there are two separate issues going on here.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>