Intermittent screen blinking with 4k external mini display port with 4.4 kernels

I'd like to perform a bisect to identify the commit that introduced this regression. To narrow the bisect window, can you test the 4.4.0-1.15 kernel first? It can be downloaded from:

https://launchpad.net/ubuntu/+source/linux/4.4.0-1.15/+build/8880824

This kernel has the bug:

$ cat /proc/version_signature
Ubuntu 4.4.0-1.15-generic 4.4.0

I was unable to bisect between 4.3.0-7.18 and 4.4.0-1.15-generic because the commits are not linear. Due to this, we should test and confirm 4.4.0-0.10 does not have the bug. It shouldn't.

Once we confirm that, I can start a bisect between 4.4.0-0.10 and 4.4.0-1.15-generic.

I built a 4.4.0-0.10 kernel which can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619/

I have booted into this kernel:

$ cat /proc/version_signature
Ubuntu 4.4.0-0.10Commit3b7e590bf-generic 4.4.0

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day on Monday.

This kernel has the bug:

$ cat /proc/version_signature
Ubuntu 4.4.0-0.10Commit3b7e590bf-generic 4.4.0

Thanks for testing, Jamie. This would indicate the bug was introduced somewhere in late 4.3. I'll figure out the best next kernel to test and post it shortly.

I built a 4.4.0-0.3 kernel which was based off of upstream 4.4-rc4. This kernel can be downloaded from:

http://kernel.ubuntu.com/~jsalisbury/lp1547619/

Can you see if this kernel has the bug or not?

I have booted into this kernel:

$ cat /proc/version_signature
Ubuntu 4.4.0-0.3~lp1547619Commit324ae35-generic 4.4.0

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

This kernel has the bug:

$ cat /proc/version_signature
Ubuntu 4.4.0-0.3~lp1547619Commit324ae35-generic 4.4.0

I've been trying to get early Ubuntu 4.4 kernel to build, but not having much luck. Are you unable to test mainline kernels on this system? It would make the bisect much faster.

It is difficult for me to use a non-Ubuntu kernel since I do a lot of work with apparmor for the distro. I suppose I could try for a little while at a time, but my ability to test will be impeded (ie, I'll need to run mainline only when not doing the other work).

Thanks, Jamie. If we can identify which 4.4 release candidate the regression was introduce, we might be able to switch back to Ubuntu kernels for the actual bisect.

Can you test the following upstream kernel to see if it has the bug:

http://kernel.ubuntu.com/~jsalisbury/lp1547619/

I have booted into this kernel:

$ cat /proc/version
Linux version 4.4.0-040400rc1-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160222 (Ubuntu 5.3.1-9ubuntu3) ) #201602231809 SMP Tue Feb 23 23:12:04 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

This kernel has the bug:

$ cat /proc/version
Linux version 4.4.0-040400rc1-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160222 (Ubuntu 5.3.1-9ubuntu3) ) #201602231809 SMP Tue Feb 23 23:12:04 UTC 2016

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:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

I saw a new kernel in xenial with intel fixes so I decided to try it.

This kernel has the bug:
$ cat /proc/version_signature
Ubuntu 4.4.0-9.24-generic 4.4.3

I'll try the bisected kernel now.

The kernels from http://kernel.ubuntu.com/~jsalisbury/lp1547619 are 4.4.0-040400rc1.201602231809 and have the same checksums as the kernels I tested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1547619/comments/15.

I rebuilt the first test kernel and copied it to:

http://kernel.ubuntu.com/~jsalisbury/lp1547619

Hi, just to add some info to this really annoying bug.
I am using external monitors connected through a display port hub which in turn connects to my laptop mini display port.
What I noticed is that this only happens when my monitors are at the 1920 x 1080 resolution. If I switch to 1280 x 1024, this never ever happens.

I have booted into this kernel:

$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160225 (Ubuntu 5.3.1-10ubuntu2) ) #201603030935 SMP Thu Mar 3 14:39:41 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

I saw a new xenial kernel 4.4.0-10.25 come in. All try that one too after this one.

People reported 4.5.0-040500rc6 fixes the bug for them.

You can see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1488719 for reference

I am on 4.5.0 RC6 myself and for me it is not fixed. It is a lot better, screen blinking is reduced a lot but it still happens from time to time.

While I can't be 100% sure cause the issue is intermittent, it seems that this kernel does not have the bug:

$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160225 (Ubuntu 5.3.1-10ubuntu2) ) #201603030935 SMP Thu Mar 3 14:39:41 UTC 2016

$ uptime
 08:44:12 up 3 days, 19 min, 3 users, load average: 1.43, 0.68, 0.57

I built the next test kernel, up to the following commit:
e6604ecb70d4b1dbc0372c6518b51c25c4b135a1

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

I have booted into this kernel:

$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160225 (Ubuntu 5.3.1-10ubuntu2) ) #201603101009 SMP Thu Mar 10 15:13:56 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

FYI, I needed overlayfs and so had to interrupt my 4.3.0-040300-generic (#201603101009) testing and booted into 4.4.0-12.28. 4.4.0-12.28 has the bug.

I am back in 4.3.0-040300-generic (#201603101009) now.

I built the next test kernel, up to the following commit:
2f4bf528eca5b2d9eef12b6d323c040254f8f67c

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

While I can't be 100% sure cause the issue is intermittent, it seems that this kernel does not have the bug:

$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160225 (Ubuntu 5.3.1-10ubuntu2) ) #201603101009 SMP Thu Mar 10 15:13:56 UTC 2016

$ uptime
 14:16:39 up 1 day, 5:18, 2 users, load average: 1.72, 1.29, 1.20

I built the next test kernel, up to the following commit:
b44a3d2a85c64208a57362a1728efb58a6556cd6

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

Having this issue as well. Blinking happens on mini displayport not on mini HDMI (running on Intel NUC with dual monitor setup). Some applications trigger the blinking more often than others. Blinking occurs every few minutes when working in a terminal, but it can happen multiple times in a row. Switching to (or away from) the terminal triggers the bug more often than just working in the terminal.

$ cat /proc/version_signature
Ubuntu 4.4.0-21.37-generic 4.4.6

Hi Onno. Do you have the blinking with all resolutions?

Hi Joseph, any news on this?

@Gronor, we were performing a kernel bisect. However, we are still waiting on test results for the kernel in comment #29. WOuld it be possible for you to test that kernel?

Unfortunately I won't be able to do that. In the meantime I have switched away from Ubuntu and cannot test the kernel you build

Apologies for the delay-- I needed our Ubuntu kernel for a number of weeks and had to pause this bisection.

I have booted into this kernel:

$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160311 (Ubuntu 5.3.1-11ubuntu1) ) #201603151533 SMP Tue Mar 15 19:37:15 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

Ah, that was fast. This kernel has the bug:

$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160311 (Ubuntu 5.3.1-11ubuntu1) ) #201603151533 SMP Tue Mar 15 19:37:15 UTC 2016

There is a similar bug that is now reported fixed in 4.4.9. When you have a chance, could you test that kernel? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4.9-xenial/

I have booted into this kernel:

$ cat /proc/version
Linux version 4.4.9-040409-generic (kernel@gomeisa) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #201605041832 SMP Wed May 4 22:34:16 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

This kernel has the bug:

$ cat /proc/version
Linux version 4.4.9-040409-generic (kernel@gomeisa) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #201605041832 SMP Wed May 4 22:34:16 UTC 2016

I built the next test kernel, up to the following commit:
c0f3f90cf454dd845dcc443afa4f0e312a8eaee0

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

I have booted into this kernel:

$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605111621 SMP Wed May 11 20:26:24 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

This kernel does not seem to have the bug after using the system all day:

$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605111621 SMP Wed May 11 20:26:24 UTC 2016

I built the next test kernel, up to the following commit:
42d4ebb42a17754d2e8344dc1aa486119671d0eb

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

I have booted into this kernel:

$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #201605181045 SMP Wed May 18 14:50:13 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

This kernel has the bug:

$ cat /proc/version
Linux version 4.3.0-040300-generic (jsalisbury@gomeisa) (gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2) ) #201605181045 SMP Wed May 18 14:50:13 UTC 2016

I built the next test kernel, up to the following commit:
816d2206f0f9953ca854e4ff1a2749a5cbd62715

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

I have booted into this kernel:

$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605201447 SMP Fri May 20 18:50:00 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

This kernel has the bug:

$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605201447 SMP Fri May 20 18:50:00 UTC 2016

I built the next test kernel, up to the following commit:
1c431cb4615334fb81c0d1c0ede21aa4354c1187

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance

I have booted into this kernel:

$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605241152 SMP Tue May 24 16:01:12 UTC 2016

Since the bug doesn't always show itself right away, I will want to use the kernel for at least several hours. I'll report back as soon as I see the bug or after using the computer throughout the day.

This kernel has the bug:

$ cat /proc/version
Linux version 4.3.0-040300rc5-generic (jsalisbury@gomeisa) (gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2) ) #201605241152 SMP Tue May 24 16:01:12 UTC 2016

I built the next test kernel, up to the following commit:
a2736b07df1f17c24c8890eb7b2dac529d9725d3

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1547619

Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results.

Thanks in advance