skylake Modesetting Driver on X failure

[kenjo]

with the change away from the intel driver to modeset I get a lot of tearing.

This video shows the problem.

https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
And the video capture is done in 240fps so its possible to see what is happening more clearly.

The test video itself is just a short test video with alternating red/green pictures in 60Hz.

What you should see is a somewhat flickering screen but the color should be a consistent orange hue.

there should be no pulsing of colors that is more green then back to more red and so on then something is wrong.

I have attached the video. if you are uncertain how it should look try to play it directly on a TV. that is with the TV own player not with a computer as that has a lot higher probability of not having any issues with vsync and frame updates.
---
.tmp.unity_support_test.0:

ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
BootLog:
 /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
 (K(K
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py'
DistroCodename: yakkety
DistroRelease: Ubuntu 16.10
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 [1462:7976]
 Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] [1002:7300] (rev c8) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
InstallationDate: Installed on 2015-10-18 (281 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
MachineType: MSI MS-7976
Package: xorg-server (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
Tags: yakkety ubuntu regression reproducible compiz-0.9
Uname: Linux 4.7.0-rc7+ x86_64
UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 02/22/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.B0
dmi.board.asset.tag: Default string
dmi.board.name: Z170A GAMING M7 (MS-7976)
dmi.board.vendor: MSI
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
dmi.product.name: MS-7976
dmi.product.version: 1.0
dmi.sys.vendor: MSI
version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.69-1
version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

[Alexander E. Patrakov (patrakov-gmail)]

Please describe what desktop environment and window manager you use, and whether compositing is enabled in the window manager settings.

I am asking because the same bug exists on Haswell in Arch Linux with Marco window manager (in MATE), and is fixable by installing and running compiz.

[kenjo (ken-kenjo)]

The issue is with unity as window manager. I have no idea how to check if compositing is enabled.

[Timo Aaltonen (tjaalton)]

unity implies compositing

install xdiagnose and run 'apport-collect 1605953'

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[kenjo (ken-kenjo)]

apport information

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[N. W. (nw9165-3201)]

Wouldn't it be better to report such things to the upstream developers of xf86-video-modesetting on bugs.freedesktop.org:

https://bugs.freedesktop.org/buglist.cgi?component=Driver%2Fmodesetting&order=changeddate%20DESC%2Cbug_status%2Cpriority%2Cassigned_to%2Cbug_id&product=xorg&query_format=advanced&resolution=---

?

Is Launchpad really the correct place for it?

[Timo Aaltonen (tjaalton)]

It would be good to file upstream, yes. But I've notified upstream about this via irc for now.

[Timo Aaltonen (tjaalton)]

I assume you were running with modesetting and not intel, since the logs are with intel

anyway, I tried it on Broadwell and it doesn't show anything like your google photo video. Some frames do show more red/green but there's no tearing

[kenjo (ken-kenjo)]

yes it's the modsetting module that has the problem. should have mentioned that the log was from after I changed back to old drive.

So the issue is when I run without any xorg.conf file and get the default. when I create a xorg.conf and load the intel driver it works. well I have other issues but this particular one is not present.

But this is so bad it basically is unusable.

[Timo Aaltonen (tjaalton)]

then you need to tell more.. what video player, what settings etc... I tried VLC and Totem, both worked fine on BDW at least

[kenjo (ken-kenjo)]

well it's not just vlc and any special setting. its EVERYTHING!!! noting is synced moving a window playing video in any player. scrolling in browser playing youtube in browser.

EVERYTHING look like shit you can not miss it.

here is another person having the same issue.

https://whirm.eu/posts/fix-for-xorgs-modesetting-driver-tearing/

[Timo Aaltonen (tjaalton)]

So I guess you're not running Ubuntu/Kubuntu but something else? What's the window manager? Could just be a WM bug..

[kenjo (ken-kenjo)]

No I'm running ubuntu with unity. Standard ubuntu desktop.

[Timo Aaltonen (tjaalton)]

And I have the lowest specced Skylake available on a laptop, default desktop and all... things are just fine on that too. I blame your session settings, try with the guest user

[kenjo (ken-kenjo)]

well what settings is there ?? I have no xorg.conf I also deleted the .drirc file. still same.

Now I have a bit of a hard time testing as I switched over to a AMD R9 card and installed amdgpu-pro package. Not sure I can just switch back to intel now and still have a working system.

I know it did not work to switch back when I had a nvida card without reinstalling a lot of packages for intel again. Not sure what the procedure is for switching amd to intel.

gfx on linux sure sucks compared to windows10 :(

[Timo Aaltonen (tjaalton)]

just purge amdgpu-pro and you're done, no need to reinstall anything

but if you don't provide logs without it and xorg.conf, there's not much I can do other than close the bug

[N. W. (nw9165-3201)]

> tjaalton wrote:
>
> there's not much I can do other than close the bug

Closing a confirmed bug which affects several users?

> tjaalton wrote:
>
> if you don't provide logs without it and xorg.conf

What logs do you need exactly?

[Timo Aaltonen (tjaalton)]

closing the bug since the original reporter can't debug this anymore

if you still have this issue with current yak, make sure you have xdiagnose installed and run 'ubuntu-bug xorg-server'