Launchpad has imported 11 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=63383.
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 2013-04-10T14:24:03+00:00 Chris J Arges wrote: Created attachment 77747 Glitchy Output If I attach an external monitor to my Lenovo Thinkpad T420 and type the following command: xrandr --output VGA1 --auto --primary --output LVDS1 --off I get glitchy output as shown in the attached picture. I have tested with a pre-built Ubuntu kernel here: http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/current/ This should be commit bae3699182027525d92b97d904578a533264b242 from the drm-intel tree next branch. The related launchpad bug is here: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1157678 While https://bugs.freedesktop.org/show_bug.cgi?id=57160 is linked in the bug, I believe this is another issue. I've tested with a kernel that contains the patch and it did not fix the issue. My graphics card is: 2nd Generation Core Processor Family Integrated Graphics Controller [8086:116] Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/40 ------------------------------------------------------------------------ On 2013-04-10T14:33:43+00:00 Daniel-ffwll wrote: Ah, a victim for testing a few patches of mine! Please test the pll-limits-mess branch from http://cgit.freedesktop.org/~danvet/drm Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/42 ------------------------------------------------------------------------ On 2013-04-10T19:11:59+00:00 Chris J Arges wrote: Daniel, I've tested with the pll-limits-mess branch, and it resulted in the same output. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/43 ------------------------------------------------------------------------ On 2013-04-10T20:44:39+00:00 Chris Wilson wrote: Can you please attach a drm.debug=6 dmesg and Xorg.log from the latest run? Also the output of intel_reg_dumper would be useful. Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/46 ------------------------------------------------------------------------ On 2013-04-10T21:45:48+00:00 Chris J Arges wrote: Created attachment 77782 dmesg (drm.debug=6) Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/47 ------------------------------------------------------------------------ On 2013-04-10T21:46:09+00:00 Chris J Arges wrote: Created attachment 77783 Xorg.0.log Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/48 ------------------------------------------------------------------------ On 2013-04-10T21:46:35+00:00 Chris J Arges wrote: Created attachment 77784 intel_reg_dump Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/49 ------------------------------------------------------------------------ On 2013-04-10T22:12:26+00:00 Chris Wilson wrote: And the other one is 'cat /sys/kernel/debug/dri/0/i915_gem_framebuffers' Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/50 ------------------------------------------------------------------------ On 2013-04-10T22:36:11+00:00 Chris J Arges wrote: Created attachment 77787 i915_gem_framebuffer Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/51 ------------------------------------------------------------------------ On 2013-04-12T10:42:40+00:00 Chris Wilson wrote: So what I thought might have been happening was that we reused an incorrectly sized cached framebuffer. Not so sure after reading i915_gem_framebuffer. However, I've implemented a defense against using the wrong framebuffer size: commit 9dae6f9f1f169c228929185a8bd94e82afe92574 Author: Chris Wilson <ch...@chris-wilson.co.uk> Date: Fri Apr 12 11:01:08 2013 +0100 sna: Flush the scanout cache after resizing the display And ensure that any new scanout allocations make the requested size. It will be worth updating xf86-video-intel.git and seeing if that makes any difference (will be in ppa:xorg-edgers in a few hours). Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/52 ------------------------------------------------------------------------ On 2013-04-15T16:55:09+00:00 Chris J Arges wrote: Building and installing latest xf86-video-intel.git with HEAD: http://cgit.freedesktop.org/xorg/driver/xf86-video- intel/commit/?id=f0b6ae2cfb811a8c234634c878800ca1fb95703f Seems to resolve the issue, I've tested the original issue of unplugging and plugging in an external monitor, suspending and resuming, and also the xrandr trigger. So far no screen corruption! Reply at: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- intel/+bug/1157678/comments/53 ** Changed in: xserver-xorg-video-intel Status: Unknown => Incomplete ** Changed in: xserver-xorg-video-intel Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1157678 Title: unplugging an external monitor from laptop results in corrupted screen. Logging out fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1157678/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
