Summary: | [i915][SKL] wayland desktop crash from i915 driver bug: gen8_ppgtt_alloc_page_directories | ||
---|---|---|---|
Product: | DRI | Reporter: | aappddeevv |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | major | ||
Priority: | medium | CC: | aappddeevv, arnaud.kleinveld, dienste, intel-gfx-bugs, mario.diraimondo, pdecat, peter |
Version: | unspecified | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | SKL | i915 features: |
Description
aappddeevv
2017-03-31 15:07:29 UTC
The crash happens when moving the mouse or opening a window, say in Chrome. It appears to be random other than the mouse/window/popup action. commit e2b763caa6eb68ea56918ee6f79b40b82bdcf7c9 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Wed Feb 15 08:43:48 2017 +0000 drm/i915: Remove bitmap tracking for used-pdpes Which is too big for stable and queued for 4.12. So, because the fix is too big for "stable" kernels, kernel 4.10 and 4.11 are therefore unstable for any PC running Intel graphics? I've seen this happen under X, so it's not just Wayland sessions that crash with this bug. Is the fix in drm-intel-nightly? I am running on drm-tip which does not generate this error, it generates another error that seems similar in that it deals with allocation. Devs thought it was a userspace issue with say, gnome-shell, but I'm not so sure. I am running Fedora 25 with 4.10.13 and Xorg crashes one or two times daily with the following message: BUG: unable to handle kernel NULL pointer dereference at 0000000000000018 IP: gen8_ppgtt_alloc_page_directories.isra.36+0x115/0x250 [i915] I guess the fix didn't make it into 4.10.12? Chris, I wonder how you guys find it "ok" to have two major kernel versions (4.10 and 4.11) lockup on users accross the board with no intent to backport the fix ? This is hitting *all* the laptops here in ozlabs since the distros have been updating to 4.10. We can't get more than about a day uptime. This really need a workaround of some sort in 4.10 and 4.11 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.