<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [i915] oops in intel_update_cursor_plane(): "BUG: unable to handle kernel NULL pointer dereference"" href="https://bugs.freedesktop.org/show_bug.cgi?id=100725#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [i915] oops in intel_update_cursor_plane(): "BUG: unable to handle kernel NULL pointer dereference"" href="https://bugs.freedesktop.org/show_bug.cgi?id=100725">bug 100725</a> from <a class="email" href="mailto:krisman@collabora.co.uk" title="krisman@collabora.co.uk">krisman@collabora.co.uk</a> <pre>(In reply to David H. Gutteridge from <a href="show_bug.cgi?id=100725#c0">comment #0</a>) > Created <a href="attachment.cgi?id=130919" name="attach_130919" title="Log of dmesg with drm.debug enabled from boot to oops">attachment 130919</a> <a href="attachment.cgi?id=130919&action=edit" title="Log of dmesg with drm.debug enabled from boot to oops">[details]</a> > Log of dmesg with drm.debug enabled from boot to oops > > I've been encountering a recurring kernel oops since I upgraded a (rather > old) laptop to the 4.10 kernel series. These happen pretty consistently > after the machine has been up for a few hours, and after a series of > warnings are logged. > I reproduced this with Fedora's 4.10.11-200.fc25.i686 kernel last evening. > This is a regression against the 4.9 kernel. > I've attached a dmesg log from boot to the oops, with drm.debug output > enabled. Sorry for the delay. Is this still reproducible with a recent kernel? The log has some high order allocation failure in GEM immediately preceding the WARN_ON and oops, so this is likely a mishandling of the allocation error path. Since you observed this on a 4.10 distro kernel, can you please confirm it still occur with the tip of drm-intel-nightly mainline branch and provide the logs? Thanks.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>