intel driver fails to use dual-link LVDS if lid is down at boot

[Allison Karlitskaya]

This email more or less describes the exact situation I experience on my T420 with Ubuntu:

http://lists.freedesktop.org/archives/intel-gfx/2012-March/015473.html

I have a dock and external monitors. If I boot the laptop with the lid down then when I open the lid, the display is corrupted.

The thread has a patch in it here: http://lists.freedesktop.org/archives/intel-gfx/2012-March/015486.html

I'm going to test that out and report back.

[Jochen (jradmacher)]

When booting with the lid closed and in the docking station, the external Monitor works fine. (two monitors also work) But when opening the lid then laptop screen shows "noise" and a partialy visible and streched picture.
The "noise" does not look like wrong data in the video memory but more like the wrong refresh rate got selected.

System ubuntu natty, with xorg-edgers (error is present in plain install)
- xserver-xorg-video-intel 2:2.15.0+git20110513.9d6e02a1-0ubuntu0sarvatt
- Linux version 2.6.39-2-generic (buildd@king) (gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-8ubuntu4) ) #7-Ubuntu SMP Mon May 16 12:45:34 UTC 2011

[Jochen (jradmacher)]

Created attachment 47302
lspci -v

[Jochen (jradmacher)]

Created attachment 47303
dmesg after booting with *open* lid

[Jochen (jradmacher)]

Created attachment 47304
reg dump after booting with *open* lid

[Jochen (jradmacher)]

Created attachment 47305
dmesg after booting with *closed* lid,now opened

[Jochen (jradmacher)]

Created attachment 47306
regdump after booting with *closed* lid,now opened

[Jochen (jradmacher)]

Created attachment 47308
regdump after booting with *closed* lid,still closed (external monitor)

[Chris Wilson (ickle)]

Lid open:
PCH_DREF_CONTROL: 0x00001402 (cpu source disable, ssc_source enable, nonspread_source enable, superspread_source disable, ssc4_mode downspread, ssc1 enable, ssc4 disable)
PCH_DPLL_A: 0x89086008 (enable, sdvo high speed no, mode LVDS, p2 Div 7, FPA0 P1 4, FPA1 P1 4, refclk SSC, sdvo/hdmi mul 1)

Lid closed:
PCH_DREF_CONTROL: 0x00001400 (cpu source disable, ssc_source enable, nonspread_source enable, superspread_source disable, ssc4_mode downspread, ssc1 disable, ssc4 disable)
PCH_DPLL_A: 0x88026002 (enable, sdvo high speed no, mode LVDS, p2 Div 14, FPA0 P1 2, FPA1 P1 2, refclk SSC, sdvo/hdmi mul 1)

One last test, what happens without the external DVI plugged in?

[Jochen (jradmacher)]

Created attachment 47318
regdump after booting with *closed* lid, no video attached to the docking station

The regdump does _not change_ when opening the lid

[Jochen (jradmacher)]

(In reply to comment #8)
> Created an attachment (id=47318) [details]
> regdump after booting with *closed* lid, no video attached to the docking
> station
>
> The regdump does _not change_ when opening the lid

The display is ok when booting this way. No distortion.

[Jochen (jradmacher)]

Checked again with kernel 3.0. Same issues.

Do you have anything new to test (git is fine too)?

[Jochen (jradmacher)]

Tested this again:
kernel 3.1.1 and X.Org/intel driver as below:

[ 50.386] (II) Loading /usr/lib64/xorg/modules/drivers/intel_drv.so
[ 50.413] (II) Module intel: vendor="X.Org Foundation"
[ 50.413] compiled for 1.11.2, module version = 2.17.0
[ 50.413] Module class: X.Org Video Driver
[ 50.413] ABI class: X.Org Video Driver, version 11.0

Nothing changed, I still have the same issues.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 956046

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Allison Karlitskaya (desrt)]

I just built a kernel package with that patch. It fixes the issue for me.

[Seth Forshee (sforshee)]

There's a newer version of the patch.

http://lists.freedesktop.org/archives/intel-gfx/2012-March/015487.html

It's still not certain this is the final version of the patch though, so we'll need to wait. Once a fix is applied upstream we can look at backporting it.

[Paulo Zanoni (pzanoni)]

(In reply to comment #10)
> Checked again with kernel 3.0. Same issues.
>
> Do you have anything new to test (git is fine too)?

http://lists.freedesktop.org/archives/intel-gfx/2012-March/015552.html

Does this help?

[Allison Karlitskaya (desrt)]

It seems like this is something like the final version of the patch:

http://lists.freedesktop.org/archives/intel-gfx/2012-March/015552.html
http://lists.freedesktop.org/archives/intel-gfx/2012-March/015553.html

[Allison Karlitskaya (desrt)]

I did another test build. I applied the two patches linked above to the latest kernel package (3.2.0-20.32). The fix still works for me.

[Daniel-ffwll (daniel-ffwll)]

Patches which should fix this are queued to drm-intel-next at http://cgit.freedesktop.org/~danvet/drm-intel/

Specifically:

commit b03543857fd75876b96e10d4320b775e95041bb7
Author: Takashi Iwai <email address hidden>
Date: Tue Mar 20 13:07:05 2012 +0100

    drm/i915: Check VBIOS value for determining LVDS dual channel mode, too

Please reopen this bug if this patch does not fix your issues.

[Allison Karlitskaya (desrt)]

Will this go in for 3.4 or wait until 3.5?

[Daniel-ffwll (daniel-ffwll)]

The patch is merged for 3.5 (and already in drm-next).

[Chris Wilson (ickle)]

*** Bug 43379 has been marked as a duplicate of this bug. ***

[Jochen (jradmacher)]

>
> http://lists.freedesktop.org/archives/intel-gfx/2012-March/015552.html
>
> Does this help?
Sorry for the delay.

Today I had some time to test this patch and it did not help with the issue.
Should this patch alone enough fix this, or is something else from the drm-next branch needed?

[Daniel-ffwll (daniel-ffwll)]

Hm, we do have some other patches in drm-intel-next-queued that might apply for your situation here. Please test with that. I'll reopen the bug meanwhile, problem is clearly not yet solved.

[Chris Wilson (ickle)]

Please do retest with 3.7-rc1 as that contains the modeset-rework promised by Daniel.

[Jochen (jradmacher)]

I finally had the chance to retest this Bug. And it is already fixed in 3.5. (I tested 3.5.3)

This is a bit embarrassing: I think I could track the fix to drm-intel-next.

It's included in this build:
commit a85d4bcb8a0cd5b3c754f98ff91ef2b9b3a73bc5
Date: Fri Apr 20 11:50:01 2012 -0700

[Daniel-ffwll (daniel-ffwll)]

Np, and thanks for the update ;-)

[W-florijn-k (w-florijn-k)]

A patch referencing a commit somehow associated to this bug report has been merged in Linux v3.9-rc1:

commit a210b028f07690c127733addbbe137e8f4cad30c
Author: Daniel Vetter <email address hidden>
Date: Mon Nov 26 17:22:08 2012 +0100

    drm/i915: replace ad-hoc dual-link lvds checks

[penalvch (penalvch)]

Ryan Lortie, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

If reproducible, could you also please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.13-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Allison Karlitskaya (desrt)]

As noted on the upstream bug, this has been fixed for quite some time already. I'm guessing (through no special effort) this fix has made its way into Ubuntu at some point and is therefore fixed there as well.