<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#c7">Comment # 7</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:adi@drcomp.erfurt.thur.de" title="Adrian Knoth <adi@drcomp.erfurt.thur.de>"> Adrian Knoth</a> <pre>(In reply to <a href="show_bug.cgi?id=61953#c6">comment #6</a>) > I've noticed that especially hover effects (images that change on > onMouseOver) in chromium are among the first elements to show screen > corruption. I guess we can remove the chromium hover corruption, it's a chromium bug which is present on other video drivers (radeon, NVIDIA blob), too: <a href="https://code.google.com/p/chromium/issues/detail?id=227447">https://code.google.com/p/chromium/issues/detail?id=227447</a> However, there is still some correlation with the video driver: if I disable the flashplugin in chromium or stop using chromium altogether, the kernel corruption occurs *much* later. So the original hypothesis still stands that some apps (ardour3, maybe also libreoffice) can write to arbitrary physical memory on my nouveau-based system. A short test with the NVIDIA blob did not exhibit this issue, but I'd need to run for several days to be sure. Maybe a power management issue? (memory timing?)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>