[Bug 100725] [i915] oops in intel_update_cursor_plane(): "BUG: unable to handle kernel NULL pointer dereference"

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=100725

--- Comment #5 from krisman at collabora.co.uk ---
(In reply to David H. Gutteridge from comment #4)
> 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?

https://lists.freedesktop.org/archives/intel-gfx/2017-July/133158.html

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 dri-devel at freedesktop.org together with the Oops log? 
Please, CC me too so I can follow up quickly.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170717/84cc9797/attachment.html>