<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [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#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [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#c4">comment #4</a>) > I tried testing with the drm-intel-nightly branch cloned the evening of July > 7th, but this has proven unusable for me for an unrelated reason: the mouse > cursor ends up being stuck permanently rendered in its initial position. > That is, the underlying mouse movement is registered (regardless of trackpad > or mouse, X.org or Wayland) on the screen, with GUI components reacting as > the mouse position changes, but the cursor itself never moves. (The config > I'm using is basically what's used by Fedora, since I need various options > enabled for the laptop in question to be usable. The default config in > drm-intel-nightly wasn't adequate for that.) > > I've also tried testing with a downstream Fedora build of the 4.12 kernel, > which doesn't exhibit the frozen mouse cursor problem. I haven't been able > to duplicate this original issue yet with that kernel, though I haven't had > time to put in as much use as I'd like. (It typically happened under memory > pressure after the machine was up at least a few hours.) (I compared output > with drm.debug enabled between the drm-intel-nightly and Fedora kernels, and > I don't see anything to indicate why the mouse pointer problem is > happening.) I can continue testing with the Fedora kernel if that's still > relevant here. (I also have a build of the vanilla 4.12 kernel I can try if > need be. I'm not remotely familiar with the Intel kernel branches, but I > also found the test kernel I built from drm-intel-nightly panics on boot > when I use it in a VM, where the vanilla kernel does not. In that case, it > relates to the qxl driver, which might not be of interest on an Intel > branch.) ouch.. That is a bummer. :( Sorry about that. Regarding the mouse issue, it reminded me of a new Ville patch. Can you give it a try and see how it goes? <a href="https://lists.freedesktop.org/archives/intel-gfx/2017-July/133158.html">https://lists.freedesktop.org/archives/intel-gfx/2017-July/133158.html</a> Also, I'd ask you to open a new bug to track that issue. Regarding the QXL crash, I'd like to take a look at that one too. Can you please report it to <a href="mailto:dri-devel@freedesktop.org">dri-devel@freedesktop.org</a> together with the Oops log? Please, CC me too so I can follow up quickly.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>