I finished the bisect. I am running xubuntu 14.04. I pulled mainline
kernels v3.6 which worked without error and v3.7 which exhibited the
error. I then bisected between the 2. It took 14 steps and concluded
with this which makes more sense:

24929352481f085c5f85d4d4cbc919ddf106d381 is the first bad commit
commit 24929352481f085c5f85d4d4cbc919ddf106d381
Author: Daniel Vetter <[email protected]>
Date:   Mon Jul 2 20:28:59 2012 +0200

    drm/i915: read out the modeset hw state at load and resume time
    
    ... instead of resetting a few things and hoping that this will work out.
    
    To properly disable the output pipelines at the initial modeset after
    resume or boot up we need to have an accurate picture of which outputs
    are enabled and connected to which crtcs. Otherwise we risk disabling
    things at the wrong time, which can lead to hangs (or at least royally
    confused panels), both requiring a walk to the reset button to fix.
    
    Hence read out the hw state with the freshly introduce get_hw_state
    functions and then sanitize it afterwards.
    
    For a full modeset readout (which would allow us to avoid the initial
    modeset at boot up) a few things are still missing:
    - Reading out the mode from the pipe, especially the dotclock
      computation is quite some fun.
    - Reading out the parameters for the stolen memory framebuffer and
      wrapping it up.
    - Reading out the pch pll connections - luckily the disable code
      simply bails out if the crtc doesn't have a pch pll attached (even
      for configurations that would need one).
    
    This patch here turned up tons of smelly stuff around resume: We
    restore tons of register in seemingly random way (well, not quite, but
    we're not too careful either), which leaves the hw in a rather
    ill-defined state: E.g. the port registers are sometimes
    unconditionally restore (lvds, crt), leaving us with an active
    encoder/connector but no active pipe connected to it. Luckily the hw
    state sanitizer detects this madness and fixes things up a bit.
    
    v2: When checking whether an encoder with active connectors has a crtc
    wire up to it, check for both the crtc _and_ it's active state.
    
    v3:
    - Extract intel_sanitize_encoder.
    - Manually disable active encoders without an active pipe.
    
    v4: Correclty fix up the pipe<->plane mapping on machines where we
    switch pipes/planes. Noticed by Chris Wilson, who also provided the
    fixup.
    
    v5: Spelling fix in a comment, noticed by Paulo Zanoni
    
    Reviewed-by: Jesse Barnes <[email protected]>
    Signed-Off-by: Daniel Vetter <[email protected]>

:040000 040000 27592a2f94f6651cf1e96e8826c0d365de7b298c
416fd34aacc0e3f8248a6ff4a1095157f24ad4dd M      drivers

What next?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1324935

Title:
  [Dell Inspiron 1525] WARNING: CPU: 1 PID: 1154 at
  /build/buildd/linux-3.13.0/drivers/gpu/drm/i915/intel_display.c:9226
  intel_modeset_check_state+0x62d/0x780 [i915]()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1324935/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to