8086:0116 [snb-m-gt2] Blank screen after login or after connecting second monitor

[Mark Russell]

Using precise amd64.

System starts normally without an external display. With an external display plugged in (mini-HDMI to VGA), you can see the lightdm login screen, but after logging in, you get blank screens.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+10ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,resize,grid,mousepoll,move,place,regex,vpswitch,snap,wall,session,animation,fade,expo,workarounds,scale,ezoom,unityshell]
Date: Thu Feb 9 11:17:34 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, whatever it takes to get this fixed in Ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1427]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120127.2)
MachineType: ASUSTeK Computer Inc. UX31E
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-15-generic root=UUID=6fb5c681-fd2b-4e0a-a9a0-d4a1acb88cce ro quiet splash elevator=noop vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.210
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX31E
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.210:bd12/26/2011:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: UX31E
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.6+bzr20110929-0ubuntu8
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0~rc2-0ubuntu5
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0~rc2-0ubuntu5
version.xserver-xorg-core: xserver-xorg-core 2:1.11.3-0ubuntu10
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901-1ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.99~git20111219.aacbd629-0ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.17.0-1ubuntu3
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Bryce Harrington (bryce)]

Hi Mark,

There have been several sandybridge fixes upstream. Could you test the latest drm-intel-fixes kernel? You can install it from the kernel team's PPA: kernel.ubuntu.com/~kernel-ppa/mainline/ Unfortunately that PPA is offline at the moment but should be back online by the end of the day.

[Mark Russell (marrusl)]

Hi Bryce,
Just got back home to my external display. Here are my results so far using the kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-fixes/current/ (uname -r = 3.3.0-994-generic).

Steps: boot all the way to Unity desktop, plug in external display, observe.

Try 1: both screens go black, syslog reports:
Feb 26 08:20:14 ix kernel: [ 116.759740] [drm:pch_irq_handler] *ERROR* PCH poison interrupt
Feb 26 08:20:17 ix kernel: [ 119.188654] [drm:intel_cpt_verify_modeset] *ERROR* mode set failed: pipe 0 stuck

Try 2 and 3: same.

Try 4: external display turns on, laptop display turns off. Syslog only has the first of the two messages (PCH poison interrupt). When I go to System Settings > Displays and try to enable the laptop panel, the dialog box returns:
"The selected configuration for displays could not be applied
could not set the configuration for CRTC 63"
Additional syslog line after attempt to start laptop panel:
Feb 26 08:38:40 ix kernel: [ 398.581027] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3]

So far that's been the experience: most boots (more than 75%) go like Try 1, but sometimes, I get the results of Try 4.

[Joseph Salisbury (jsalisbury)]

Hi Mark,

Do you think you could test the latest mainline kernel? If so, you can get it from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc5-precise/

There is some information on the topic of testing the mainline kernel at:
 https://wiki.ubuntu.com/KernelMainlineBuilds

[Mark Russell (marrusl)]

I've done three boots so far with this kernel. All three times the second display came on. It still always shows the "PCH poison interrupt" error, but not the "pipe 0 stuck" error you get when the external display goes black. You still can't enable the laptop display after attaching the external. But that's an improvement overall.

[Mark Russell (marrusl)]

I take it back. I've seen failures now. Same two errors. I also tried with the display connected from boot, which looked good all the way through lightdm, but it went black when x loaded.

[Joseph Salisbury (jsalisbury)]

Hi Mark,

That might indicate this bug exists upstream as well. Do you think you could test some earlier kernels, such as Oneiric[0] or Lucid[1]? That way we can see if this is a regression.

[0] https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/3126697
[1] https://launchpad.net/~canonical-kernel-team/+archive/ppa/+build/3066546

[Mark Russell (marrusl)]

Hi Joe,

Sorry for the slowness. I tested several times booting off an Oneiric live USB and dual monitors works fine. No evidence of the [drm:pch_irq_handler] or [drm:intel_cpt_verify_modeset] errors.

When I installed precise on January 27, dual monitor was working. I would say the regression occurred sometime a week or two later.

[Mark Russell (marrusl)]

I don't get either error when I plug in a 1920 x 1200 display. Just with 2048 x 1152.

I still can't use both if the external is plugged in at startup, but the external does work each time.

[Joseph Salisbury (jsalisbury)]

Hey Mark,

The v3.3 kernel is now release. Can you test the 3.3 kernel before we try to bisect the issue in 3.2? The kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[madbiologist (me-again)]

There was a fix for a similar (same?) problem on this hardware in the upstream 3.5 kernel, which is available in Ubuntu 12.10 "Quantal Quetzal". I also recall seeing a more recent fix for large displays in one of the 3.6-rc's upstream, so you might want to also try the 3.6.1 kernel available at http://kernel.ubuntu.com/~kernel-ppa/mainline/
Instructions oh how to install and remove the mainline kernels are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds

[Dennis Kruyt (dennis-kruyt)]

Got the same problem on 12.10 on a ivy bridge and intel HD4000, some times after log in black screen, als when I switch users in X.

Kernel show these messages:

[ 241.667578] [drm:intel_cpt_verify_modeset] *ERROR* mode set failed: pipe 0 stuck

This happens on stock 12.10 kernel and on kernel 3.6.2 from the ppa

Linux neghvar 3.6.2-030602-generic #201210121823 SMP Fri Oct 12 22:24:18 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

[Joseph Salisbury (jsalisbury)]

@Mark

Have you had a chance to see if this bug still exists in Quantal?

[Mark Russell (marrusl)]

Hi Joe. I worked around my issues last cycle by switching to a 1920x1200 external monitor (worked around blank screen after lightdm) and the "attach-reattach" issue by switching to VGA (from HDMI).

But since you asked, I went back and checked again on quantal (i.e. back to the 2048x1152 and HDMI). Looks good! Works in general, and attach-reattach works perfectly so far.

Do you need help trying to determine what could be SRU'd to precise? Or would this fall under "go to the enablement stack" ?

The only real issue I have left is the fact that if I boot with the external display attached, that's the only display that will work at all. But that's LP #946311.

@Dennis, I think, the mode set issue on Ivy Bridge is a separate issue. I would file a new bug.

[Joseph Salisbury (jsalisbury)]

Hi Mark,

If you have a chance, can you test the latest upstream v3.2 stable kernel:

v3.2.32: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2.32-precise/

That will tell us if it's already fixed and on it's way to Precise.

[Mark Russell (marrusl)]

Hey Joe,

Good news! It looks like the fix is there. I installed the kernel above (note: on quantal) and tested: a few boots and more than a few attach reattach sequences. Everything worked perfectly.

Mark

[Joseph Salisbury (jsalisbury)]

That's good news. The fix will make it's way into Precise, once Precise receives the stable updates from upstream. If you can, would it be possible for you to test Precise and then mark this bug "Fix Released" once the fix is in Precise?

[Mark Russell (marrusl)]

Although now I see that I'm getting an occasional flicker on the external display (with normal quantal). Sometimes 1 minute apart, sometimes longer. No log entry. Well, I suppose that's a different bug!

[penalvch (penalvch)]

Closing tasks given this is fixed in Quantal, which was backported already to Precise.