only external screen is working with asus zenbook ux31e [eDP1]

[Oleksij Rempel]

This is regression after some recent (2-3 weeks) xorg? update.

I also tested newest kernel v3.3.0-rc6 with no changes, so we can exclude kernel.

This ultrabook is intensively used. So if you need some testing, i can do it only on weekends.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+10ubuntu1
Uname: Linux 3.3.0-rc6 x86_64
.tmp.unity.support.test.0:

ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,grid,gnomecompat,imgpng,mousepoll,regex,place,vpswitch,move,animation,snap,resize,session,expo,wall,ezoom,fade,workarounds,scale,unityshell]
CompositorRunning: compiz
Date: Sun Mar 4 13:56:04 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 (20120201.1)
MachineType: ASUSTeK Computer Inc. UX31E
ProcEnviron:
 TERM=xterm
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-rc6 root=UUID=ab2e9ae5-a032-44f5-b956-3223de09edff ro oops=panic panic=10 quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.211
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.211:bd01/20/2012: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.7.0~bzr2995-0ubuntu5
version.ia32-libs: ia32-libs 20090808ubuntu33
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ubuntu2
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-1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20111201+b5534a1-1build2

[Timo Aaltonen (tjaalton)]

You can't rule out the kernel if the bug happens on an upstream development kernel, since there might be commits backported to the stable queue that cause regressions.

Boot an older kernel to see if they work.

[Oleksij Rempel (olerem)]

here is aditional info:
xrandr --output eDP1 --auto --output VGA1 --auto --same-as eDP1

i get this error:
xrandr: cannot find crtc for output eDP1

in Xorg.og i get this:
[ 1656.684] (WW) intel(0): flip queue failed: Device or resource busy
[ 1656.684] (WW) intel(0): Page flip failed: Device or resource busy

[Oleksij Rempel (olerem)]

I also tested kernel wich worked befor (3.2.0-12-generic), but it is not working now. so i assum it is not kernel

[Bryce Harrington (bryce)]

Boot an alpha-2 livecd (http://cdimage.ubuntu.com/releases/12.04/alpha-2/) and assuming that works properly, collect the Xorg.0.log, xrandr --verbose, and dmesg from that, to compare with. It's odd that it doesn't show an LVDS output, I wonder if it did previously.

Also, just so I understand your report, are you trying to connect the external display to the VGA port or to the eDP port?

[Oleksij Rempel (olerem)]

alpha2 is working. There is no LVDS too. External port is VGA1, the internal display is eDP1

[Adrien Cunin (adri2000)]

Same problem here: can't display both on the laptop screen and on an external monitor. Laptop screen alone is ok; when plugging the external monitor with VGA, I can only use that external monitor.
It used to work. Dell Latitude E5410, i915 driver.

There are quite a lot of this in Xorg.0.log:
[ 614.160] (WW) intel(0): flip queue failed: Device or resource busy
[ 614.160] (WW) intel(0): Page flip failed: Device or resource busy

When using xrandr:
% xrandr --output eDP1 --auto --output VGA1 --auto --same-as eDP1
xrandr: cannot find crtc for output eDP1

When using gnome-control-center display, dmesg says:
[ 107.800350] [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:3]

I can test experimental packages or workarounds if needed. :-)

[Chris Wilson (ickle)]

I'm wondering if this is related to bug 44039. The issue would appear to be that it is unable to find a free PLL (or the like) for the eDP after it is turned off. eDP isn't limited to the first pipe, so it should be happy to attach to the second CRTC, just a puzzle as to why it did not.

[Chris Wilson (ickle)]

Created attachment 59920
Separate the PLL from the pipes

Something to test.

[Oleksij Rempel (olerem)]

Against what kernel should i test? I tryed vanilla master HEAD, v3.3, v3.2 and intel-next-fixes HEAD. "git am" always fails.

[Chris Wilson (ickle)]

http://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=bug48652 will provide the context you need to apply it. However Jesse mentioned that the ux31e is a CPU eDP and so doesn't use a PCH PLL anyway (and in theory not affected by the patch).

[Bryce Harrington (bryce)]

Ah, I didn't catch it before; this is one of those laptops that uses eDP1 for the laptop display itself. These have been wonky.

Thanks, I think you've collected enough info; we need to forward it upstream.

[Bryce Harrington (bryce)]

Forwarding this bug from Ubuntu reporter Oleksij Rempel:
http://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/946311

[Problem]
Uses eDP1 rather than LVDS1 for the laptop panel. When an external monitor is attached via VGA1 and RANDR used to tweak the config, the laptop panel loses its crtc and can't be enabled.

[Original Description]
This is regression after some recent (2-3 weeks) xorg? update.

I also tested newest kernel v3.3.0-rc6 with no changes.
I also tested kernel which worked before (3.2.0-12-generic), but it is not working now.

I tried beta1 : actually it works until I change the display configuration to disable one screen and try to re-enable both of them. Then I can't get both screens to work again.
I tried beta 1 because IIRC back with beta 1 I didn't have any problem. but maybe it's just that I was lucky and didn't mess enough with the display configuration...

DistroRelease: Ubuntu 12.04
Package: xorg 1:7.6+10ubuntu1
Uname: Linux 3.3.0-rc6 x86_64
.tmp.unity.support.test.0:

ApportVersion: 1.93-0ubuntu2
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,decor,compiztoolbox,grid,gnomecompat,imgpng,mousepoll,regex,place,vpswitch,move,animation,snap,resize,session,expo,wall,ezoom,fade,workarounds,scale,unityshell]
CompositorRunning: compiz
Date: Sun Mar 4 13:56:04 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 (20120201.1)
MachineType: ASUSTeK Computer Inc. UX31E
ProcEnviron:
TERM=xterm
LANG=de_DE.UTF-8ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.3.0-rc6 root=UUID=ab2e9ae5-a032-44f5-b956-3223de09edff ro oops=panic panic=10 quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX31E.211
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.211:bd01/20/2012: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.7.0~bzr2995-0ubuntu5
version.ia32-libs: ia32-libs 20090808ubuntu33
version.libdrm2: libdrm2 2.4.30-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 8.0.1-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 8.0.1-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.11.4-0ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.6.99.901+git20120126-0ub...

[Bryce Harrington (bryce)]

Created attachment 59911
XorgLog.working.txt

Log from a working session with both monitors fired up.

[Bryce Harrington (bryce)]

Created attachment 59912
XorgLog.txt

Log from a broken session, where only the external monitor fires up.

Of note is this error following RANDR log messages, which is not present in the other log:

[ 55.743] (EE) intel(0): failed to set mode: Invalid argument

[Bryce Harrington (bryce)]

Created attachment 59913
dmesg.working.txt

dmesg from a working session

[Bryce Harrington (bryce)]

Created attachment 59914
BootDmesg.txt

[Bryce Harrington (bryce)]

Created attachment 59915
CurrentDmesg.txt

dmesg from broken system.

Nothing interesting in these files.

[Bryce Harrington (bryce)]

Created attachment 59916
xrandr.working.txt

xrandr output from working system

[Bryce Harrington (bryce)]

Created attachment 59917
Xrandr.txt

Broken system's xrandr.

Note that both VGA1 and eDP1 are shown as connected, but no crtc is registered for eDP1.

The user attempted using both the gnome settings capplet, and the xrandr command line tool. For the latter he adds:

"""
here is aditional info:
xrandr --output eDP1 --auto --output VGA1 --auto --same-as eDP1

i get this error:
xrandr: cannot find crtc for output eDP1

in Xorg.og i get this:
[ 1656.684] (WW) intel(0): flip queue failed: Device or resource busy
[ 1656.684] (WW) intel(0): Page flip failed: Device or resource busy
"""

[Bryce Harrington (bryce)]

Oleksij Rempel - I've forwarded this bug upstream to https://bugs.freedesktop.org/show_bug.cgi?id=48652 - please subscribe yourself to this bug, in case they need further information or wish you to test something. Thanks ahead of time!

[Oleksij Rempel (olerem)]

Created attachment 59957
dmesg bug48652

I tested the source from your link and it seems to be completely broken for me. The kernel with latest commit: "drm/i915: manage PCH PLLs separately from pipes". will produce oops on the start. Se attached dmesg. I also tryed to reset the source to HEAD~1, but this kernel will start with black screen.

[Adrien Cunin (adri2000)]

I'm attaching a more detailed kernel log (using drm.debug=999 at boot) of what's happening when using xrandr, in case it could be useful.

[Chris Wilson (ickle)]

Looks like the sequence itself is inconsistent triggering the WARN. Jesse?

[Chris Wilson (ickle)]

Can you set drm.debug=0xe and grab a fresh dmesg of the fail?

[Oleksij Rempel (olerem)]

Do you mean oops of bug48652 tree, or working kernel with current display bug?

[Chris Wilson (ickle)]

For the OOPS presently. I'm looking at whether it is a regression from the PLL patch or elsewhere.

[Chris Wilson (ickle)]

Found the cause, patch on its way.

[Chris Wilson (ickle)]

Branch updated at http://cgit.freedesktop.org/~ickle/linux-2.6/log/?h=bug48652, can you please attach a drm.debug=0xe for the modesetting failure.

[Jesse Barnes (jbarnes-virtuousgeek)]

This seems more likely to be the dithering bug, have you tried with:
commit c4867936474183332db4c19791a65fdad6474fd5
Author: Daniel Vetter <email address hidden>
Date: Tue Apr 10 10:42:36 2012 +0200

    drm/i915: properly compute dp dithering for user-created modes

[Bryce Harrington (bryce)]

@kernel team: This one is still in progress upstream, but they're proposing some kernel patches to test.

[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.

[Oleksij Rempel (olerem)]

Created attachment 60147
dmesg bug48652 (3.4.0-rc2-00197-gba8f6a2)

here is new dmesg bug48652 three, kernel v3.4.0-rc2-00197-gba8f6a2
there is oops with drm.debug=0xe

[Oleksij Rempel (olerem)]

note: i do not need to attach external display to reproduce this oops.

[Daniel-ffwll (daniel-ffwll)]

I'm slightly confused, I don't see any OOPS in the new attachment ... or does the machine die right away?

[Oleksij Rempel (olerem)]

ouch... i right. every time i see call trace i think it is oops :( and some thing really bad happened. I'll be careful next time. There are only warnings will call traces in this dmesg.
But any way, x server fails to start on this kernel and goes to save mode.

[Oleksij Rempel (olerem)]

s/i right/you was right/

[Jesse Barnes (jbarnes-virtuousgeek)]

I guess it's either fixed or the reporter gave up...

[Bug-track-c (bug-track-c)]

Hmm... looks like i missed last message. I'll do some tests tomorrow.

[Daniel-ffwll (daniel-ffwll)]

Please reopen if it's still broken after retesting with the latest bits. We know that eDP is a bit flakey, but knowing which parts are still broken exactly is always helpful.

[Bug-track-c (bug-track-c)]

It still miserably fails :(

- on hotplug, after start - every thing is ok. vga screen will be recognised without problem.

- on coldplug. before power on - laptop screen is blank. vga - shows part of oops message. X is not started, but machine is accessible over ssh.

[Bug-track-c (bug-track-c)]

Created attachment 81446
dmesg-3.10.0-rc6-00406-g73bc88c

dmesg from current nightly git.

[Imre Deak (ideak)]

(In reply to comment #105)
> Created attachment 81446 [details]
> dmesg-3.10.0-rc6-00406-g73bc88c
>
> dmesg from current nightly git.

Could you locate the source line for the oops? With the same build you can trigger it, ideally with the latest -nightly:

$ gdb drivers/gpu/drm/i915/i915.ko
$ l *intel_crtc_set_config+0x216

[Bug-track-c (bug-track-c)]

So, i tasted with latest git 3.10.0-rc7-00854-gf19c9d3 - same result.

(gdb) l *intel_crtc_set_config+0x216
0x2bab0 is in intel_crtc_set_config (/home/lex/tmp/linux/drivers/gpu/drm/i915/intel_display.c:8678).
8673 int num_connectors)
8674 {
8675 int i;
8676
8677 for (i = 0; i < num_connectors; i++)
8678 if (connectors[i].encoder &&
8679 connectors[i].encoder->crtc == crtc &&
8680 connectors[i].dpms != DRM_MODE_DPMS_ON)
8681 return true;
8682

I noticed that in some circumstances i null pointer dereference on xhci driver. Interesting, are these errors connected? Or may be there is some memory region used by what ever, bios, efi?

[Bug-track-c (bug-track-c)]

Seems like disabling "Intel VT-d" solve this oops. I was able to boot with vga+laptop screen and both was working!

I'll do more testing to be sure.

[Bug-track-c (bug-track-c)]

Created attachment 82263
dmesg-3.10.0-rc7-00858-g2a74dfa

Here is dmesg from current git and boot with attached VGA display. Some notes:
- right now it works only with Intel VT-d disabled.
- there is some warnings abut pipe_off wait timed out
- i have only one login screen, on VGA. After login both displays are recognised. On SND both screens are working on already on login.
- what about "Intel VT-d" i use virtualisation intensively, is it possible to fix it?

[Daniel-ffwll (daniel-ffwll)]

Can you please reenable vt-d support and instead boot with intel_iommu=igfx_off? That should only disable vt-d for the intel integrated gfx device (and usually helps as well as turning it off completely).

[Bug-track-c (bug-track-c)]

yes, intel_iommu=igfx_off helps too. Thanks!

[Daniel-ffwll (daniel-ffwll)]

(In reply to comment #111)
> yes, intel_iommu=igfx_off helps too. Thanks!

Ok, that's proof that something _really_ fishy is going on here. Big WTF moment ... Imre do you have any ideas what this could be? Seen anything like this when you've done the sg conversion?

[Bug-track-c (bug-track-c)]

After your comment i did some more tests -- just in case.
Enabled VT-d and removed intel_iommu=igfx_off line. Result is really interesting:
I get oops only on second boot without igfx_off. First boot without igfx_off is ok, both displays are working, but after power off and new start with same configuration - without igfx_off kernel it will oops.

Other Zenbook had similar problem with suspend. After some suspend issue it wasn't able to boot. Reason - memory corruption. May be some thing similar is happening here. And some controller stay confused after power off with not setted "intel_iommu=igfx_off".

[Imre Deak (ideak)]

Created attachment 82344
disable sg compaction

> (In reply to comment #111)
> > yes, intel_iommu=igfx_off helps too. Thanks!
>
> Ok, that's proof that something _really_ fishy is going on here. Big WTF
> moment ... Imre do you have any ideas what this could be? Seen anything like
> this when you've done the sg conversion?

No, I haven't tested vt-d ... But yeah, it may be similar to the swiotlb limitation. Oleksij could you try if the attached patch fixes the problem? I can take a closer look tomorrow.

[Bug-track-c (bug-track-c)]

Yes, it works.

[Imre Deak (ideak)]

(In reply to comment #115)
> Yes, it works.

Thanks, it narrows it down. I looked through the Intel HW IOMMU code and haven't found anything obvious that could explain this.

OTOH, looking again at the dmesg with the crash (dmesg-3.10.0-rc6-00406-g73bc88c) I can't see the HW IOMMU being enabled. I'd expect "PCI-DMA: Intel(R) Virtualization Technology for Directed I/O". Instead I see SWIOTLB being enabled there. But if you are using SWIOTLB I don't understand why igfx_off makes any difference. Also the workaround in my patch should be already active for SWIOTLB, so that shouldn't make any difference either. Could you check if you had that workaround in your test kernel (1625e7e549 - "drm/i915: make compact dma scatter lists creation work with SWIOTLB backend")?

[Chris Wilson (ickle)]

(In reply to comment #107)
> So, i tasted with latest git 3.10.0-rc7-00854-gf19c9d3 - same result.
>
> (gdb) l *intel_crtc_set_config+0x216
> 0x2bab0 is in intel_crtc_set_config
> (/home/lex/tmp/linux/drivers/gpu/drm/i915/intel_display.c:8678).
> 8673 int num_connectors)
> 8674 {
> 8675 int i;
> 8676
> 8677 for (i = 0; i < num_connectors; i++)
> 8678 if (connectors[i].encoder &&
> 8679 connectors[i].encoder->crtc == crtc &&
> 8680 connectors[i].dpms != DRM_MODE_DPMS_ON)
> 8681 return true;
> 8682
>
>
> I noticed that in some circumstances i null pointer dereference on xhci
> driver. Interesting, are these errors connected? Or may be there is some
> memory region used by what ever, bios, efi?

This OOPS is fixed by

commit 2e57f47d317dd035b18634b0c602272529368fcc
Author: Chris Wilson <email address hidden>
Date: Wed Jul 17 12:14:40 2013 +0100

    drm/i915: Fix dereferencing invalid connectors in is_crtc_connector_off()

    In commit e3de42b68478a8c95dd27520e9adead2af9477a5
    Author: Imre Deak <email address hidden>
    Date: Fri May 3 19:44:07 2013 +0200

        drm/i915: force full modeset if the connector is in DPMS OFF mode

No idea why VT-d affects that at all.

[Daniel-ffwll (daniel-ffwll)]

Please retest with latest drm-intel-fixes, specifically

commit 2e6efddd203c15ca5c4700511f717c0e9a3ea31a
Author: Imre Deak <email address hidden>
Date: Fri Aug 23 23:50:23 2013 +0300

    drm/i915: ivb: fix edp voltage swing reg val

[Jani-nikula (jani-nikula)]

Oleksij, if I may ask for another test round with current drm-intel-nightly branch of git://people.freedesktop.org/~danvet/drm as there have been some relevant fixes since we last heard from you. Thanks.

[Bug-track-c (bug-track-c)]

Hi Jani.
If VGA attached on before power on:
only VGA has image. DP has backlight on, but no image.
xrandr list both displays.
After pressing Fn+F8, display switch button, both screens will work.
After this i get some warnings in dmesg.

If VGA attached after boot, both displays are working OK.

Now i able to test HDMI too. And there some issues as well. For example it is not automatically detected after cable was attached.

[Bug-track-c (bug-track-c)]

Created attachment 87402
dmesg-3.12.0-rc4-00468-g16b4e9b

[Bug-track-c (bug-track-c)]

Created attachment 87403
dmesg-3.12.0-rc4-00468-g16b4e9b

[Jani-nikula (jani-nikula)]

(In reply to comment #122)
> Created attachment 87403 [details]
> dmesg-3.12.0-rc4-00468-g16b4e9b

Please do the same with drm.debug=0xe module parameter. Sorry I forgot to mention this before. Thanks.

[Bug-track-c (bug-track-c)]

Created attachment 87441
dmesg-3.12.0-rc4-00468-g16b4e9b

Start with previously attached VGA. Both displays seems to be detected, and listed by xrandr. But DP is blank with backlight on.

[Jani-nikula (jani-nikula)]

(In reply to comment #124)
> Created attachment 87441 [details]
> dmesg-3.12.0-rc4-00468-g16b4e9b
>
> Start with previously attached VGA. Both displays seems to be detected, and
> listed by xrandr. But DP is blank with backlight on.

And does intel_iommu=igfx_off still fix this? If it does, please attach the dmesg for that too. Thanks.

[Bug-track-c (bug-track-c)]

No, intel_iommu=igfx_off do not fix it any more.

[Bug-track-c (bug-track-c)]

Created attachment 87451
dmesg-3.12.0-rc4-00468-g16b4e9b + switch in grub

Here is dmesg with other workaround.
I started laptop with attached VGA and switched it default screen in grub with Fn+F8 button. After it both displays work OK.

[Bug-track-c (bug-track-c)]

Hi, tested yesterdays drm-intel-nightly with hope this patch will fix it:

commit 52e1e223456e3aa747e9932f95948381f04b3b26
Author: Jani Nikula <email address hidden>
Date: Mon Oct 21 10:52:07 2013 +0300

    drm/i915/dp: workaround BIOS eDP bpp clamping issue

suddenly it is not.
Right now i found one more way to bring eDP up. After start i can open gnome-control-center, display setting and press save. No changes needed. It will reenable eDP. Output of xrnadr --verbose, before and after this action, differs only here:
< CRTCs: 1 0 2
---
> CRTCs: 0 1 2

will it help?

[Jesse Barnes (jbarnes-virtuousgeek)]

I'm not sure how X orders the CRTCs, but theoretically that's just the CRTC mask (i.e. which CRTCs can drive that connector). The order they're printed in shouldn't matter...

If moving the actual CRTC made a difference, that would make more sense, but that doesn't seem to be the case here.

[Bug-track-c (bug-track-c)]

Status update, tested on latest git nightly. No changes.

[Oleksij Rempel (olerem)]

Is it possible thet this bug has same oots as this one in acpi?
http://www.spinics.net/lists/kernel/msg1686042.html
https://bugzilla.kernel.org/show_bug.cgi?id=70241

[Jesse Barnes (jbarnes-virtuousgeek)]

Is this still a problem? We've landed some fixes that could affect this, though the X thing still confuses me.

[Oleksij Rempel (olerem)]

No, it is not fixed :(

[Daniel-ffwll (daniel-ffwll)]

I think time to ask again for a retest on drm-intel-nightly, just to keep the bug up-to-date.

[Oleksij Rempel (olerem)]

Still same issue. Internal display enabled, backlight is on, but no image.

[Jani-nikula (jani-nikula)]

Looking at this bug for the umpteent time, I would suggest closing this one, RESOLVED WESUCK, and starting with a clean slate by filing a new bug against v4.0-rc1 or drm-intel-nightly. There's too much baggage here for anyone to look at this with fresh eyes, or if they were fresh while starting they won't be fresh by comment #136.

The new bug can reference this one for historical perspective, but I think it would be best to narrow it down to describing the symptoms running the new kernels only.

How about it, Oleksij?

[Oleksij Rempel (olerem)]

I'm ok with it.

Should i open new bug, you open it with needed description?

[Jani-nikula (jani-nikula)]

(In reply to Oleksij Rempel from comment #137)
> I'm ok with it.
>
> Should i open new bug, you open it with needed description?

I would really appreciate you doing it, so you describe your symptoms, instead of me putting words in your mouth. Thanks.

[Oleksij Rempel (olerem)]

New Bug is 89578

[Jani-nikula (jani-nikula)]

(In reply to Oleksij Rempel from comment #139)
> New Bug is 89578

Many thanks Oleksij. I'm resolving this as dupe of the new one (usually we'd go about this the other way round) so we have links both ways.

*** This bug has been marked as a duplicate of bug 89578 ***