[Bug 1543683] Re: Fails to detect (second) display

** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications about this bug go to:

[Bug 1543683] Re: Fails to detect (second) display

** Changed in: linux (Ubuntu Xenial) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Xenial) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu) Assignee:

[Bug 1543683] Re: Fails to detect (second) display

4.6 test kernel (2dcd0af568b0cf583645c8a317dd12e344b1c72a would seem to be the base) does not exhibit the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second)

[Bug 1543683] Re: Fails to detect (second) display

based on discussion, more work is needed. ** Changed in: linux (Ubuntu Xenial) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to

[Bug 1543683] Re: Fails to detect (second) display

Said kernel appears to be good. The reshuffling of windows does not occur (and I get two displays!!) In the worst case, I'd recommend shipping xenial with 237ed86c reverted, if they can't get a fixed version before our deadline. Holler at me if there's another kernel for me to test. thanks,

[Bug 1543683] Re: Fails to detect (second) display

Can you test one additional kernel? It is the current Xenial kernel with commit 237ed86c also reverted. If this one is good, then commit 7a5c500 (drm/i915: Fix hpd live status bits for g4x). Needs some more work. The latest test kernel is in the usual location:

[Bug 1543683] Re: Fails to detect (second) display

The kernel in #45: 1) exhibits the window shuffling issue. 2) if I lock the screen, and sit back for a few seconds, the display blanks, and then (almost immediately) unblanks. I would expect it to remain blanked until there was mouse or keyboard activity. I suspect that the next step is to

[Bug 1543683] Re: Fails to detect (second) display

I built a 4.4.0-9 with the "original" fix added (and 237ed86c NOT reverted). The kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1543683] Re: Fails to detect (second) display

The kernel in comment #40 exhibits neither the original bug, nor the window-shuffling bug. On a lark, I'd like tip 4.4.0-9 with the "original" fix added (and 237ed86c NOT reverted). All of which assumes that 237ed86c was not reverted as part of landing the fix. Something about this feels like

[Bug 1543683] Re: Fails to detect (second) display

So the kernel posted in comment #40 does not exhibit the original bug, or this possible new bug of the windows getting re-shuffled? The kernel in comment #40 was the tip of 4.4.0-9 with commit 237ed86c reverted and the fix added. -- You received this bug notification because you are a member

[Bug 1543683] Re: Fails to detect (second) display

And I completely misstated myself. :( What I think I want is: 237ed86c with the current patch for this bug applied. Here is what I'm seeing, and trying to isolate it to these two patches, or if it's something yet newer that we'll need to bisect all over again: With current xenial (4.4.0-13 and

[Bug 1543683] Re: Fails to detect (second) display

Rereading #40, what exactly was that kernel? On rereading, it sounds like it was top-of-tree (ish), with 237ed86c reverted and the fix added -- or was it bonafide 237ed86c~1 + the fix? (on which hinges what the kernel to try next is, but the last 2 paragraphs in #41 are still valid) -- You

[Bug 1543683] Re: Fails to detect (second) display

I built a test kernel with commit 237ed86c reverted, like in comment #29. However, I also applied the patch for this bug from the latest Xenial kernel. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683/ -- You received this bug notification because you

[Bug 1543683] Re: Fails to detect (second) display

This bug was fixed in the package linux - 4.4.0-12.28 --- linux (4.4.0-12.28) xenial; urgency=low * Miscellaneous Ubuntu changes - reconstruct: Work around orig tarball packaging limitiations Fixes FTBS -- Tim Gardner Tue, 08 Mar 2016

[Bug 1543683] Re: Fails to detect (second) display

I built a test kernel without the new patch and with commit 237ed86c reverted. Can you see if this new issue still happens with this test kernel? It can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683/NoPatchCommit237ed86cReverted -- You received this bug notification

[Bug 1543683] Re: Fails to detect (second) display

On the other hand, for the "completely unacceptable" part of the diff: locking the screen results in the display going away or something, such that X randomly moves windows from the right hand to the left and vice versa. Just... No. -- You received this bug notification because you are a member

[Bug 1543683] Re: Fails to detect (second) display

** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications

[Bug 1543683] Re: Fails to detect (second) display

4.4.0-9.24~lp1543683Commit8d409cb is a good kernel. (with the now expected lag of ~1/2 second between the two displays refreshing during boot at driver cutover.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1543683] Re: Fails to detect (second) display

I built a Xenial test kernel with the following commit requested by upstream: commit 8d409cb3e8a24196be7271defafd4638f3e0b514 Author: Ville Syrjälä Date: Wed Feb 10 19:59:05 2016 +0200 drm/i915: Fix hpd live status bits for g4x The test kernel can be

[Bug 1543683] Re: Fails to detect (second) display

Possibly a similar issue upstream: https://lkml.org/lkml/2016/2/24/654 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications about

[Bug 1543683] Re: Fails to detect (second) display

Interestingly, while two displays show up in the lspci output, only the one was detected and used. lamont -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second)

[Bug 1543683] Re: Fails to detect (second) display

Here is the boot... Interestingly, it shows 2 displays in lspci. I'm not in front of the computer, so I can't exactly say if it found it or not, but ISTR that it didn't show the device at all (in lspci) in the bad kernels. ** Attachment added: "zz"

[Bug 1543683] Re: Fails to detect (second) display

I created a debug test kernel that bumps the number for tries to 300 and print each try to the log. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683/DEBUG-KERNEL/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1543683] Re: Fails to detect (second) display

Works. Note that during boot, when it flashes (presumably over to the kernel's i915 driver?) there is a noticible delay between the first (00:02.0) display and the second (failing, 00:02.1) display coming up - on the order of "under a second or two". I'm attaching the kernel log from the boot,

[Bug 1543683] Re: Fails to detect (second) display

I built a Xenial test kernel with commit 237ed86c reverted. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683/Commit237ed86cReverted/ Can you test this kernel and see if it resolves the bug? Note, with this test kernel, you need to install both the

[Bug 1543683] Re: Fails to detect (second) display

d2e0 is good 74fc bad 237e bad. We have a winner: 237ed86c is the first failing commit. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage

[Bug 1543683] Re: Fails to detect (second) display

I built all the remaining test kernels but the last one. The test kernels are available from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 The first kernel is in the d2e08c0f3 directory. There are also two sub- directories: bad.cfe01a5e good.7f4c628 Test the kernel in the sub-directory

[Bug 1543683] Re: Fails to detect (second) display

9eca6832f7254d49d25494da7d47c0f8a24f7862 is bad. In the interest of letting me do the rest in one interruption of my primary worksurface, would it be possible for you to build all 7 remaining versions (or throw me a script..), and then I can just reboot a few times for completion. I'm of the

[Bug 1543683] Re: Fails to detect (second) display

That is, if it's convenient to just loop through and build all 7, then throw them into ~jsalisubury/lp1543683/$REF, then I can smash through the reboots in minimal time. (Getting tired of rebuilding my workspace...) -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1543683] Re: Fails to detect (second) display

I built the next test kernel, up to the following commit: 9eca6832f7254d49d25494da7d47c0f8a24f7862 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on

[Bug 1543683] Re: Fails to detect (second) display

23eafea6a9d1faac0588a5275d0c755cb261346e is good (with complaints from the monitor about refreshrate out of range) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect

[Bug 1543683] Re: Fails to detect (second) display

I built the next test kernel, up to the following commit: 23eafea6a9d1faac0588a5275d0c755cb261346e The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on

[Bug 1543683] Re: Fails to detect (second) display

e8cb8d69d125f56fa3ba5239b215a56718e2ca44 is bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications about this bug go to:

[Bug 1543683] Re: Fails to detect (second) display

I built the next test kernel, up to the following commit: e8cb8d69d125f56fa3ba5239b215a56718e2ca44 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on

[Bug 1543683] Re: Fails to detect (second) display

40a4a5727f21a0e439d317aa99953e24467605eb fails. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications about this bug go to:

[Bug 1543683] Re: Fails to detect (second) display

6b6d562 reported as good on IRC. I built the next test kernel, up to the following commit: 40a4a5727f21a0e439d317aa99953e24467605eb The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will

[Bug 1543683] Re: Fails to detect (second) display

I built the next test kernel, up to the following commit: 6b6d5626750d72a22180a6e094cf95acd1d85c9b The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on

[Bug 1543683] Re: Fails to detect (second) display

717d84d67e3a95f440c37c7482681b3535fdc7e2 is bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications about this bug go to:

[Bug 1543683] Re: Fails to detect (second) display

I built the next test kernel, up to the following commit: 717d84d67e3a95f440c37c7482681b3535fdc7e2 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on

[Bug 1543683] Re: Fails to detect (second) display

c0f3f90cf454dd845dcc443afa4f0e312a8eaee0 is bad. (201602161109 timestamp on the kernel build, for confirmation) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second)

[Bug 1543683] Re: Fails to detect (second) display

In the previous comments first should be 'next'. Cut and paste error. ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Status: Incomplete => Confirmed -- You received this bug notification because you

[Bug 1543683] Re: Fails to detect (second) display

I built the first test kernel, up to the following commit: c0f3f90cf454dd845dcc443afa4f0e312a8eaee0 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on

[Bug 1543683] Re: Fails to detect (second) display

b44a3d2a85c64208a57362a1728efb58a6556cd6 is bad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications about this bug go to:

[Bug 1543683] Re: Fails to detect (second) display

118c216e16c5ccb028cd03a0dcd56d17a07ff8d7 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications about this bug go to:

[Bug 1543683] Re: Fails to detect (second) display

e6604ecb70d4b1dbc0372c6518b51c25c4b135a1 is good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683 Title: Fails to detect (second) display To manage notifications about this bug go to:

[Bug 1543683] Re: Fails to detect (second) display

I started a kernel bisect between v4.3 final and v4.4-rc1. The kernel bisect will require testing of about 13 test kernels. I built the first test kernel, up to the following commit: 118c216e16c5ccb028cd03a0dcd56d17a07ff8d7 The test kernel can be downloaded from:

[Bug 1543683] Re: Fails to detect (second) display

I built the first test kernel, up to the following commit: e6604ecb70d4b1dbc0372c6518b51c25c4b135a1 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on

[Bug 1543683] Re: Fails to detect (second) display

I built the first test kernel, up to the following commit: b44a3d2a85c64208a57362a1728efb58a6556cd6 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1543683 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on

[Bug 1543683] Re: Fails to detect (second) display

LaMont Jones, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following: 1) The one to test is at

[Bug 1543683] Re: Fails to detect (second) display

I went the route of bisecting the RCs... rc2: no kernel present in page, which makes rc6 the obvious bisect point rc6: bad. rc4: bad. FIN. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1543683

[Bug 1543683] Re: Fails to detect (second) display

There are over 400 changes to i915 between Ubuntu-4.3.0-7.18 and Ubuntu-4.4.0-2.16. We should probably narrow down the exact kernel version that introduced this first. At the same time, we can see if this is Ubuntu specific, so testing the upstream kernels is best. We need to identify the

[Bug 1543683] Re: Fails to detect (second) display

** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Also affects: linux (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags added: kernel-da-key -- You received this bug notification because you

[Bug 1543683] Re: Fails to detect (second) display

As requested, here is the output of lspci -vvvnn on the good kernel. ** Attachment added: "lspci -vvvnn from 4.3.0-7" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543683/+attachment/4567889/+files/lspci.good -- You received this bug notification because you are a member of Ubuntu