Bug 58024 - [HD 3000] [Dual Monitor DVI+HDMI] [Asrock Z68 Extreme3 Gen3] Monitor connected to the DVI port randomly receives an incompatible monitor signal and is put to sleep.
Summary: [HD 3000] [Dual Monitor DVI+HDMI] [Asrock Z68 Extreme3 Gen3] Monitor connecte...
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Mika Kuoppala
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-08 17:23 UTC by Freddie F. Haddad
Modified: 2017-07-24 22:59 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments
dmesg (59.59 KB, text/plain)
2012-12-08 17:23 UTC, Freddie F. Haddad 		no flags Details
Xorg log (43.83 KB, text/plain)
2012-12-08 17:24 UTC, Freddie F. Haddad 		no flags Details
xrandr -q (1.58 KB, text/plain)
2012-12-08 17:24 UTC, Freddie F. Haddad 		no flags Details
View All

Description Freddie F. Haddad 2012-12-08 17:23:38 UTC 
Created attachment 71207 [details]
dmesg

Overview
----------------------
I switched to the Intel HD3000 GPU (Sandy Bridge) from a dedicated NVIDIA PCIx GPU. Prior to the switch, the problem to be described never occured. I was successfully able to use the NVIDIA propietary driver mixed with uvesafb, and the nouveau driver (alone).

Hardware
----------------------
Motherboard:  Asrock Z68 Extreme3 Gen3 (latest firmware)
CPU:          Intel Core i5 2500k w/ HD Graphics 3000 (Sandy Bridge)
Overclocking: Stock
Monitor:      (2x) Dell Ultrasharp 2007FP (1600x1200@60Hz)
Connections:  Left monitor is connected via DVI
              Right monitor is connectd via HDMI

Occurs
----------------------
1) During the boot process of any Linux installation media that attempts to load the Intel console frame buffer (Arch) or the Xorg driver (Ubuntu 12.04 and 12.10).

2) During the bootup of a minimum install of Linux (Gentoo, Arch) and during a full desktop installation (Ubuntu).

Symptom
----------------------
During the bootup process, randomly, the left monitor, which is connected to the DVI port on the motherboard, receives a bad signal. The result is either a scrambled picture (think a tv receiving a bad signal via antenna) or the on screen display reporting an incompatible signal and putting the monitor to sleep.

Troubleshooting Steps
----------------------
1) Replaced the DVI cable
2) Moved the left monitor to the right side and connected it to the HDMI cable and moved the right monitor to the left side and connected it to the DVI cable. The problem followed the monitor which indicates the problem is somewhere between the DVI port and the Intel driver.
3) Tried booting via UEFI and BIOS various distributions of Linux (Ubuntu 12.04, Ubuntu 12.10, and Arch) and displayed the same behavior.
4) Reverted to BIOS default values.
5) Reflashed the BIOS.
6) Tried various kernel versions 3.5.0, 3.5.9 EOL, 3.6.8, 3.6.9
*7) Disabled the Intel console frame buffer and switched to the uvesafb frame buffer. However, I was unable to start the X server because I did not have the appropriate drivers to use configured.

* After step 7, the problem has not occured.

Logs (Ubuntu 12.10)
----------------------

Linux fhaddad78-desktop 3.5.0-19-generic #30-Ubuntu SMP Tue Nov 13 17:48:01 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

I will attach the logs separately (exceeding the max characters for the bug report).
Comment 1 Freddie F. Haddad 2012-12-08 17:24:24 UTC 
Created attachment 71208 [details]
Xorg log
Comment 2 Freddie F. Haddad 2012-12-08 17:24:47 UTC 
Created attachment 71209 [details]
xrandr -q
Comment 3 Freddie F. Haddad 2012-12-08 17:29:04 UTC 
Correction:

Under troubleshooting, step 2 should read:

2) Moved the left monitor to the right side and connected it to the HDMI cable and moved the right monitor to the left side and connected it to the DVI cable. The problem **DID NOT** follow the monitor which indicates the problem is somewhere between the DVI port and the Intel driver.
Comment 4 Daniel Vetter 2012-12-08 17:42:24 UTC 
Can you please try the patch at:

https://patchwork.kernel.org/patch/1852411/
Comment 5 Freddie F. Haddad 2012-12-10 23:20:35 UTC 
I played with this for a few days, but I can't quite figure out how to apply the patch and recompile/configure the driver. It's a bit over my head. Any advice on how I can do this and report the results? I can install any linux distro which will make this easier to do so I am very flexible.
Comment 6 Daniel Vetter 2012-12-11 12:29:31 UTC 
Patch is now merged into drm-intel-fixes at http://cgit.freedesktop.org/~danvet/drm-intel

If you need howtos for compiling kernels's from git sources, usually distro's have nice documentation. Or ask on relevant irc channels for help.
Comment 7 Freddie F. Haddad 2012-12-14 17:47:32 UTC 
I'm familiar with configuration/compilation of linux kernels, however, what I'm not familiar with is modifying the source files contained in a particular kernel source package. Is it safe to extract the intel-drm-fixes patch into my /usr/src/linux director and have it overwrite any existing files? Or is there a more appropriate way to do this. I'm currently using the 3.5.7 linux kernel from Gentoo sources.
Comment 8 Freddie F. Haddad 2013-01-13 00:58:17 UTC 
I tested again with the patch and the problem still occurs. I also installed the 3.7.1 kernel from the Gentoo sources with resolution. As another troubleshooting step, I switched the monitor connected to the DVI port to the DSUB (VGA) port and have not had the problem since. So, the current setup is the left (main) monitor is connected via VGA port and the right monitor is connected via HDMI. I will also connecting the right monitor to the DVI port (leaving the left one connected via VGA) and see if the problem occurs. I'm starting to think it might have something to do with using the DVI and HDMI ports simultaneously, however, the motherboard manual says any two of the three video output ports can be used simultaneously, but NOT all three at the same time.
Comment 9 Freddie F. Haddad 2013-01-13 00:59:33 UTC 
CORRECTION: ...Gentoo sources with *NO* resolution...
Comment 10 Daniel Vetter 2013-03-20 11:51:03 UTC 
Could be flaky PLLs, so worth a shot to test with

https://bugs.freedesktop.org/attachment.cgi?id=71767

Applies on top of drm-intel-nightly, but should work on pretty much any reasonable recent kernel. But testing with latest 3.9-rc kernels at least would be good to ensure we have all the other known workarounds.
Comment 11 Jani Nikula 2013-10-10 15:37:57 UTC 
Freddie, there's been plenty of progress since we've last heard from you. Please try the drm-intel-nightly branch of git://people.freedesktop.org/~danvet/drm and report back. Thanks.
Comment 12 Jani Nikula 2013-12-16 14:22:40 UTC 
(In reply to comment #11)
> Freddie, there's been plenty of progress since we've last heard from you.
> Please try the drm-intel-nightly branch of
> git://people.freedesktop.org/~danvet/drm and report back. Thanks.

Should be git://people.freedesktop.org/~danvet/drm-intel, sorry. Please give it a try.

http://cgit.freedesktop.org/~danvet/drm-intel/log/?h=drm-intel-nightly
Comment 13 Jani Nikula 2014-08-14 13:28:32 UTC 
Timeout. Please reopen if the problem persists with recent kernels.

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.