Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Fix Released
|
High
|
|||
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned |
Bug Description
*** Temporary workaround ***
Install Kernel from the following location:
- http://
OR
Perform the following:
- $ apt-add-repository "deb http://
- $ echo -en "Package: *\nPin: release o=LP-PPA-
- $ apt update
- $ apt install linux-image-
```
There was a typo in instructions (/etc/preferences.d should have been /etc/apt/
As result you might have upgraded Linux META packages and therefor you won't receive proper upgrades of Xenial native Linux packages (hoping they will ever contain the fix).
I suggest you move /etc/preference
$ apt update
$ apt install linux-headers-
```
***
Please inspect duplicate reports for more details:
Bug #1522922
Bug #1535048
Bug #1552304
Bug #1555158
Bug #1561729
Bug #1565234
Bug #1568599
Bug #1573392
does not affect 4.4.0-8
affects 4.4.0-9 to 4.4.0-22
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-generic 4.4.0.11.12
ProcVersionSign
Uname: Linux 4.4.0-8-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CurrentDesktop: KDE
Date: Tue Mar 8 09:57:12 2016
HibernationDevice: RESUME=
InstallationDate: Installed on 2016-01-07 (61 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0c45:670c Microdia
Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9350
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.156
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
dmi.bios.date: 01/08/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 07TYC2
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.
Thomas Bonfort (thomas-bonfort) wrote : | #1 |
- AlsaInfo.txt Edit (35.9 KiB, text/plain; charset="utf-8")
- CRDA.txt Edit (392 bytes, text/plain; charset="utf-8")
- CurrentDmesg.txt Edit (76.4 KiB, text/plain; charset="utf-8")
- Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
- IwConfig.txt Edit (508 bytes, text/plain; charset="utf-8")
- JournalErrors.txt Edit (31.4 KiB, text/plain; charset="utf-8")
- Lspci.txt Edit (12.4 KiB, text/plain; charset="utf-8")
- ProcCpuinfo.txt Edit (4.4 KiB, text/plain; charset="utf-8")
- ProcEnviron.txt Edit (331 bytes, text/plain; charset="utf-8")
- ProcInterrupts.txt Edit (3.2 KiB, text/plain; charset="utf-8")
- ProcModules.txt Edit (8.0 KiB, text/plain; charset="utf-8")
- PulseList.txt Edit (19.5 KiB, text/plain; charset="utf-8")
- RfKill.txt Edit (113 bytes, text/plain; charset="utf-8")
- UdevDb.txt Edit (161.7 KiB, text/plain; charset="utf-8")
- WifiSyslog.txt Edit (143.7 KiB, text/plain; charset="utf-8")
penalvch (penalvch) wrote : | #2 |
tags: | added: latest-bios-1.2.3 |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
status: | New → Incomplete |
tags: | added: regression-release |
Thomas Bonfort (thomas-bonfort) wrote : | #3 |
I have tested 4.5.0-040500rc7
tags: | added: kernel-bug-exists-upstream-4.5-rc7 |
tags: | added: kernel-bug-exists-upstream |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
penalvch (penalvch) wrote : | #4 |
Thomas Bonfort, the next step is to fully commit bisect from kernel 4.4.0-8 to 4.4.0-9 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https:/
Please note, finding adjacent kernel versions is not fully commit bisecting.
After the offending commit (not kernel version) has been identified, then please mark this report Status Confirmed.
Thank you for your understanding.
Helpful bug reporting tips:
https:/
tags: | added: needs-bisect |
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
Thomas Bonfort (thomas-bonfort) wrote : | #5 |
I'm unable to run the bisection. The first bisect step between Ubuntu-4.4.0-8.23 and Ubuntu-4.4.0-9.24 from git://kernel.
pranith (bobby-prani) wrote : | #6 |
I think this bug is caused by the backported i915 driver in 4.4.0-9 which is being loaded as i915_bpo.
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
penalvch (penalvch) wrote : | #7 |
Thomas Bonfort, have you had a chance to review the section https:/
Changed in linux (Ubuntu): | |
status: | Confirmed → Incomplete |
Thomas Bonfort (thomas-bonfort) wrote : | #8 |
Christopher,
Yes I have read that section but it is not useful as selecting between bad/good is already the required workflow. The issue is that the documentation refers to using the packaging scripts in the debian/ subdir, which is not present and/or usable in the intermediate bisecting steps.
I'm currently testing using this workflow, please advise if it is the correct one:
make mrproper && git clean -d -f && git checkout debian
git bisect good/bad/skip
cp /boot/config-
make oldconfig
make-kpkg --rootcmd=fakeroot --append-to-version "-04-deadbeef" --initrd --us --uc kernel_image -j4
#install and test kernel
here is my current bisect log. note that I have to skip many commits as they fail to compile:
git bisect start '--' 'drivers/gpu/' 'include/drm/' 'include/uapi/drm/' 'ubuntu/i915'
# good: [463f21c6a2dcc9
git bisect good 463f21c6a2dcc90
# bad: [b8723f286caa92
git bisect bad b8723f286caa921
# good: [1cb8570bf04ab1
git bisect good 1cb8570bf04ab12
# skip: [19ed21af1bffa6
git bisect skip 19ed21af1bffa66
# skip: [a9b3cdd235bf96
git bisect skip a9b3cdd235bf966
# skip: [8bfcd31065a60f
git bisect skip 8bfcd31065a60ff
# skip: [693a6307552437
git bisect skip 693a63075524374
# good: [34f091b3d14dad
git bisect good 34f091b3d14dadd
# skip: [abfd1387464d2e
git bisect skip abfd1387464d2e7
# skip: [975bc60948107b
git bisect skip 975bc60948107bc
# good: [98e1eef7fa2b71
git bisect good 98e1eef7fa2b711
# skip: [1f955e92dc87f4
git bisect skip 1f955e92dc87f48
# skip: [7d5329085d3e64
git bisect skip 7d5329085d3e64b
# skip: [8167675659a930
git bisect skip 8167675659a9300
# skip: [8ba5c26373f1e4
git bisect skip 8ba5c26373f1e43
# skip: [197b480eac049b
Thomas Bonfort (thomas-bonfort) wrote : | #9 |
I have tested 4.0.0-13 which does not seem to exhibit the flickering present from 4.0.0-9 to 4.0.0-12. It does however now present tearing artifacts when switching focus between windows, see https:/
Thomas Bonfort (thomas-bonfort) wrote : | #10 |
After a couple of hours using 4.0.0.13 the flickering has re-appeared.
description: | updated |
Thomas Bonfort (thomas-bonfort) wrote : | #11 |
I have finished bisecting the commits and the switch from i915 to i915_bpo seems to be the culprit. There are quite a few candidates but that's because all those skipped commits failed to build/compile.
Note that on the first flicker after booting, this message appears in dmesg:
[drm:intel_
Here is the log of the bisect:
git bisect start '--' 'drivers/gpu/' 'include/drm/' 'include/uapi/drm/' 'ubuntu/i915'
# good: [463f21c6a2dcc9
git bisect good 463f21c6a2dcc90
# bad: [b8723f286caa92
git bisect bad b8723f286caa921
# good: [1cb8570bf04ab1
git bisect good 1cb8570bf04ab12
# skip: [19ed21af1bffa6
git bisect skip 19ed21af1bffa66
# skip: [a9b3cdd235bf96
git bisect skip a9b3cdd235bf966
# skip: [8bfcd31065a60f
git bisect skip 8bfcd31065a60ff
# skip: [693a6307552437
git bisect skip 693a63075524374
# good: [34f091b3d14dad
git bisect good 34f091b3d14dadd
# skip: [abfd1387464d2e
git bisect skip abfd1387464d2e7
# skip: [975bc60948107b
git bisect skip 975bc60948107bc
# good: [98e1eef7fa2b71
git bisect good 98e1eef7fa2b711
# ski...
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
description: | updated |
tags: |
added: bisect-done removed: needs-bisect |
Thomas Bonfort (thomas-bonfort) wrote : | #12 |
introduced in LP: #1540390
Thomas Bonfort (thomas-bonfort) wrote : | #13 |
4.5.0-040500 is still affected
tags: |
added: kernel-bug-exists-upstream-4.5 removed: kernel-bug-exists-upstream-4.5-rc7 |
Thomas Bonfort (thomas-bonfort) wrote : | #14 |
also present in 4.5.0-994-
penalvch (penalvch) wrote : | #15 |
Thomas Bonfort. the issue you are reporting is an upstream one. Could you please report this problem following the 1.1 - DRM Kernel instructions verbatim at https:/
Please provide a direct URL to your post when it becomes available so that it may be tracked.
Thank you for your understanding.
Changed in linux (Ubuntu): | |
importance: | Medium → High |
status: | Confirmed → Triaged |
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #32 |
I'm experiencing what seems to be random flickering (not related to hiding cursor as seen on #93945).
https:/
[359d2243117a79
from drm-intel-next still exhibits the issue
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #33 |
I've bisected this down with relative confidence (had to mark commits from 4.3 as artificially good as the system was not usable with this older version of the kernel):
921ec285a6589cf
commit 921ec285a6589cf
Author: Rodrigo Vivi <email address hidden>
Date: Wed Nov 18 11:21:12 2015 -0800
Here is the full bisect log:
git bisect start '--' 'drivers/
# bad: [359d2243117a79
git bisect bad 359d2243117a795
# good: [1cb8570bf04ab1
git bisect good 1cb8570bf04ab12
# good: [afd2ff9b7e1b36
git bisect good afd2ff9b7e1b367
# bad: [2a33d93486f247
git bisect bad 2a33d93486f2479
# bad: [013d37520af735
git bisect bad 013d37520af735f
# good: [b1a14c6e40413f
git bisect good b1a14c6e40413f8
# good: [78e0d2e3477aa3
git bisect good 78e0d2e3477aa3e
# good: [a6d09186fa27de
git bisect good a6d09186fa27dea
# good: [ca1a95334ddaf6
git bisect good ca1a95334ddaf62
# bad: [9bbc8258ae5914
git bisect bad 9bbc8258ae5914a
# bad: [05eec3c2709d89
git bisect bad 05eec3c2709d896
# bad: [bb929cbc1f58c7
git bisect bad bb929cbc1f58c72
# bad: [921ec285a6589c
git bisect bad 921ec285a6589cf
# first bad commit: [921ec285a6589c
Thomas Bonfort (thomas-bonfort) wrote : | #16 |
upstream issue opened at : https:/
Thomas Bonfort (thomas-bonfort) wrote : | #17 |
Stille present with 4.4.0-16 , and after updating BIOS to latest 1.3.3 version
description: | updated |
tags: |
added: latest-bios-1.3.2 removed: latest-bios-1.2.3 |
Thomas Bonfort (thomas-bonfort) wrote : | #19 |
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
1.3.3
03/01/2016
tags: |
added: latest-bios-1.3.3 removed: latest-bios-1.3.2 |
Eugene San (eugenesan) wrote : | #20 |
I would like to add few observations:
1. Seems like the issue is Power Management related since I've never experienced it with AC adapter connected and sometimes almost instantly after disconnecting it, the flickering is started.
2. Sometimes first "flick" after reboot or PM change is accompanied with "[drm:intel_
3. My dmesg is not as clean as the one provided by original reporter. It filled with quite a few bug/dump reports of i915 driver. Attaching my dmesg.log.
4. Once in a while, I find the computer in state which seems like a hardware "hang" but I suspect it's an i915 driver fault since sometimes after a prolonged wait the computer finally wakes up and later I find the errors mentioned in 3. Note those hangs can happen even if the computer is powered from AC and no automatic suspend is configured.
Seems like upstream bug report didn't get the attention it deserves, any ideas on how to assist with this bug(s) resolution?
Eugene San (eugenesan) wrote : | #21 |
Thomas Bonfort (thomas-bonfort) wrote : | #22 |
For me, the flickering happens with or without AC. And First flicker always ends up having the FIFO error message being printed.
Daniel Basten (axhm3a) wrote : Re: [Bug 1554613] Re: screen flickering on XPS13 9350 | #23 |
I do confirm that behavior
Thomas Bonfort <email address hidden> schrieb am Sa., 2. Apr. 2016,
18:05:
> For me, the flickering happens with or without AC. And First flicker
> always ends up having the FIFO error message being printed.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1561729).
> https:/
>
> Title:
> screen flickering on XPS13 9350
>
> Status in linux package in Ubuntu:
> Triaged
>
> Bug description:
> see LP: #1552304
>
> does not affect 4.4.0-8
> affects 4.4.0-9 to 4.4.0-16
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-generic 4.4.0.11.12
> ProcVersionSign
> Uname: Linux 4.4.0-8-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Tue Mar 8 09:57:12 2016
> HibernationDevice: RESUME=
> InstallationDate: Installed on 2016-01-07 (61 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0c45:670c Microdia
> Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: Dell Inc. XPS 13 9350
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> RelatedPackageV
> linux-restricte
> linux-backports
> linux-firmware 1.156
> SourcePackage: linux
> UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
> dmi.bios.date: 01/08/2016
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: 1.2.3
> dmi.board.name: 07TYC2
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A01
> dmi.chassis.type: 9
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.
> dmi.product.name: XPS 13 9350
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https:/
>
Eugene San (eugenesan) wrote : Re: screen flickering on XPS13 9350 | #24 |
I am still not 100% sure but after a day with this kernel: http://
1. No flickering
2. No more kernel dumps/bugs reports
3. No more i915 warnings
4. No more suspend issues
5. No more Dell WMI events errors
6. Not that it wasn't great but battery life seems to be improved (might be a placebo effect)
Looks like Linux 4.4 is just not ready for Skylake and backporting all the fixes is going to be hell for both maintainers and users.
If I were in position, I would push for Kernel 4.6 as an official kernel variant for 16.04 (before 16.04.1).
I just hope Dell will create enough momentum for those issues to be resolved soon, after all it's their flagship device with official Ubuntu support.
Thomas Bonfort (thomas-bonfort) wrote : | #25 |
No change with 4.6-rc1-wily for me
Daniel Basten (axhm3a) wrote : | #26 |
as mentioned in #1561729:
kernel 4.6rc1 also did not fixed the issue for me
Daniel Basten (axhm3a) wrote : | #27 |
In freedesktop.org Bugzilla #94593, penalvch (penalvch) wrote : | #34 |
Could someone at Intel please assign this to offending commit committer Rodrigo Vivi (or request he assign himself)?
Unfortunately, bugzilla won't allow one to either assign him or CC as per error message:
Assignee:
rodrigo.vivi AT intel DOT com did not match anything
Also, this seems strange one cannot assign him given Intel's documentation states to report here as per https:/
Despite this, increasing importance, given it's bisected, reproducible for a few folks as reported downstream, and reproducible in latest drm-intel-nightly.
Timo Aaltonen (tjaalton) wrote : | #28 |
i915_bpo is tracking 4.6, and 4.4.0-17 has essentially the same driver as 4.6-rc1. Does reverting that commit fix it? Also, you could try booting with 'i915.enable_psr=1' to actually use PSR, which should be stable on SKL now, assuming X is using the intel driver.
Thomas Bonfort (thomas-bonfort) wrote : | #29 |
with 4.4.0-16: flickers with or without i915.enable_psr=1 , and with or without reverting rodrigo's commit found by bisection
with 4.4.0-17: X does not start , I'm left with a blank screen. happens with or without i915.enable_psr
Thomas Bonfort (thomas-bonfort) wrote : | #30 |
- Xorg.0.log Edit (16.5 KiB, text/plain)
failed X startup with 4.4.0-17. Let me know if you want more info.
Thomas Bonfort (thomas-bonfort) wrote : | #31 |
In freedesktop.org Bugzilla #94593, Jani-nikula (jani-nikula) wrote : | #35 |
(In reply to Christopher M. Penalver from comment #2)
> Could someone at Intel please assign this to offending commit committer
> Rodrigo Vivi (or request he assign himself)?
>
> Unfortunately, bugzilla won't allow one to either assign him or CC as per
> error message:
> Assignee:
> rodrigo.vivi AT intel DOT com did not match anything
Done now, it's just that he's registered here with another email address. Writing just parts of the name will show up alternatives.
Changed in linux: | |
importance: | Unknown → High |
status: | Unknown → In Progress |
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #39 |
Created attachment 122707
revert of bisected commit...
Hi there,
First of all please accept my apologies for using different emails here and in the commits. But besides the auto-complete with only my name as Jani suggested I'm always open for direct emails.
So, there are 2 separated tests that I'd like you to to perform:
1. Apply the attached patch and let me know if the issue goes away.
2. Without applying any patch boot with i915.enable_psr=2.
Thanks,
Rodrigo.
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #40 |
Rodrigo:
I have already tried reverting that commit (in ubuntu's mainline kernel, i.e. in their backported i915_bpo module) but the flickering still occurs.
I may have messed up my bisect: from memory, b1a14c6e40413f8 78e0d2e3477aa3e
I will try psr=2 and let you know.
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #41 |
enable_psr=2 still flickers with 4.4.0-16. unable to try latest 4.4.0-17 as X doesn't start with it.
dmesg|grep i915
[ 0.000000] Command line: BOOT_IMAGE=
[ 0.000000] Kernel command line: BOOT_IMAGE=
[ 1.540320] [drm] Finished loading i915/skl_
[ 1.566144] [drm] Initialized i915_bpo 1.6.0 20160214 for 0000:00:02.0 on minor 0
[ 1.820091] i915_bpo 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 3.962877] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_
[ 191.798099] [drm:intel_
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #42 |
what about i915.enable_psr=0?
Timo Aaltonen (tjaalton) wrote : Re: screen flickering on XPS13 9350 | #36 |
you didn't install linux-image-extra, which has most of the drivers, including i915..
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #43 |
4.4.0-17 (which backports i915 from 4.6.0-rc1 IIUC) flickers with enable_psr = 0, 1 and 2.
My impression after a short test is that the flickering occurs more frequently when set to 0 than 1 or 2.
Thomas Bonfort (thomas-bonfort) wrote : | #37 |
Timo: with -extra installed I can now boot up successfully. The flickering still occurs with enable_psr=0, 1 and 2 . It seems to occur more frequently when set to 0
Timo Aaltonen (tjaalton) wrote : | #38 |
0 is the default, PSR isn't enabled (yet)
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #44 |
Given it happens even with i915.enable_psr=0 I'm sure the bisect was misslead at some point.
I'm starting to suspect on Watermark.
Could you please try to apply the following series to see if it helps:
https:/
https:/
https:/
https:/
https:/
https:/
https:/
https:/
Thanks,
Rodrigo.
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #45 |
On top of which SHA do you want me to apply these? Should I apply them all or test the one by one ?
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #46 |
All at once preferably on top of drm-intel-nightly.
In case you have conflicts just let me know that I try to prepare a repo for you.
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #47 |
could you quickly walk me through as to how to apply these please? I know nothing about patchwork.
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #48 |
OK, I'm applying them manually.
The 7th one is failing:
git apply -v /home/tbonfort-
Checking patch drivers/
error: while searching for:
#include <linux/pm.h>
#include <linux/
#include <linux/oom.h>
static int i915_getparam(
error: patch failed: drivers/
error: drivers/
Checking patch drivers/
Hunk #1 succeeded at 1984 (offset -38 lines).
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #49 |
using 3-way:
/**
* i915_driver_
* @dev_priv: device private
*
* Setup minimal device state necessary for MMIO accesses later in the
* initialization sequence. The setup here should avoid any other device-wide
* side effects or exposing the driver via kernel internal or user space
* interfaces.
*/
static int i915_driver_
{
struct drm_device *dev = dev_priv->dev;
int ret;
<<<<<<< ours
if (i915_inject_
=======
/* walk the dmi device table for getting platform memory information */
if (!dev_priv-
/* Setup the write-once "constant" device info */
device_info = (struct intel_device_info *)&dev_priv->info;
>>>>>>> theirs
if (i915_get_
ret = i915_mmio_
if (ret < 0)
return 0;
put_bridge:
return ret;
}
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #50 |
hm, I had a different conflict on my patch 7 here, so not sure... Anyway I prepared a branch with these 8 patches on top of nightly:
https:/
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #51 |
Rodrigo,
sorry for being a noob here...: what remote should I add to get to that branch?
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #52 |
there is nothing wrong that needs apologies here ;)
Thank you very much for your report and effort helping us here!
git remote add vivijim git://people.
git fetch vivijim
git checkout vivijim/
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #53 |
can you please advise as to the workflow I should be using to compile a meaningfull kernel to test this, starting from the config used by ubuntu?
this is what I'm inclined to do:
make mrproper
cp /boot/config-
make oldconfig
#reply to the questions to the best of my knowledge, set i915 debugging to true
#should there be some questions I should reply with something non-default?
make
make modules
sudo make modules_install
sudo make modules
In freedesktop.org Bugzilla #94593, Timo Aaltonen (tjaalton) wrote : | #54 |
better way is to just
make -j N deb-pkg INSTALL_MOD_STRIP=1
after copying the config there, and adjust N to match your cpu thread count
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #55 |
Flickering still present on watermarks-wa
cp /boot/config-
make -j 4 deb-pkg INSTALL_MOD_STRIP=1
#answer default on everything except i915 debugging
booted using no specific enable_psr flags
$ dmesg|grep i915
[ 1.754871] [drm] Finished loading i915/skl_
[ 2.280124] [drm] Initialized i915 1.6.0 20160330 for 0000:00:02.0 on minor 0
[ 3.331669] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 4.452639] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_
[ 207.155111] [drm:intel_
the first flickering occurs at the time the underrun message appears in the logs (after a minute or so of usage)
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #56 |
booting with enable_psr=1 leads to same results:
$ dmesg|grep i915
[ 0.000000] Command line: BOOT_IMAGE=
[ 0.000000] Kernel command line: BOOT_IMAGE=
[ 1.743617] [drm] Finished loading i915/skl_
[ 1.774134] [drm] Initialized i915 1.6.0 20160330 for 0000:00:02.0 on minor 0
[ 3.376327] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 4.397625] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_
[ 185.017240] [drm:intel_
Changed in linux: | |
status: | In Progress → Incomplete |
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #58 |
The bug's status is NEEDINFO. Is there anything more you need from me?
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #59 |
Another bisect attempt would be ideal.
Since it happens with i915.enable_psr=0 it is not PSR related.
But anyway, could you please provide more info about your system:
- full dmesg after booting with drm.debug=0xe
- /var/log/Xorg.0.log
- what graphical environment you use
- do you have an external monitor attached?
- Is there anything special that triggers the flickering? something like: "it starts flickering when having more than one monitor I try to move the cursor to the external one"
- Could you please try i915.enable_dc=0 i915.disable_
Thanks,
Rodrigo.
BlackLight (blacklight86) wrote : Re: screen flickering on XPS13 9350 | #57 |
Same issue on Dell XPS 13 9343.
Running Arch Linux, 4.4.5-1-ARCH, x86_64.
$ pacman -Q | grep xf86-video-intel
xf86-video-intel 1:2.99.
$ pacman -Q | grep xorg-server
xorg-server 1.18.3-1
Things went better when I upgraded from 1:2.99.
dmesg log lines when the issue occurs:
[ 7780.306704] [drm:intel_
[ 7824.405766] [drm:intel_
[ 7865.757760] [drm:intel_
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #60 |
Created attachment 122843
dmesg with drm.debug on 4.4.0-18 up until first flicker
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #61 |
Created attachment 122844
Xorg.0.log
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #62 |
>what graphical environment you use
KDE plasma
>do you have an external monitor attached?
No
>Is there anything special that triggers the flickering? something like: "it starts flickering when having more than one monitor I try to move the cursor to the external one"
No special trigger. First happens between 30secs and 5 minutes after boot, then by salves of ~3-10 flickers separated by a few seconds, followed by a few minutes with no flickering. Flickers seem to happen essentially when the machine is more or less idling.
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #64 |
Created attachment 122845
dmesg with enable_dc=0 disable_
In freedesktop.org Bugzilla #94593, Nhellwege (nhellwege) wrote : | #65 |
(In reply to thomas bonfort from comment #27)
> Created attachment 122845 [details]
> dmesg with enable_dc=0 disable_
Ive been following this bug for a while.
It seems to me that the bug does not occur while fullscreen video playback, which includes fullscreen chrome youtube and netflix, as well als fullscreen vlc playback. Can someone confirm? Hope this helps.
Is another bisect still needed? I might be able to do that.
Daniel Basten (axhm3a) wrote : Re: screen flickering on XPS13 9350 | #63 |
Is there anything i can do to support?
In freedesktop.org Bugzilla #94593, Peteryuchuang (peteryuchuang) wrote : | #72 |
(In reply to thomas bonfort from comment #26)
> >what graphical environment you use
> KDE plasma
> >do you have an external monitor attached?
> No
> >Is there anything special that triggers the flickering? something like: "it starts flickering when having more than one monitor I try to move the cursor to the external one"
> No special trigger. First happens between 30secs and 5 minutes after boot,
> then by salves of ~3-10 flickers separated by a few seconds, followed by a
> few minutes with no flickering. Flickers seem to happen essentially when the
> machine is more or less idling.
I believe I am having the same problem. I am on XPS 13 9350 too, and now on 4.6-rc3 kernel. And yes the flickers do tend to occur when the machine is kind of idling.
My suspicion is that it has something to do with RC6. When I change the i915.enable_rc6 parameter from 7 to 0, the flickering seems to go away. The problem is, of course, disabling RC6 will drain battery a lot faster.
PS. I notice that even with i915.enable_rc6=7, the GPU never goes to RC6p and RC6pp. Is that not supported on Skylake yet?
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #73 |
RC6p/RC6pp split got deprecated few generations ago. So on Skylake RC6 is the deepest already.
Thomas, do you confirm disabling RC6 the flickerings goes away for you as well?
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #74 |
nhellwege another bisect would be awesome for sure. Thanks
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #75 |
Uhm interesting that even with i915.enable_dc=0 you Thomas are getting
[ 17.788425] [drm:gen9_
What firmware version do you have loaded?
cat /sys/kernel/
In freedesktop.org Bugzilla #94593, Peteryuchuang (peteryuchuang) wrote : | #76 |
Here's the dmesg FYI:
$ dmesg|grep i915
[ 0.000000] Command line: BOOT_IMAGE=
[ 0.000000] Kernel command line: BOOT_IMAGE=
[ 0.897902] [drm] Finished loading i915/skl_
[ 0.917624] [drm] Initialized i915 1.6.0 20160229 for 0000:00:02.0 on minor 0
[ 2.644829] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 9.329977] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_exit [i915])
[ 24.371605] WARNING: CPU: 0 PID: 884 at drivers/
[ 24.371669] af_alg dm_crypt dm_mod sd_mod rtsx_pci_sdmmc mmc_core atkbd libps2 crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd ahci libahci xhci_pci libata xhci_hcd rtsx_pci scsi_mod usbcore usb_common i8042 serio i915 video button i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm intel_agp intel_gtt
[ 24.371722] [<ffffffffa013f
[ 24.371731] [<ffffffffa013f
[ 24.371742] [<ffffffffa0149
[ 342.932696] [drm:intel_
In freedesktop.org Bugzilla #94593, Nhellwege (nhellwege) wrote : | #77 |
I am currently bisecting the kernel again and one thing I realize is that I can detect an error through dmesg and then set the commit to bad, but after reviewing some kernels which I have marked as good, it turns out these were bad too. This messed up my bisect and I have to start over again.
Does anyone know how to specifically excite the error? So far I mostly open chrome and open netflix and youtube, since browsing through the galleries sometimes helps to see the bug, but unfortunately not always. Any method is welcomed and could speed up my bisect a lot :)
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #78 |
(In reply to Rodrigo Vivi from comment #30)
> RC6p/RC6pp split got deprecated few generations ago. So on Skylake RC6 is
> the deepest already.
>
> Thomas, do you confirm disabling RC6 the flickerings goes away for you as
> well?
with i915.enable_rc6=0 the flickering is gone. Maybe unrelated, but after waking up from suspend I am now getting a new message:
i915_bpo 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #79 |
(In reply to Rodrigo Vivi from comment #32)
> Uhm interesting that even with i915.enable_dc=0 you Thomas are getting
> [ 17.788425] [drm:gen9_
>
> What firmware version do you have loaded?
> cat /sys/kernel/
fw loaded: yes
path: i915/skl_
version: 1.26
DC3 -> DC5 count: 0
DC5 -> DC6 count: 0
program base: 0x09004040
ssp base: 0x00002fc0
htp: 0x00b40068
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #80 |
(In reply to thomas bonfort from comment #35)
> (In reply to Rodrigo Vivi from comment #30)
> > RC6p/RC6pp split got deprecated few generations ago. So on Skylake RC6 is
> > the deepest already.
> >
> > Thomas, do you confirm disabling RC6 the flickerings goes away for you as
> > well?
>
> with i915.enable_rc6=0 the flickering is gone. Maybe unrelated, but after
> waking up from suspend I am now getting a new message:
>
> i915_bpo 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
I thought I had waited long enough before reporting, but apparently not so :)
I just had a salve of flickers even with rc6=0. dmesg shows the usual:
[17243.901481] [drm:intel_
In freedesktop.org Bugzilla #94593, ash (ashley-b) wrote : | #81 |
looks like a power management issues dating 8 months back, Also happened on the broadwell systems https:/
This makes any linux system a pain to work because of this integrated gpu driver . Skylake has been out for 7 months and we still have problems
In freedesktop.org Bugzilla #94593, Peteryuchuang (peteryuchuang) wrote : | #82 |
I'm not sure if this is kind of expected for this particular bug, but it seems that the problem doesn't happen when the laptop is plugged into the power.
In freedesktop.org Bugzilla #94593, Timo Aaltonen (tjaalton) wrote : | #83 |
sounds like a dupe of
https:/
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #84 |
(In reply to Peter Y. Chuang from comment #39)
> I'm not sure if this is kind of expected for this particular bug, but it
> seems that the problem doesn't happen when the laptop is plugged into the
> power.
Flickering happens with AC plugged here
In freedesktop.org Bugzilla #94593, Peteryuchuang (peteryuchuang) wrote : | #85 |
(In reply to thomas bonfort from comment #41)
> (In reply to Peter Y. Chuang from comment #39)
> > I'm not sure if this is kind of expected for this particular bug, but it
> > seems that the problem doesn't happen when the laptop is plugged into the
> > power.
>
> Flickering happens with AC plugged here
Which kernel are you using at the moment?
In freedesktop.org Bugzilla #94593, Nhellwege (nhellwege) wrote : | #86 |
(In reply to tranceash from comment #38)
> looks like a power management issues dating 8 months back, Also happened on
> the broadwell systems https:/
> This makes any linux system a pain to work because of this integrated gpu
> driver . Skylake has been out for 7 months and we still have problems
I am starting to believe that the common error
[drm:intel_
is not actually responsible for the flicker. To be more precise, the FIFO underrun may result in conjunction with a flicker, but is not a unique indication. I am currently bisecting the kernel and right now I am on commit 5ffd4da+. This commit does show the FIFO underun but not at the same time the screen turns completely black for a split second.
I assume the flicker (screen completely black for a split second) is not directly mapped by the FIFO underrun.
Reading https:/
In freedesktop.org Bugzilla #94593, Peteryuchuang (peteryuchuang) wrote : | #87 |
(In reply to nhellwege from comment #43)
> (In reply to tranceash from comment #38)
> > looks like a power management issues dating 8 months back, Also happened on
> > the broadwell systems https:/
> > This makes any linux system a pain to work because of this integrated gpu
> > driver . Skylake has been out for 7 months and we still have problems
>
> I am starting to believe that the common error
>
> [drm:intel_
> FIFO underrun
>
> is not actually responsible for the flicker. To be more precise, the FIFO
> underrun may result in conjunction with a flicker, but is not a unique
> indication. I am currently bisecting the kernel and right now I am on commit
> 5ffd4da+. This commit does show the FIFO underun but not at the same time
> the screen turns completely black for a split second.
>
> I assume the flicker (screen completely black for a split second) is not
> directly mapped by the FIFO underrun.
>
> Reading https:/
> is at least related, if not identical.
I tend to agree with you that the error
[drm:intel_
may not be specific to the problem we are talking about here.
Regarding my previous comment on whether the laptop is plugged into AC, Thomas is right: if I wait long enough, the flicker does occur even when plugged in, although much less frequent on my machine.
Interestingly, now that I am plugged into AC, the CPU pipe A FIFO underrun thing is no longer the error I see. Instead, this is the error I saw on dmesg:
[ 2045.481992] [drm:intel_
This is the first time I see this error since I started looking for the solution for this problem.
Hope this might give you some clues.
Moondog (hroosen) wrote : Re: screen flickering on XPS13 9350 | #66 |
While I noticed the screen-flicker doesn't show while compiling a linux kernel, I am guessing the problem might be related to c-states. After adding "intel_
While disabling c-states is not acceptable as a workaround, it might help to find the root-cause of the problem for the (Intel) developers. Can anyone confirm the c-state relation?
Daniel Basten (axhm3a) wrote : Re: [Bug 1554613] Re: screen flickering on XPS13 9350 | #67 |
I will try current Kernel with disable c-states give me a few hours.
Moondog <email address hidden> schrieb am Mi., 20. Apr. 2016, 07:21:
> While I noticed the screen-flicker doesn't show while compiling a linux
> kernel, I am guessing the problem might be related to c-states. After
> adding "intel_
> flicker hasn't shown anymore.
>
> While disabling c-states is not acceptable as a workaround, it might
> help to find the root-cause of the problem for the (Intel) developers.
> Can anyone confirm the c-state relation?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1561729).
> https:/
>
> Title:
> screen flickering on XPS13 9350
>
> Status in Linux:
> Incomplete
> Status in linux package in Ubuntu:
> Triaged
>
> Bug description:
> see LP: #1552304
>
> does not affect 4.4.0-8
> affects 4.4.0-9 to 4.4.0-16
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-generic 4.4.0.11.12
> ProcVersionSign
> Uname: Linux 4.4.0-8-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Tue Mar 8 09:57:12 2016
> HibernationDevice: RESUME=
> InstallationDate: Installed on 2016-01-07 (61 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0c45:670c Microdia
> Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: Dell Inc. XPS 13 9350
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> RelatedPackageV
> linux-restricte
> linux-backports
> linux-firmware 1.156
> SourcePackage: linux
> UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
> dmi.bios.date: 01/08/2016
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: 1.2.3
> dmi.board.name: 07TYC2
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A01
> dmi.chassis.type: 9
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.
> dmi.product.name: XPS 13 9350
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https:/
>
Daniel Basten (axhm3a) wrote : Re: screen flickering on XPS13 9350 | #68 |
i am on 4.4.0-21-generic with intel_idle.
but I still got the flickering display:
[ 188.260368] [drm:intel_
antonino elia mandri (antonino-elia) wrote : | #69 |
i am on 4.6.0-997-generic drm-intel-next and flicker is not present since one week
antonino elia mandri (antonino-elia) wrote : | #70 |
while on kernel 4.6 rc4 screen-flicker is present
Brad Buran (bburan) wrote : | #71 |
Currently running Xenial. Kernel 4.4.0-18 and 4.4.0-21 have the screen flicker. Currently on Kernel 4.3.3-040303. No screen flicker. Please let me know what other information you need to help debug this.
In freedesktop.org Bugzilla #94593, Nhellwege (nhellwege) wrote : | #93 |
Created attachment 123104
bisect log for underrun FIFO Error
Bisect log for the i915 Underrun FIFO ERROR. Since no clear method is known on how to excite the error, the bisect might be unfinished. All bad commits did show the FIFO error AND also the Flicker. All good ones did not within a reasonable time (I testet each good Kernal at least 30 minutes). There are some (many) skippes commits, which I was not able to build. The Faulty commit must be somewhere in these skipped commits.
Thomas Bonfort (thomas-bonfort) wrote : Re: screen flickering on XPS13 9350 | #88 |
I've been on 4.6.0-997-generic drm-intel-next for a day and can confirm that the flickering is gone
In freedesktop.org Bugzilla #94593, Nhellwege (nhellwege) wrote : | #94 |
(In reply to tranceash from comment #38)
> looks like a power management issues dating 8 months back, Also happened on
> the broadwell systems https:/
> This makes any linux system a pain to work because of this integrated gpu
> driver . Skylake has been out for 7 months and we still have problems
Ok, I looked into that bug and it seems its not the same. It specifically mentions external monitors and also not black screen flickering, but more a graphical flickering, without the completely black frames in between.
Nevertheless, I tried the proposes patches from https:/
Also, it seems that the FIFO error does appear for the first flicker, but not for any ones after the first, so in my opinion, it can be used as an error criteria.
I could bisect the kernel further, but as seen in https:/
In freedesktop.org Bugzilla #94593, Rodrigo-vivi (rodrigo-vivi) wrote : | #95 |
Probably a bisect on drm-intel-nightly is less painful.
But it seems that we are indeed now duplicating the discussion and there is more information on the other bug. Please reopen if you believe this one here is a different case.
*** This bug has been marked as a duplicate of bug 91393 ***
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #96 |
If the underlying issue is the same then fine. I can confirm that the resulting appearance of this current bug is very different than what the video shows in 91393
In freedesktop.org Bugzilla #94593, Thomas Bonfort (thomas-bonfort) wrote : | #97 |
As another user confirms on https:/
In freedesktop.org Bugzilla #94593, O-jay (o-jay) wrote : | #98 |
On my end, the issue looks like a random "blanking" of the screen for 1/4 of a second, two or three times or so in a row. It can happen several times in a few minutes, but I've also seen it last 20 minutes between occurrences. On my end it looks nothing like in that video.
In freedesktop.org Bugzilla #94593, Nhellwege (nhellwege) wrote : | #99 |
(In reply to thomas bonfort from comment #49)
> As another user confirms on
> https:/
> flickering has disappeared on the latest drm-intel-next
I can confirm that the blank screen flickering is gone with 4.6.0-997-generic intel-drm-next.
Just a follow up question: I am not that familiar with Kernel releases, but as I understand, the 4.4. has long term support, whereas the 4.6. doesnt. Will the driver from the 4.6. eventually be backported to 4.4.?
Thanks for all the effort which has gone into this bug.
In freedesktop.org Bugzilla #94593, Nhellwege (nhellwege) wrote : | #100 |
(In reply to jay from comment #50)
> On my end, the issue looks like a random "blanking" of the screen for 1/4 of
> a second, two or three times or so in a row. It can happen several times in
> a few minutes, but I've also seen it last 20 minutes between occurrences. On
> my end it looks nothing like in that video.
Yes, that is the same with me. I dont know if the underlying issues are identical, but the blanking of the screen is totally different from the graphical flickering in #91393.
In freedesktop.org Bugzilla #94593, Peteryuchuang (peteryuchuang) wrote : | #101 |
(In reply to nhellwege from comment #51)
> (In reply to thomas bonfort from comment #49)
> > As another user confirms on
> > https:/
> > flickering has disappeared on the latest drm-intel-next
>
> I can confirm that the blank screen flickering is gone with
> 4.6.0-997-generic intel-drm-next.
>
> Just a follow up question: I am not that familiar with Kernel releases, but
> as I understand, the 4.4. has long term support, whereas the 4.6. doesnt.
> Will the driver from the 4.6. eventually be backported to 4.4.?
>
> Thanks for all the effort which has gone into this bug.
I can confirm that the flickering is gone with the latest drm-intel-next kernel too.
Thanks everyone.
In freedesktop.org Bugzilla #94593, Jani-nikula (jani-nikula) wrote : | #102 |
Thanks, closing. Please reopen or file new bugs if the problems persist. (Please be careful about not reopening this one if you have bug 91393)
Timo Aaltonen (tjaalton) wrote : | #89 |
could you bisect either drm-intel-next or -nightly kernels to point out where it got fixed?
Timo Aaltonen (tjaalton) wrote : | #90 |
I suspect even the oldest nightly works fine.. so check -next builds starting from the second newest (newest was already found working)
In freedesktop.org Bugzilla #94593, pranith (bobby-prani) wrote : | #103 |
Is this really resolved? The problem is gone, but I don't think anyone identified what is really causing the problem to occur. Also, we need to identify which patch fixed the issue so that it can be back-ported. Both 4.5 and 4.6 kernels have this problem.
In freedesktop.org Bugzilla #94593, Nhellwege (nhellwege) wrote : | #104 |
I could try to bisect https:/
Should this be done? Bisecting is very tedious.
tags: | added: cherry-pick |
In freedesktop.org Bugzilla #94593, Jani-nikula (jani-nikula) wrote : | #105 |
(In reply to Pranith Kumar from comment #55)
> Is this really resolved? The problem is gone, but I don't think anyone
> identified what is really causing the problem to occur.
In a perfect world we'd get to the roots of every problem, but in reality we don't have the time to keep debugging issues that seem to be gone. Especially in areas where we've done a lot of fixing upstream.
> Also, we need to
> identify which patch fixed the issue so that it can be back-ported. Both 4.5
> and 4.6 kernels have this problem.
If the v4.6-rc kernels still have the issue, but drm-intel-nightly works, it should be a pretty straightforward reverse bisect to find the commit that fixed the bug. If you provide that, it may be possible to do the backport.
Richard Platt (richard-d-platt) wrote : | #91 |
Please could someone explain how I upgrade my kernel to the one with the fix. Thanks.
Richard Platt (richard-d-platt) wrote : | #92 |
Please ignore my last comment I figured it out:
plattr@beatrice:~$ uname -a
Linux beatrice 4.6.0-994-generic #201604242200 SMP Mon Apr 25 02:03:20 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
plattr@beatrice:~$
Changed in linux: | |
status: | Incomplete → Fix Released |
pranith (bobby-prani) wrote : Re: screen flickering on XPS13 9350 | #106 |
The bug is apparently fixed in the latest intel-drm-next branch. We still need to identify the fix and backport it to the kernel in Ubuntu. Any bisecting help is appreciated.
summary: |
- screen flickering on XPS13 9350 + screen flickering on XPS13 9350/9550 |
summary: |
- screen flickering on XPS13 9350/9550 + Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) |
description: | updated |
description: | updated |
pranith (bobby-prani) wrote : | #107 |
@eugenesan Does the temporary workaround fix this issue? AFAIK, it is still present in 4.6 rc mainline kernels and only fixed in intel-drm-next which will go to 4.7-rc1.
tags: | added: needs-reverse-bisect |
Eugene San (eugenesan) wrote : | #108 |
@pranith
On my system, 4.6.0rc3+
Other people report solution only with more recent version, 4.6.0rc5+
The difference in reports might be related to installed BIOS version or/and power management behavior in different conditions.
Anyways, I highly recommend updating XPS systems to BIOS v1.33 since it fixes so called "blank screen" issues which might be related.
Lorenzo Bettini (bettini) wrote : | #109 |
you mean this one?
http://
Eugene San (eugenesan) wrote : | #110 |
@bettini
I guess any 4.6.0rc+
pranith (bobby-prani) wrote : | #111 |
@eugenesan but the workaround you posted in the summary lists mainline kernels. These kernels still have the problem so they are not work arounds. The link posted by @bettini will solve the current problem, but they have other bugs(suspend resume bug). So there is no current work around for this problem without introducing other bugs.
tags: | added: kernel-da-key |
Boris Erdmann (boris-erdmann) wrote : | #112 |
This bug is fixed for me in http://
Daniel Basten (axhm3a) wrote : | #113 |
How can I optain linux-image-extra for http://
The flicker is gone, but docker with aufs isn't working anymore.
Eugene San (eugenesan) wrote : | #114 |
Hi all,
Please report your experience with 4.4.0-22.
It seems to be ok on my XPS13.
description: | updated |
Kostadin Stoilov (kmstoilov) wrote : | #115 |
I have the latest kernel 4.4.0-22.39, but the flickering is still present on an XPS 15 9550.
description: | updated |
Eugene San (eugenesan) wrote : | #116 |
@kmstoilov Please make sure you've updated computer's firmware to 1.3.3.
Brad Buran (bburan) wrote : | #117 |
I have a XPS 13 9350. Screen flicker bug is still present.
~ ❯❯❯ uname -r
4.4.0-22-generic
Computer's BIOS is on 1.3.3.
Luís Correia (luis-correia) wrote : Re: [Bug 1554613] Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) | #118 |
Easy workaround: turn bluetooth on
Learned from http://
LC
No dia 13/05/2016, às 18:30, Brad Buran <email address hidden> escreveu:
> I have a XPS 13 9350. Screen flicker bug is still present.
>
> ~ ❯❯❯ uname -r
> 4.4.0-22-generic
>
> Computer's BIOS is on 1.3.3.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1565234).
> https:/
>
> Title:
> Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
>
> Status in Linux:
> Fix Released
> Status in linux package in Ubuntu:
> Triaged
>
> Bug description:
>
> *** Temporary workaround ***
> Install Kernel from one of the following locations:
> - http://
> - http://
> ***
>
> Please inspect duplicate reports for more details:
> Bug #1522922
> Bug #1535048
> Bug #1552304
> Bug #1555158
> Bug #1561729
> Bug #1565234
> Bug #1568599
> Bug #1573392
>
> does not affect 4.4.0-8
> affects 4.4.0-9 to 4.4.0-22
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-generic 4.4.0.11.12
> ProcVersionSign
> Uname: Linux 4.4.0-8-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Tue Mar 8 09:57:12 2016
> HibernationDevice: RESUME=
> InstallationDate: Installed on 2016-01-07 (61 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0c45:670c Microdia
> Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: Dell Inc. XPS 13 9350
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> RelatedPackageV
> linux-restricte
> linux-backports
> linux-firmware 1.156
> SourcePackage: linux
> UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
> dmi.bios.date: 01/08/2016
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: 1.2.3
> dmi.board.name: 07TYC2
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A01
> dmi.chassis.type: 9
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias: dmi:bvnDellInc.
> dmi.product.name: XPS 13 9350
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https:/
---
Luís Correia
Universidade de Lisboa - Faculdade de Ciências
Departamento de Informática
Campo Grande, 1749-016 ...
Jeremy LaCroix (j-jlacroix) wrote : | #119 |
@Brad, are you using Ubuntu MATE by chance? I've long suspected that the MATE desktop environment (or at least Ubuntu MATE) has its own flickering issue that is not related at all.
Kostadin Stoilov (kmstoilov) wrote : | #120 |
@eugenesan I have the XPS 15 9550 with the latest bios, which is 1.2.0 in my case.
Brad Buran (bburan) wrote : Re: [Bug 1554613] Re: Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU) | #121 |
I'm using Unity.
On Fri, May 13, 2016 at 10:53 AM, Jeremy LaCroix <<email address hidden>
> wrote:
> @Brad, are you using Ubuntu MATE by chance? I've long suspected that the
> MATE desktop environment (or at least Ubuntu MATE) has its own
> flickering issue that is not related at all.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
>
> Status in Linux:
> Fix Released
> Status in linux package in Ubuntu:
> Triaged
>
> Bug description:
>
> *** Temporary workaround ***
> Install Kernel from one of the following locations:
> - http://
> - http://
> ***
>
> Please inspect duplicate reports for more details:
> Bug #1522922
> Bug #1535048
> Bug #1552304
> Bug #1555158
> Bug #1561729
> Bug #1565234
> Bug #1568599
> Bug #1573392
>
> does not affect 4.4.0-8
> affects 4.4.0-9 to 4.4.0-22
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-generic 4.4.0.11.12
> ProcVersionSign
> Uname: Linux 4.4.0-8-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Tue Mar 8 09:57:12 2016
> HibernationDevice: RESUME=
> InstallationDate: Installed on 2016-01-07 (61 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0c45:670c Microdia
> Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> MachineType: Dell Inc. XPS 13 9350
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=
> root=UUID=
> RelatedPackageV
> linux-restricte
> linux-backports
> linux-firmware 1.156
> SourcePackage: linux
> UpgradeStatus: Upgraded to xenial on 2016-02-28 (9 days ago)
> dmi.bios.date: 01/08/2016
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: 1.2.3
> dmi.board.name: 07TYC2
> dmi.board.vendor: Dell Inc.
> dmi.board.version: A01
> dmi.chassis.type: 9
> dmi.chassis.vendor: Dell Inc.
> dmi.modalias:
> dmi:bvnDellInc.
> dmi.product.name: XPS 13 9350
> dmi.sys.vendor: Dell Inc.
>
> To manage notifications about this bug go to:
> https:/
>
Martin Wimpress (flexiondotorg) wrote : | #122 |
I've installed the following Mainline PPA kernel on today's Ubuntu MATE 16.10
* http://
All screen flicker is gone. Just running Ubuntu MATE 16.10, without this kernel upgrade, the flicker was still present.
Martin Wimpress (flexiondotorg) wrote : | #123 |
My system:
Machine: System: Intel (portable) product: SharkBay Platform v: 0.1
Mobo: Topstar model: WhiteTip Mountain1 Fab2 v: Fab2
Bios: American Megatrends v: 5.6.5 date: 03/17/2015
CPU: Dual core Intel Core i3-5010U (-HT-MCP-) cache: 3072 KB
clock speeds: max: 2100 MHz 1: 2000 MHz 2: 2001 MHz 3: 2000 MHz
4: 2000 MHz
Graphics: Card: Intel HD Graphics 5500
Display Server: X.Org 1.18.3 drivers: intel (unloaded: fbdev,vesa)
GLX Renderer: Mesa DRI Intel HD Graphics 5500 (Broadwell GT2)
GLX Version: 3.0 Mesa 11.2.1
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Kostadin Stoilov (kmstoilov) wrote : | #124 |
Amazingly, Bluetooth ON/OFF seems to have an effect on this bug. I have been running with Bluetooth constantly ON for the past couple of days and have seen no flicker at all. As soon as I turn off Bluetooth a flicker occurs after a couple of minutes. I also copied the firmware file from the Windows drivers for the Dell Wireless 1830 card as Bluetooth wasn't finding any devices without it. I am not 100% sure, but I think before adding the bluetooth firmware I got flicker with Bluetooth ON as well. You can get the firmware file from this thread - https:/
I am running an XPS 9550 with an i7-6700HQ.
Romano Giannetti (romano-giannetti) wrote : | #125 |
I had this problem with a Dell desktop; It was especially bad with the second monitor, which blanked out every time it lost focus. I can confirm that
- $ apt-add-repository "deb http://
- $ echo -en "Package: *\nPin: release o=LP-PPA-
- $ apt update
- $ apt install linux-image-
after having created the directory /etc/preferences.d manually, and so upgrading to the yakkety kernel, fixed the issue.
Can anyone please post the instruction to revert this and go back to normal Xenial kernel release when the bug is fixed there? Thanks!
Thiago Martins (martinx) wrote : | #126 |
Still present on latest Xenial... :-(
description: | updated |
Eugene San (eugenesan) wrote : | #127 |
@romano-giannetti and anyone who followed the instructions referenced in https:/
There was a typo in instructions, please read bug description for details and fix.
description: | updated |
Vasya Pupkin (shadowlmd) wrote : | #128 |
I have flickering problem in Chrome on my ASUS UX301LA laptop. The funny thing is that latest kernel (4.6) doesn't fix anything.
Romano Giannetti (romano-giannetti) wrote : | #129 |
@Vasya: seems a different problem. The flickering which this bug is referring to is application-
ArTaX (marco-zannoni) wrote : | #130 |
I want to share my experience: I have a Dell XPS 13 9350 QHD SSD: 512GB RAM: 16GB. Bios 1.3.3.
I installed plain Ubuntu 16.04 erasing all Windows partitions. I did not apply any workaround (I read about this bug).
I do NOT experience this bug.
In the meantime I stambled upon these link, according to which TLP causes screen flickers:
https:/
I don't know if it is the same problem, but you may try to disable/remove TLP.
Alexander Vinbæk Strand (alexstrand7-o) wrote : | #131 |
I have this bug with Ubuntu only.
Linux mint 18 beta cinnamon (based on Ubuntu 16.04) does not have that that problem.
Maybe the Mint team have found a fix that could also be used on Ubuntu.
I don't know if Ubuntu uses different kernel than Mint.
Alexander Vinbæk Strand (alexstrand7-o) wrote : | #132 |
I can help with testing Linux Mint 18 beta on different kernels if you want, so I can see if I get the same problem as Ubuntu with the Intel graphics card, but only if someone can tell me what i should test, and how to do it, because I have never done that before, but I want to find out if there is just the kernel Linux Mint 18 uses that is not affected or there is a fix on Linux Mint that Ubuntu does not have, because if there is a fix, then I think we also can use it on Ubuntu.
Alexander Vinbæk Strand (alexstrand7-o) wrote : | #133 |
Alexander Vinbæk Strand (alexstrand7-o) wrote : | #134 |
Alexander Vinbæk Strand (alexstrand7-o) wrote : | #135 |
Still no problems with Linux Mint 18 beta, and I found out that Linux Mint 18 use the same kernel and driver as Ubuntu 16.04, so why does everything work in Linux Mint 18 Beta when not in Ubuntu 16.04?
I have the same card and I have the same problem with Ubuntu earlier as this bug is for, but after I installed Linux Mint instead of Ubuntu then I can't see any problems with graphics.
I don't know if I can help, but here is some files from my computer with logs and information that I hope can be used to fix the bug in Ubuntu.
Here is the output of:
lsb_release -a
Distributor ID: LinuxMint
Description: Linux Mint 18 Sarah
Release: 18
Codename: sarah
uname -a
Linux alexstrand7-
Kenichi Ito (ken-i54k) wrote : | #136 |
It seems that the screen flicker problem fixed in 4.4.0-24 .
Anyone else?
Environment:
XPS 13 9350
Ubuntu 16.04
kernel 4.4.0-24-generic
Bluetooth off
Giacomo Russo (giako87) wrote : | #137 |
Same environment as in #136, I confirm that there's no flickering anymore.
Eugene San (eugenesan) wrote : | #138 |
Confirming #136.
Environment (on 2 machines):
Machine: XPS 13 9350 FHD Display
Distro: Ubuntu 16.04
Kernel: 4.4.0-24-generic
Bluetooth: off and on
Firmware: 1.3.3 and 1.4.3
DE: Unity and GnomeFlashback
Power: On battery and on AC
Screen: eDP (Built-In) or/and DP1 (External TB3/USBC->HDMI)
Changed in linux (Ubuntu): | |
status: | Triaged → Fix Released |
Kostadin Stoilov (kmstoilov) wrote : | #139 |
I can also confirm #136. Screen flickering has been gone on an XPS 9550 with BIOS 1.2.0 since upgrading to 4.4.0-24-generic.
Thiago Martins (martinx) wrote : | #140 |
I'm on 4.4.0-28-generic (Xenial), problem still here.
A good website to test it, is TradingView:
https:/
Google Chrome window flickers a lot! Especially if you really use the above website, by login in, clicking on its functions, pop-up windows and etc...
Hardware is a Macbook Pro, end-2015.
Anmar Oueja (anmar) wrote : | #141 |
Chrome flickers... but FF doesn't for me. Are you sure it isn't the browser.
On Thu, Jul 7, 2016 at 7:58 PM, Thiago Martins <email address hidden>
wrote:
> I'm on 4.4.0-28-generic (Xenial), problem still here.
>
> A good website to test it, is TradingView:
>
> https:/
>
> Google Chrome window flickers a lot! Especially if you really use the
> above website, by login in, clicking on its functions, pop-up windows
> and etc...
>
> Hardware is a Macbook Pro, end-2015.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1552304).
> https:/
>
> Title:
> Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
>
> Status in Linux:
> Fix Released
> Status in linux package in Ubuntu:
> Fix Released
>
> Bug description:
> *** Temporary workaround ***
> Install Kernel from the following location:
> - http://
>
> OR
> Perform the following:
> - $ apt-add-repository "deb
> http://
> - $ echo -en "Package: *\nPin: release
> o=LP-PPA-
> /etc/apt/
> - $ apt update
> - $ apt install linux-image-
> linux-headers-
> ```
> There was a typo in instructions (/etc/preferences.d should have been
> /etc/apt/
> As result you might have upgraded Linux META packages and therefor you
> won't receive proper upgrades of Xenial native Linux packages (hoping they
> will ever contain the fix).
> I suggest you move
> /etc/preference
> /etc/apt/
> $ apt update
> $ apt install linux-headers-
> linux-tools-
> ```
> ***
>
> Please inspect duplicate reports for more details:
> Bug #1522922
> Bug #1535048
> Bug #1552304
> Bug #1555158
> Bug #1561729
> Bug #1565234
> Bug #1568599
> Bug #1573392
>
> does not affect 4.4.0-8
> affects 4.4.0-9 to 4.4.0-22
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-generic 4.4.0.11.12
> ProcVersionSign
> Uname: Linux 4.4.0-8-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Tue Mar 8 09:57:12 2016
> HibernationDevice: RESUME=
> InstallationDate: Installed on 2016-01-07 (61 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0c45:670c Microdia
> Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
> Bus 001 Device 001: ID 1d6b:0002 Linu...
Thiago Martins (martinx) wrote : | #142 |
Anmar,
I am 100% sure that it is not the browser, please guys, watch this:
https:/
This BUG is not fixed. Or maybe, what I'm seeing here is a different bug.
On Ubuntu 16.10, things looks a little bit better but, Chrome still flickers.
Ubuntu 14.04 is fine. While 16.04 and 16.10 are just terrible.
Anmar Oueja (anmar) wrote : | #143 |
Yikes. In your case it isn't the browser for sure. I read somewhere that
the adaptive brightness control might be a culprit but don't count on that
being true unless confirmed.
On Thu, Oct 6, 2016 at 11:38 AM, Thiago Martins <email address hidden>
wrote:
> Anmar,
>
> I am 100% sure that it is not the browser, please guys, watch this:
>
> https:/
>
> This BUG is not fixed. Or maybe, what I'm seeing here is a different
> bug.
>
> On Ubuntu 16.10, things looks a little bit better but, Chrome still
> flickers.
>
> Ubuntu 14.04 is fine. While 16.04 and 16.10 are just terrible.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1552304).
> https:/
>
> Title:
> Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
>
> Status in Linux:
> Fix Released
> Status in linux package in Ubuntu:
> Fix Released
>
> Bug description:
> *** Temporary workaround ***
> Install Kernel from the following location:
> - http://
>
> OR
> Perform the following:
> - $ apt-add-repository "deb http://
> canonical-
> - $ echo -en "Package: *\nPin: release o=LP-PPA-
> -1\n" >> /etc/apt/
> - $ apt update
> - $ apt install linux-image-
> linux-headers-
> ```
> There was a typo in instructions (/etc/preferences.d should have been
> /etc/apt/
> As result you might have upgraded Linux META packages and therefor you
> won't receive proper upgrades of Xenial native Linux packages (hoping they
> will ever contain the fix).
> I suggest you move /etc/preference
> to /etc/apt/
> $ apt update
> $ apt install linux-headers-
> linux-tools-
> ```
> ***
>
> Please inspect duplicate reports for more details:
> Bug #1522922
> Bug #1535048
> Bug #1552304
> Bug #1555158
> Bug #1561729
> Bug #1565234
> Bug #1568599
> Bug #1573392
>
> does not affect 4.4.0-8
> affects 4.4.0-9 to 4.4.0-22
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-generic 4.4.0.11.12
> ProcVersionSign
> Uname: Linux 4.4.0-8-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Tue Mar 8 09:57:12 2016
> HibernationDevice: RESUME=
> InstallationDate: Installed on 2016-01-07 (61 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0c45:...
Lorenzo Bettini (bettini) wrote : | #144 |
At least for my DELL 3800, current kernel in Ubuntu Xenial, 4.4.0-38.57, fixes the flickering
Sukttarb (n-kb0) wrote : | #145 |
On my Dell XPS 13-9350, I had been running 4.4.0-38.57 for two weeks and continued to experience screen flash while using google-chrome-beta until updating this morning to 54.0.2840.50-1. No more flash. Halleluja!
Anmar Oueja (anmar) wrote : | #146 |
Guys, there is an entry on the Chromium site talking about xorg modesetting
vs intel xorg driver. By installing modesetting module and getting rid of
the intel driver, the flicker was gone completely on Ubuntu 16.04.
https:/
On Thu, Oct 6, 2016 at 10:27 AM, Sukttarb <email address hidden>
wrote:
> On my Dell XPS 13-9350, I had been running 4.4.0-38.57 for two weeks and
> continued to experience screen flash while using google-chrome-beta
> until updating this morning to 54.0.2840.50-1. No more flash. Halleluja!
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1552304).
> https:/
>
> Title:
> Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
>
> Status in Linux:
> Fix Released
> Status in linux package in Ubuntu:
> Fix Released
>
> Bug description:
> *** Temporary workaround ***
> Install Kernel from the following location:
> - http://
>
> OR
> Perform the following:
> - $ apt-add-repository "deb http://
> canonical-
> - $ echo -en "Package: *\nPin: release o=LP-PPA-
> -1\n" >> /etc/apt/
> - $ apt update
> - $ apt install linux-image-
> linux-headers-
> ```
> There was a typo in instructions (/etc/preferences.d should have been
> /etc/apt/
> As result you might have upgraded Linux META packages and therefor you
> won't receive proper upgrades of Xenial native Linux packages (hoping they
> will ever contain the fix).
> I suggest you move /etc/preference
> to /etc/apt/
> $ apt update
> $ apt install linux-headers-
> linux-tools-
> ```
> ***
>
> Please inspect duplicate reports for more details:
> Bug #1522922
> Bug #1535048
> Bug #1552304
> Bug #1555158
> Bug #1561729
> Bug #1565234
> Bug #1568599
> Bug #1573392
>
> does not affect 4.4.0-8
> affects 4.4.0-9 to 4.4.0-22
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-generic 4.4.0.11.12
> ProcVersionSign
> Uname: Linux 4.4.0-8-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Tue Mar 8 09:57:12 2016
> HibernationDevice: RESUME=
> InstallationDate: Installed on 2016-01-07 (61 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64
> (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0c45:670c Microdia
> Bus 001 Device 002: ID...
John Smith (atesting) wrote : | #147 |
I'm having this same issue on a Dell 7537 running Ubuntu 16.10 (kernel 4.8).
The flickering that occurs is a rapid change in the brightness of the screen, in a random, persistently manner (it never stops).
Not so often the screen goes all white and quickly returns to normal.
It's interesting to mention that on Ubuntu 16.04 (kernel 4.4) the bug appears to be fixed, as the flickering does not occur.
Michel-Ekimia (michel.ekimia) wrote : | #148 |
I can happily confirm that this does not occur anymore on Ubuntu 16.04 ( kernel 4.4) .
tags: | removed: kernel-da-key needs-reverse-bisect |
Patrick Gillespie (vermontpoet) wrote : | #149 |
Just started noticing this(?) bug (matches symptoms) on my system 3 or 4 days ago. Using Linux Mint:
System: Host: vtpoet-
Distro: Linux Mint 18.1 Serena
Machine: System: LENOVO (portable) product: 20428 v: Lenovo Yoga 2 11
Mobo: LENOVO model: VIUU4 v: 31900058WIN Bios: LENOVO v: AACN21WW date: 01/30/2015
CPU: Dual core Intel Core i3-4012Y (-HT-MCP-) cache: 3072 KB
clock speeds: max: 1500 MHz 1: 1500 MHz 2: 1500 MHz 3: 1499 MHz 4: 1500 MHz
Graphics: Card: Intel Device 0a1e
Display Server: X.Org 1.18.4 drivers: (unloaded: fbdev,vesa) Resolution: 1366x768@60.00hz
GLX Renderer: Mesa DRI Intel Haswell GLX Version: 3.0 Mesa 12.0.6
Have tried kernels:
4.4x
4.8x
4.10x
4.11x
Doesn't affect TTY.
Mikko Rytkönen (mikko-fractilegames) wrote : | #150 |
Same here. I upgraded from Xubuntu 16.04 to 17.04 maybe a month ago and that finally fixed my screen flickering issue, but it has now returned. I have been seeing it again at least couple of days now.
Running kernel 4.10.0-21-generic on Asus Zenbook laptop with Intel Skylake.
Brad Buran (bburan) wrote : | #151 |
Same here. It appears to have reappeared using the XPS9350.
4.10.0-21-generic. Flickering is intermittent (e.g., once a day) and
goes away if I resize the window I'm currently using.
On Sat, May 27, 2017 at 8:02 AM, Mikko Rytkönen <email address hidden> wrote:
> Same here. I upgraded from Xubuntu 16.04 to 17.04 maybe a month ago and
> that finally fixed my screen flickering issue, but it has now returned.
> I have been seeing it again at least couple of days now.
>
> Running kernel 4.10.0-21-generic on Asus Zenbook laptop with Intel
> Skylake.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
>
> Status in Linux:
> Fix Released
> Status in linux package in Ubuntu:
> Fix Released
>
> Bug description:
> *** Temporary workaround ***
> Install Kernel from the following location:
> - http://
>
> OR
> Perform the following:
> - $ apt-add-repository "deb http://
> - $ echo -en "Package: *\nPin: release o=LP-PPA-
> - $ apt update
> - $ apt install linux-image-
> ```
> There was a typo in instructions (/etc/preferences.d should have been /etc/apt/
> As result you might have upgraded Linux META packages and therefor you won't receive proper upgrades of Xenial native Linux packages (hoping they will ever contain the fix).
> I suggest you move /etc/preference
> $ apt update
> $ apt install linux-headers-
> ```
> ***
>
> Please inspect duplicate reports for more details:
> Bug #1522922
> Bug #1535048
> Bug #1552304
> Bug #1555158
> Bug #1561729
> Bug #1565234
> Bug #1568599
> Bug #1573392
>
> does not affect 4.4.0-8
> affects 4.4.0-9 to 4.4.0-22
>
> ProblemType: Bug
> DistroRelease: Ubuntu 16.04
> Package: linux-image-generic 4.4.0.11.12
> ProcVersionSign
> Uname: Linux 4.4.0-8-generic x86_64
> ApportVersion: 2.20-0ubuntu3
> Architecture: amd64
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
> CurrentDesktop: KDE
> Date: Tue Mar 8 09:57:12 2016
> HibernationDevice: RESUME=
> InstallationDate: Installed on 2016-01-07 (61 days ago)
> InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
> Lsusb:
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 003: ID 0c45:670c Microdia
> Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp.
> Bus 001 Device 001: ID 1d6b:0002 Li...
Anmar Oueja (anmar) wrote : | #152 |
Have you guys tried uninstalling the Intel Xorg driver so you default
to kernel mode settings. That solved a lot of flicker issues for me.
$ sudo dpkg --purge install xserver-
On Tue, May 30, 2017 at 12:02 PM, Brad Buran <email address hidden> wrote:
> Same here. It appears to have reappeared using the XPS9350.
> 4.10.0-21-generic. Flickering is intermittent (e.g., once a day) and
> goes away if I resize the window I'm currently using.
>
> On Sat, May 27, 2017 at 8:02 AM, Mikko Rytkönen <email address hidden> wrote:
>> Same here. I upgraded from Xubuntu 16.04 to 17.04 maybe a month ago and
>> that finally fixed my screen flickering issue, but it has now returned.
>> I have been seeing it again at least couple of days now.
>>
>> Running kernel 4.10.0-21-generic on Asus Zenbook laptop with Intel
>> Skylake.
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https:/
>>
>> Title:
>> Screen flickers on XPS 13 9350/9550 (Intel Skylake/Broadwell GPU)
>>
>> Status in Linux:
>> Fix Released
>> Status in linux package in Ubuntu:
>> Fix Released
>>
>> Bug description:
>> *** Temporary workaround ***
>> Install Kernel from the following location:
>> - http://
>>
>> OR
>> Perform the following:
>> - $ apt-add-repository "deb http://
>> - $ echo -en "Package: *\nPin: release o=LP-PPA-
>> - $ apt update
>> - $ apt install linux-image-
>> ```
>> There was a typo in instructions (/etc/preferences.d should have been /etc/apt/
>> As result you might have upgraded Linux META packages and therefor you won't receive proper upgrades of Xenial native Linux packages (hoping they will ever contain the fix).
>> I suggest you move /etc/preference
>> $ apt update
>> $ apt install linux-headers-
>> ```
>> ***
>>
>> Please inspect duplicate reports for more details:
>> Bug #1522922
>> Bug #1535048
>> Bug #1552304
>> Bug #1555158
>> Bug #1561729
>> Bug #1565234
>> Bug #1568599
>> Bug #1573392
>>
>> does not affect 4.4.0-8
>> affects 4.4.0-9 to 4.4.0-22
>>
>> ProblemType: Bug
>> DistroRelease: Ubuntu 16.04
>> Package: linux-image-generic 4.4.0.11.12
>> ProcVersionSign
>> Uname: Linux 4.4.0-8-generic x86_64
>> ApportVersion: 2.20-0ubuntu3
>> Architecture: amd64
>> AudioDevicesInUse:
>> USER PID ACCESS COMMAND
>> /dev/snd/controlC0: tbonfort 1498 F.... pulseaudio
>> CurrentDesktop: KDE
>> Date: Tue Mar 8 09:57:12 2016
>> HibernationDevice: RESUME=
>> ...
Kẏra (thekyriarchy) wrote : | #153 |
is this the same bug? https:/
cement_head (andorjkiss) wrote : | #154 |
I also am experiencing this bug on 16.04.3 LTS
i7 7500U Kaby Lake HD 620 using Intel Driver.
Gustavo L (gustavo-lapido) wrote : | #155 |
Flickering still going on my Dell Inspiron N4050
Linux N4050 4.10.0-42-generic #46~16.04.1-Ubuntu SMP Mon Dec 4 15:57:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
LSB Version: core-9.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial
*-display
description: VGA compatible controller
product: 2nd Generation Core Processor Family Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@0000:00:02.0
version: 09
width: 64 bits
clock: 33MHz
resources: irq:27 memory:
Thomas Bonfort, thank you for reporting this and helping make Ubuntu better.
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: /wiki.ubuntu. com/Kernel/ MainlineBuilds .
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https:/
If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.
If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: fixed-upstream fixed-upstream- X.Y-rcZ
kernel-
kernel-
Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.
If the mainline kernel does not fix the issue, please add the following tags: bug-exists- upstream bug-exists- upstream- X.Y-rcZ
kernel-
kernel-
Please note, an error to install the kernel does not fit the criteria of kernel- bug-exists- upstream.
Also, you don't need to apport-collect further unless specifically requested to do so.
Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.
Thank you for your understanding.