Launchpad has imported 18 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=40172.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-08-17T16:26:43+00:00 Robert Hooker wrote: Created attachment 50311 Script to reproduce Forwarding this for launchpad bug reporter Marc Deslauriers https://bugs.launchpad.net/ubuntu/+source/linux/+bug/814325 After f0575e92974d328e8816ed89704c985a7d7d90ac (drm/i915: DP_PIPE_ENABLED must check transcoder on CPT) was introduced in the kernel this person's Lenovo T510 machine started to come back from dpms fuzzy (see attached pictures) randomly, and another dpms cycle corrects it. This is still a problem on 3.1-rc2, and seems to be limited to this one machine with an optimus configuration (set to use only the integrated GPU) after testing on a wide variety of other machines including another T510 with an intel only config. He can reproduce the bug with the attached epilepsy.sh script which does rapid dpms off and on again easily. System environment: -- chipset: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] -- system architecture: amd64 -- xf86-video-intel/xserver/mesa/libdrm version: both ubuntu 11.04 and current 11.10 were tested. 11.04: libdrm 2.4.23, xf86-video-intel 2.14, mesa 7.10.2, xserver 1.10.1, kernel 2.6.38-11.48 11.10: libdrm 2.4.26, xf86-video-intel 2.15.901, mesa 7.11, xserver 1.10.2.902, kernel 3.0.1 -- kernel version: 2.6.38-11 (which has the above commit backported), 3.1-rc2, various other kernels in between those two -- Linux distribution: Ubuntu 11.04, Ubuntu 11.10 -- Machine or mobo model: Lenovo T510 (4313CTO) -- Display connector: LVDS Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/73 ------------------------------------------------------------------------ On 2011-08-17T16:27:26+00:00 Robert Hooker wrote: Created attachment 50312 Screenshot without the problem Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/74 ------------------------------------------------------------------------ On 2011-08-17T16:27:45+00:00 Robert Hooker wrote: Created attachment 50313 Screenshot with the problem Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/75 ------------------------------------------------------------------------ On 2011-08-17T16:28:39+00:00 Robert Hooker wrote: Created attachment 50314 Xorg.0.log Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/76 ------------------------------------------------------------------------ On 2011-08-17T16:29:30+00:00 Robert Hooker wrote: Created attachment 50315 dmesg with debug info (after reproducing the problem) Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/77 ------------------------------------------------------------------------ On 2011-08-17T16:30:25+00:00 Robert Hooker wrote: Created attachment 50316 dmesg with debug info (just before reproducing the problem) Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/78 ------------------------------------------------------------------------ On 2011-08-17T16:30:57+00:00 Robert Hooker wrote: Created attachment 50317 intel_reg_dumper output (before) Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/79 ------------------------------------------------------------------------ On 2011-08-17T16:31:16+00:00 Robert Hooker wrote: Created attachment 50318 intel_reg_dumper output (after) Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/80 ------------------------------------------------------------------------ On 2011-08-17T16:31:38+00:00 Robert Hooker wrote: Created attachment 50319 xrandr --verbose Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/81 ------------------------------------------------------------------------ On 2011-08-18T15:31:34+00:00 Jesse Barnes wrote: I can't make sense of this based on the commit... I'm afraid this might be timing related rather than an actual register change, since the register dumps before & after are identical. Can you isolate which part of the patch causes problems? Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/83 ------------------------------------------------------------------------ On 2011-08-18T16:09:30+00:00 Robert Hooker wrote: (In reply to comment #9) > I can't make sense of this based on the commit... I'm afraid this might be > timing related rather than an actual register change, since the register dumps > before & after are identical. > > Can you isolate which part of the patch causes problems? Argh, I'm terribly sorry for this but the actual offending commit was drm/i915: disable PCH ports if needed when disabling a CRTC Which needed a bit of fixing to apply to .38, but has the same failure in both the backport and the upstream kernel http://kernel.ubuntu.com/git?p=ubuntu/ubuntu- natty.git;a=commit;h=bbeaf8811ba070fd186dfcabc957044c3a1149ac Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/84 ------------------------------------------------------------------------ On 2011-08-18T16:28:14+00:00 Jesse Barnes wrote: Ah ok, that makes more sense. Does this patch change anything? We might be disabling LVDS incorrectly (i.e. without a corresponding panel power sequence): diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_d index 35364e6..ab8a36d 100644 --- a/drivers/gpu/drm/i915/intel_display.c +++ b/drivers/gpu/drm/i915/intel_display.c @@ -1394,7 +1394,7 @@ static void intel_disable_pch_ports(struct drm_i915_privat val = I915_READ(reg); if (ADPA_PIPE_ENABLED(val, pipe)) I915_WRITE(reg, val & ~ADPA_DAC_ENABLE); - +#if 0 reg = PCH_LVDS; val = I915_READ(reg); if (LVDS_PIPE_ENABLED(val, pipe)) { @@ -1402,7 +1402,7 @@ static void intel_disable_pch_ports(struct drm_i915_privat POSTING_READ(reg); udelay(100); } - +#endif disable_pch_hdmi(dev_priv, pipe, HDMIB); disable_pch_hdmi(dev_priv, pipe, HDMIC); disable_pch_hdmi(dev_priv, pipe, HDMID); Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/85 ------------------------------------------------------------------------ On 2011-08-18T17:17:37+00:00 Marc Deslauriers wrote: @Jesse, Unfortunately no, I can still reproduce with the patch in comment 11. Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/86 ------------------------------------------------------------------------ On 2011-08-18T17:20:29+00:00 Robert Hooker wrote: (In reply to comment #12) > @Jesse, > > Unfortunately no, I can still reproduce with the patch in comment 11. he tested on 3.0.1 there with this kernel http://kernel.ubuntu.com/~sarvatt/fdo40172/ Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/87 ------------------------------------------------------------------------ On 2011-08-19T17:27:41+00:00 Jesse Barnes wrote: Can you try to isolate which part of the PCH port disable causes trouble? My other guess would be the panel register unlock, which might allow a clock change or something else to sneak in and cause LVDS problems... Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/88 ------------------------------------------------------------------------ On 2011-09-07T21:30:59+00:00 Chris Wilson wrote: I wonder if this relates to drm/i915: Enable dither whenever display bpc < frame buffer bpc? Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/89 ------------------------------------------------------------------------ On 2012-01-05T17:56:06+00:00 Marc Deslauriers wrote: FYI, I still have this issue with 3.2.0. Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/100 ------------------------------------------------------------------------ On 2012-04-14T17:44:31+00:00 Daniel-ffwll wrote: Created attachment 59984 manual revert of offending patch Can you please try with the latest 3.3 kernel (or maybe even 3.4-rc) and check whether this patch still solves your issues? Reply at: https://bugs.launchpad.net/linux/+bug/814325/comments/102 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/814325 Title: fuzzy and corrupted display after DPMS cycles To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/814325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
