Environment: -------------------------- Kernel: drm-intel-nightly commit 63618e87b05a1e73ce1d1a83f59f6fff6fc19be9 Author: Daniel Vetter <daniel.vetter@ffwll.ch> Date: Sun Jan 26 16:10:58 2014 +0100 drm-intel-nightly: 2014y-01m-26d-16h-10m-49s integration manifest Bug detailed description: ----------------------------- Change the kernel and boot the system, black screen shows. And unable to connect the device via ssh. The keyboard light is able to light up or light off, but the system unable to response keyboard event. We catched the boot log via serial port in attachment, for your reference. It works well on -nightly(f27f16540be56813df2ebb8e1106dd5c258f07c3) yesterday Steps: --------------------------- Change to latest -nightly kernel and boot the system
Created attachment 92831 [details] boot log
Can you pls try to revert 9ba35767fb7766c543f932c4b633b32b386372c1 ? If that's not the bad commit I don't have an idea what's going on here. Can you please attempt a bisect in that case?
(In reply to comment #2) > Can you pls try to revert 9ba35767fb7766c543f932c4b633b32b386372c1 ? > > If that's not the bad commit I don't have an idea what's going on here. Can > you please attempt a bisect in that case? I did not find this commit in -nightly, -next-queued and -fixes branches. I will execute bisect later.
Spotted by Ville: diff --git a/drivers/gpu/drm/i915/i915_gem_context.c b/drivers/gpu/drm/i915/i915_gem_context.c index 310370d..fb64ab4 100644 --- a/drivers/gpu/drm/i915/i915_gem_context.c +++ b/drivers/gpu/drm/i915/i915_gem_context.c @@ -290,7 +290,7 @@ i915_gem_create_context(struct drm_device *dev, goto err_unpin; } - ctx->vm = &dev_priv->mm.aliasing_ppgtt->base; + dev_priv->mm.aliasing_ppgtt = ppgtt; } } else if (USES_ALIASING_PPGTT(dev)) { /* For platforms which only have aliasing PPGTT, we fake the
Rebase fail fixup smashed in, fixed with commit 42c3b603da89d888004f41095d786b593aa6f2b3 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Thu Jan 23 19:40:02 2014 +0000 drm/i915: Always pin the default context
Checked on latest -next-queued(5b2ff3a84a979e42eaf860b4fa25e5b320f38585), this bug had fixed, thanks.
Closing verified+fixed.
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.