PRIME and PRIME Synchronization
Hello, having the same problem of ryanmusante: [code][14307.379496] BUG: scheduling while atomic: kworker/0:0/6131/0x00000000 [14307.379498] Modules linked in: ctr ccm joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_core btrtl btbcm videodev mousedev btintel hid_generic bluetooth media intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iTCO_wdt iTCO_vendor_support kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel nouveau aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_cstate intel_rapl_perf evdev input_leds mac_hid pcspkr psmouse tpm_crb mxm_wmi arc4 i2c_i801 i2c_smbus iwlmvm lpc_ich mac80211 iwlwifi cfg80211 snd_hda_codec_hdmi rfkill r8169 mii rtsx_pci_ms memstick snd_hda_codec_realtek snd_hda_codec_generic mei_me mei i915 snd_hda_intel ttm snd_hda_codec snd_hda_core ie31200_edac intel_gtt i2c_algo_bit edac_core snd_hwdep shpchp snd_soc_rt5640 [14307.379526] battery thermal snd_soc_rl6231 snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm wmi snd_timer elan_i2c snd soundcore i2c_hid ac97_bus video snd_soc_sst_acpi snd_soc_sst_match 8250_dw i2c_designware_platform i2c_designware_core spi_pxa2xx_platform fjes ac tpm_tis tpm_tis_core button tpm sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 fscrypto mbcache sd_mod usbhid hid dm_mod rtsx_pci_sdmmc serio_raw atkbd libps2 ahci libahci libata xhci_pci ehci_pci scsi_mod crc32c_intel xhci_hcd ehci_hcd nvme usbcore rtsx_pci nvme_core usb_common i8042 serio sdhci_acpi sdhci led_class mmc_core nvidia_drm(PO) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm nvidia_uvm(PO) nvidia_modeset(PO) nvidia(PO) [14307.379549] CPU: 0 PID: 6131 Comm: kworker/0:0 Tainted: P W O 4.9.11-1-ARCH #1 [14307.379549] Hardware name: Notebook P65_P67SE /P65_P67SE , BIOS 1.03.01 07/22/2015 [14307.379560] Workqueue: events intel_mmio_flip_work_func [i915] [14307.379561] ffffc90009233bb0 ffffffff81305830 0000000000000000 ffff88022fa180c0 [14307.379563] ffffc90009233bc0 ffffffff810a6b74 ffffc90009233c18 ffffffff816063c8 [14307.379565] ffffffff810976aa 00ffc90009233bf0 ffff88022fa180c0 ffffc90009233c60 [14307.379566] Call Trace: [14307.379568] [<ffffffff81305830>] dump_stack+0x63/0x83 [14307.379570] [<ffffffff810a6b74>] __schedule_bug+0x54/0x70 [14307.379571] [<ffffffff816063c8>] __schedule+0x588/0x6e0 [14307.379572] [<ffffffff810976aa>] ? __queue_work+0x17a/0x490 [14307.379574] [<ffffffff8160655d>] schedule+0x3d/0x90 [14307.379575] [<ffffffff81609318>] schedule_timeout+0x1f8/0x3d0 [14307.379577] [<ffffffff810f0620>] ? del_timer_sync+0x50/0x50 [14307.379579] [<ffffffff8148f0a2>] fence_default_wait+0x1d2/0x260 [14307.379580] [<ffffffff8148e9d0>] ? fence_release+0xa0/0xa0 [14307.379582] [<ffffffffa0ec5548>] nvidia_drm_gem_prime_fence_op_wait+0x28/0x30 [nvidia_drm] [14307.379584] [<ffffffff8148eceb>] fence_wait_timeout+0x3b/0x170 [14307.379586] [<ffffffff8148f9b6>] reservation_object_wait_timeout_rcu+0x1e6/0x2f0 [14307.379595] [<ffffffffa135b8ed>] intel_mmio_flip_work_func+0x8d/0x320 [i915] [14307.379597] [<ffffffff81098ad5>] process_one_work+0x1e5/0x470 [14307.379598] [<ffffffff81098da8>] worker_thread+0x48/0x4e0 [14307.379600] [<ffffffff81098d60>] ? process_one_work+0x470/0x470 [14307.379601] [<ffffffff81098d60>] ? process_one_work+0x470/0x470 [14307.379602] [<ffffffff8109e939>] kthread+0xd9/0xf0 [14307.379603] [<ffffffff8102d752>] ? __switch_to+0x2d2/0x630 [14307.379604] [<ffffffff8109e860>] ? kthread_park+0x60/0x60 [14307.379605] [<ffffffff8160ad55>] ret_from_fork+0x25/0x30 [/code] on: [code]System: Host: singularity Kernel: 4.9.11-1-ARCH x86_64 (64 bit gcc: 6.3.1) Desktop: KDE Plasma 5.9.3 (Qt 5.8.0) Distro: Arch Linux Machine: Device: laptop System: Notebook product: P65_P67SE Mobo: Notebook model: P65_P67SE UEFI: American Megatrends v: 1.03.01 date: 07/22/2015 Battery BAT0: charge: 34.3 Wh 100.0% condition: 34.3/40.7 Wh (84%) model: Notebook BAT status: Full CPU: Quad core Intel Core i7-4720HQ (-HT-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 20761 clock speeds: max: 3600 MHz 1: 2600 MHz 2: 2600 MHz 3: 2600 MHz 4: 2600 MHz 5: 2600 MHz 6: 2844 MHz 7: 2600 MHz 8: 2600 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 Card-2: NVIDIA GM204M [GeForce GTX 970M] bus-ID: 01:00.0 Display Server: N/A drivers: modesetting,nvidia Resolution: 236x41 Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller driver: snd_hda_intel bus-ID: 00:1b.0 Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller driver: snd_hda_intel bus-ID: 00:03.0 Sound: Advanced Linux Sound Architecture v: k4.9.11-1-ARCH Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller driver: r8169 v: 2.3LK-NAPI port: c000 bus-ID: 03:00.1 IF: enp3s0f1 state: down mac: <filter> Card-2: Intel Wireless 3160 driver: iwlwifi bus-ID: 04:00.0 IF: wlp4s0 state: up mac: <filter> Drives: HDD Total Size: 500.1GB (11.9% used) ID-1: /dev/nvme0n1 model: N/A size: 256.1GB ID-2: /dev/sda model: Samsung_SSD_850 size: 500.1GB Partition: ID-1: / size: 59G used: 29G (51%) fs: ext4 dev: /dev/dm-3 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/dm-1 Sensors: System Temperatures: cpu: 56.0C mobo: N/A gpu: 0.0:51C Fan Speeds (in rpm): cpu: N/A Info: Processes: 234 Uptime: 4:27 Memory: 1531.4/7871.5MB Init: systemd Gcc sys: 6.3.1 Client: Shell (bash 4.4.121) inxi: 2.3.8 [/code]
Hello, having the same problem of ryanmusante:

[14307.379496] BUG: scheduling while atomic: kworker/0:0/6131/0x00000000
[14307.379498] Modules linked in: ctr ccm joydev uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 btusb videobuf2_core btrtl btbcm videodev mousedev btintel hid_generic bluetooth media intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel iTCO_wdt iTCO_vendor_support kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel nouveau aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd intel_cstate intel_rapl_perf evdev input_leds mac_hid pcspkr psmouse tpm_crb mxm_wmi arc4 i2c_i801 i2c_smbus iwlmvm lpc_ich mac80211 iwlwifi cfg80211 snd_hda_codec_hdmi rfkill r8169 mii rtsx_pci_ms memstick snd_hda_codec_realtek snd_hda_codec_generic mei_me mei i915 snd_hda_intel ttm snd_hda_codec snd_hda_core ie31200_edac intel_gtt i2c_algo_bit edac_core snd_hwdep shpchp snd_soc_rt5640
[14307.379526] battery thermal snd_soc_rl6231 snd_soc_core snd_compress snd_pcm_dmaengine snd_pcm wmi snd_timer elan_i2c snd soundcore i2c_hid ac97_bus video snd_soc_sst_acpi snd_soc_sst_match 8250_dw i2c_designware_platform i2c_designware_core spi_pxa2xx_platform fjes ac tpm_tis tpm_tis_core button tpm sch_fq_codel ip_tables x_tables ext4 crc16 jbd2 fscrypto mbcache sd_mod usbhid hid dm_mod rtsx_pci_sdmmc serio_raw atkbd libps2 ahci libahci libata xhci_pci ehci_pci scsi_mod crc32c_intel xhci_hcd ehci_hcd nvme usbcore rtsx_pci nvme_core usb_common i8042 serio sdhci_acpi sdhci led_class mmc_core nvidia_drm(PO) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm nvidia_uvm(PO) nvidia_modeset(PO) nvidia(PO)
[14307.379549] CPU: 0 PID: 6131 Comm: kworker/0:0 Tainted: P W O 4.9.11-1-ARCH #1
[14307.379549] Hardware name: Notebook P65_P67SE /P65_P67SE , BIOS 1.03.01 07/22/2015
[14307.379560] Workqueue: events intel_mmio_flip_work_func [i915]
[14307.379561] ffffc90009233bb0 ffffffff81305830 0000000000000000 ffff88022fa180c0
[14307.379563] ffffc90009233bc0 ffffffff810a6b74 ffffc90009233c18 ffffffff816063c8
[14307.379565] ffffffff810976aa 00ffc90009233bf0 ffff88022fa180c0 ffffc90009233c60
[14307.379566] Call Trace:
[14307.379568] [<ffffffff81305830>] dump_stack+0x63/0x83
[14307.379570] [<ffffffff810a6b74>] __schedule_bug+0x54/0x70
[14307.379571] [<ffffffff816063c8>] __schedule+0x588/0x6e0
[14307.379572] [<ffffffff810976aa>] ? __queue_work+0x17a/0x490
[14307.379574] [<ffffffff8160655d>] schedule+0x3d/0x90
[14307.379575] [<ffffffff81609318>] schedule_timeout+0x1f8/0x3d0
[14307.379577] [<ffffffff810f0620>] ? del_timer_sync+0x50/0x50
[14307.379579] [<ffffffff8148f0a2>] fence_default_wait+0x1d2/0x260
[14307.379580] [<ffffffff8148e9d0>] ? fence_release+0xa0/0xa0
[14307.379582] [<ffffffffa0ec5548>] nvidia_drm_gem_prime_fence_op_wait+0x28/0x30 [nvidia_drm]
[14307.379584] [<ffffffff8148eceb>] fence_wait_timeout+0x3b/0x170
[14307.379586] [<ffffffff8148f9b6>] reservation_object_wait_timeout_rcu+0x1e6/0x2f0
[14307.379595] [<ffffffffa135b8ed>] intel_mmio_flip_work_func+0x8d/0x320 [i915]
[14307.379597] [<ffffffff81098ad5>] process_one_work+0x1e5/0x470
[14307.379598] [<ffffffff81098da8>] worker_thread+0x48/0x4e0
[14307.379600] [<ffffffff81098d60>] ? process_one_work+0x470/0x470
[14307.379601] [<ffffffff81098d60>] ? process_one_work+0x470/0x470
[14307.379602] [<ffffffff8109e939>] kthread+0xd9/0xf0
[14307.379603] [<ffffffff8102d752>] ? __switch_to+0x2d2/0x630
[14307.379604] [<ffffffff8109e860>] ? kthread_park+0x60/0x60
[14307.379605] [<ffffffff8160ad55>] ret_from_fork+0x25/0x30



on:

System:    Host: singularity Kernel: 4.9.11-1-ARCH x86_64 (64 bit gcc: 6.3.1)
Desktop: KDE Plasma 5.9.3 (Qt 5.8.0) Distro: Arch Linux
Machine: Device: laptop System: Notebook product: P65_P67SE
Mobo: Notebook model: P65_P67SE UEFI: American Megatrends v: 1.03.01 date: 07/22/2015
Battery BAT0: charge: 34.3 Wh 100.0% condition: 34.3/40.7 Wh (84%) model: Notebook BAT status: Full
CPU: Quad core Intel Core i7-4720HQ (-HT-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 20761
clock speeds: max: 3600 MHz 1: 2600 MHz 2: 2600 MHz 3: 2600 MHz 4: 2600 MHz 5: 2600 MHz 6: 2844 MHz
7: 2600 MHz 8: 2600 MHz
Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0
Card-2: NVIDIA GM204M [GeForce GTX 970M] bus-ID: 01:00.0
Display Server: N/A drivers: modesetting,nvidia Resolution: 236x41
Audio: Card-1 Intel 8 Series/C220 Series High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0
Card-2 Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
driver: snd_hda_intel bus-ID: 00:03.0
Sound: Advanced Linux Sound Architecture v: k4.9.11-1-ARCH
Network: Card-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: c000 bus-ID: 03:00.1
IF: enp3s0f1 state: down mac: <filter>
Card-2: Intel Wireless 3160 driver: iwlwifi bus-ID: 04:00.0
IF: wlp4s0 state: up mac: <filter>
Drives: HDD Total Size: 500.1GB (11.9% used)
ID-1: /dev/nvme0n1 model: N/A size: 256.1GB
ID-2: /dev/sda model: Samsung_SSD_850 size: 500.1GB
Partition: ID-1: / size: 59G used: 29G (51%) fs: ext4 dev: /dev/dm-3
ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/dm-1
Sensors: System Temperatures: cpu: 56.0C mobo: N/A gpu: 0.0:51C
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 234 Uptime: 4:27 Memory: 1531.4/7871.5MB Init: systemd Gcc sys: 6.3.1
Client: Shell (bash 4.4.121) inxi: 2.3.8

Posted 03/09/2017 02:08 PM   
I did three things recently that seems to have fixed this problem: 1. Upgraded to kernel [code]4.9.13[/code] 2. Removed intel driver, SNA, and changed to modesetting intel in /etc/X11/xorg.conf.d/ [code]Section "Device" Identifier "Device0" Driver "modesetting" BusID "PCI:0:2:0" EndSection [/code] 3. added grub commands [code]i915.enable_rc6=0 intel_idle.max_cstate=0[/code]
I did three things recently that seems to have fixed this problem:

1. Upgraded to kernel
4.9.13


2. Removed intel driver, SNA, and changed to modesetting intel in /etc/X11/xorg.conf.d/
Section "Device"
Identifier "Device0"
Driver "modesetting"
BusID "PCI:0:2:0"
EndSection


3. added grub commands
i915.enable_rc6=0 intel_idle.max_cstate=0

Posted 03/09/2017 03:31 PM   
Thanks! I think I will wait for the new realease. How did you find out how to solve it? Happy to know we have a similar machine, also, have you tried to switch between the tty? Do you have tearing issues and funny artifacts (they usually disappear after a bunch of seconds or view update)
Thanks! I think I will wait for the new realease. How did you find out how to solve it?
Happy to know we have a similar machine, also, have you tried to switch between the tty? Do you have tearing issues and funny artifacts (they usually disappear after a bunch of seconds or view update)

Posted 03/10/2017 04:12 PM   
lromor: I spoke too soon. The error is again showing in journalctl. It's infrequent but I believe it has to do with the nvidia driver because I have never seen it with intel or modesetting before switching to PRIME. I will upgrade to 378.13 and test again soon. I highly recommend since it appears you're using Clevo based notebook, get the Premamod BIOS https://biosmods.wordpress.com/ From your information, you're using P67SE, but double check that it's the correct one in the readme https://biosmods.wordpress.com/p6xxse/
lromor:

I spoke too soon. The error is again showing in journalctl. It's infrequent but I believe it has to do with the nvidia driver because I have never seen it with intel or modesetting before switching to PRIME. I will upgrade to 378.13 and test again soon.

I highly recommend since it appears you're using Clevo based notebook, get the Premamod BIOS
https://biosmods.wordpress.com/

From your information, you're using P67SE, but double check that it's the correct one in the readme
https://biosmods.wordpress.com/p6xxse/

Posted 03/11/2017 05:33 AM   
I believe I had the same issue (dmesg reporting a crash with stuff related to intel_mmio_flip_work_func). On Fedora 25, could usually reproduce it by going into "Add a Printer" and scrolling up and down the printers list and opening gedit and selecting/deselecting text. It only happens when Prime Sync is enabled. It's been a while since I last tried Prime Sync, but this was still happening on a 4.9 kernel.
I believe I had the same issue (dmesg reporting a crash with stuff related to intel_mmio_flip_work_func). On Fedora 25, could usually reproduce it by going into "Add a Printer" and scrolling up and down the printers list and opening gedit and selecting/deselecting text. It only happens when Prime Sync is enabled.

It's been a while since I last tried Prime Sync, but this was still happening on a 4.9 kernel.

Posted 03/11/2017 03:16 PM   
thanks for the tip, also: https://www.reddit.com/r/archlinux/comments/5yskgn/recurring_freezes_after_upgrade_to_4101_with/?st=j073fd2c&sh=a8f1ee79
Ubuntu 17.04 now has xserver 1.19.2 if you use this PPA https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging I also modified /etc/modprobe.d/nvidia-graphics-drivers.conf so that modeset = 1 after rebooting, modprobe -c confirms this options nvidia_375_drm modeset=1 This laptop is a thinkpad P50 with M1000M graphics, booted in hybrid mode with two external monitors and the laptop panel, which works out of the box with xubuntu. Kernel is 4.10 But I still have screen tearing on the laptop panel. What should I do?
Ubuntu 17.04 now has xserver 1.19.2 if you use this PPA

https://launchpad.net/~canonical-x/+archive/ubuntu/x-staging


I also modified /etc/modprobe.d/nvidia-graphics-drivers.conf so that modeset = 1

after rebooting, modprobe -c confirms this

options nvidia_375_drm modeset=1

This laptop is a thinkpad P50 with M1000M graphics, booted in hybrid mode with two external monitors and the laptop panel, which works out of the box with xubuntu. Kernel is 4.10

But I still have screen tearing on the laptop panel. What should I do?

Posted 03/13/2017 11:38 AM   
@TimRichardson: On your laptop run: [code] xrandr --verbose[/code] Does it have the following next to your display? [code] PRIME Synchronization: 1[/code]
@TimRichardson:

On your laptop run:
xrandr --verbose


Does it have the following next to your display?
PRIME Synchronization: 1

Posted 03/13/2017 12:48 PM   
@lromor: The link describes a fix to crashing,however in disabling modeset from GRUB, it also disables PRIME synch.
@lromor:

The link describes a fix to crashing,however in disabling modeset from GRUB, it also disables PRIME synch.

Posted 03/13/2017 12:49 PM   
@ryanmusante tim@tim-ThinkPad-P50:/etc/modprobe.d$ xrandr --verbose | grep PRIME PRIME Synchronization: 0 so it's not defaulting to 1. and tim@tim-ThinkPad-P50:/etc/modprobe.d$ xrandr --output eDP-1-1 --set “PRIME Synchronization” 1 xrandr: unrecognized option '1' Try 'xrandr --help' for more information. tim@tim-ThinkPad-P50:/etc/modprobe.d$ ----> however xrandr --output eDP-1-1 --set 'PRIME Synchronization' 1 succeeds in changing that value. But still get tearing. It makes no difference at all.
@ryanmusante
tim@tim-ThinkPad-P50:/etc/modprobe.d$ xrandr --verbose | grep PRIME
PRIME Synchronization: 0

so it's not defaulting to 1.

and
tim@tim-ThinkPad-P50:/etc/modprobe.d$ xrandr --output eDP-1-1 --set “PRIME Synchronization” 1
xrandr: unrecognized option '1'
Try 'xrandr --help' for more information.
tim@tim-ThinkPad-P50:/etc/modprobe.d$

----> however
xrandr --output eDP-1-1 --set 'PRIME Synchronization' 1
succeeds in changing that value. But still get tearing. It makes no difference at all.

Posted 03/13/2017 08:40 PM   
@ryanmusante Yes, the problem is that with the actual state of the driver with modeset=1 378.13-3 I'm not able at all to use the the os. Xorg has huge freezes after the last update and I don't think it's xorg but the kernel since I cannot log into the machine anymore when those crashes happens (or change tty). So I'm forced to disable modeset (and because of that vsync) in order to have a usable machine.
@ryanmusante
Yes, the problem is that with the actual state of the driver with modeset=1 378.13-3
I'm not able at all to use the the os.

Xorg has huge freezes after the last update and I don't think it's xorg but the kernel since I cannot log into the machine anymore when those crashes happens (or change tty).

So I'm forced to disable modeset (and because of that vsync) in order to have a usable machine.

Posted 03/13/2017 11:25 PM   
Please rest assured we are looking into the issue, along with making sure issues like this are caught by test coverage in the future. If you are seeing issues, as you've all mentioned, PRIME Sync can be disabled by setting nvidia-drm modeset=0. It can also be turned off via 'xrandr --output <output> --set "PRIME Synchronization" 0' if you need modeset=1 for reasons other than PRIME Sync. PRIME Sync was explicitly designed to easily disabled (and disabled by default) in part to allow users to work around unforeseen issues. I apologize for any inconvenience caused. As this is a new feature that exercises the driver and the entire stack in new novel ways, it takes time to work out the kinks. Getting sync working involves a dance between the Intel i915 kernel DRM driver, the NVIDIA DRM driver, both X drivers, as well as the X server, and if any piece changes, even outside of our jurisdiction, it has the potential to expose or even create bugs that weren't visible before. This is in contrast to the non-PRIME display pipeline which is mostly self contained. Likewise, PRIME without sync involves a similar dance for telling the iGPU to scan out the shared pixmap, but once set up there doesn't need to be any additional interaction until teardown. With PRIME Sync, every frame involves an explicit exchange between the iGPU and dGPU both in userspace and in the kernel, meaning many more potential points of failure. Until now, not many users have tested it due to the difficulty in getting set up with a self-built X server, and it's apparent that some configurations are coming up with problems. If the problems are affecting you and are interfering with your workflow, I advise opting out. Thank you all for your feedback, it's very helpful in improving stability. Thanks,
Please rest assured we are looking into the issue, along with making sure issues like this are caught by test coverage in the future.

If you are seeing issues, as you've all mentioned, PRIME Sync can be disabled by setting nvidia-drm modeset=0. It can also be turned off via 'xrandr --output <output> --set "PRIME Synchronization" 0' if you need modeset=1 for reasons other than PRIME Sync. PRIME Sync was explicitly designed to easily disabled (and disabled by default) in part to allow users to work around unforeseen issues.

I apologize for any inconvenience caused. As this is a new feature that exercises the driver and the entire stack in new novel ways, it takes time to work out the kinks. Getting sync working involves a dance between the Intel i915 kernel DRM driver, the NVIDIA DRM driver, both X drivers, as well as the X server, and if any piece changes, even outside of our jurisdiction, it has the potential to expose or even create bugs that weren't visible before. This is in contrast to the non-PRIME display pipeline which is mostly self contained. Likewise, PRIME without sync involves a similar dance for telling the iGPU to scan out the shared pixmap, but once set up there doesn't need to be any additional interaction until teardown. With PRIME Sync, every frame involves an explicit exchange between the iGPU and dGPU both in userspace and in the kernel, meaning many more potential points of failure.

Until now, not many users have tested it due to the difficulty in getting set up with a self-built X server, and it's apparent that some configurations are coming up with problems. If the problems are affecting you and are interfering with your workflow, I advise opting out.

Thank you all for your feedback, it's very helpful in improving stability.

Thanks,

Alex Goins
NVIDIA Linux Graphics

Posted 03/13/2017 11:44 PM   
@agoins : I expect that you're looking about my issue too and don't forget me. To have 2 cursors and to have a system which is slow comparing to a system without PRIME (2 minutes to load Wasteland 2 with PRIME and 10s without PRIME) I hesitate to use only the Intel Card and use the Nvidia in a GPU Passthrough with the HDMI Port to play at games ...
@agoins : I expect that you're looking about my issue too and don't forget me. To have 2 cursors and to have a system which is slow comparing to a system without PRIME (2 minutes to load Wasteland 2 with PRIME and 10s without PRIME)

I hesitate to use only the Intel Card and use the Nvidia in a GPU Passthrough with the HDMI Port to play at games ...

Posted 03/14/2017 05:14 AM   
@agoins: I know you've been reading and are aware of the issues and are doing everything to fix them. Thank you for all your work! I do appreciate it!
@agoins: I know you've been reading and are aware of the issues and are doing everything to fix them. Thank you for all your work! I do appreciate it!

Posted 03/14/2017 07:04 AM   
I have an old Thinkpad W520 (quadcore i7 with a 1000M card). Ubuntu 17.04 (64 bit) with xserver 19.2 once again, prime sync default to 0 but on this machine xrandr --output LVDS-1-1 --set "PRIME Synchronization" 1 works as confirmed by xrandr --verbose but there is still screen tearing.
I have an old Thinkpad W520 (quadcore i7 with a 1000M card). Ubuntu 17.04 (64 bit) with xserver 19.2
once again, prime sync default to 0 but on this machine
xrandr --output LVDS-1-1 --set "PRIME Synchronization" 1

works as confirmed by xrandr --verbose
but there is still screen tearing.

Posted 03/14/2017 08:49 AM   
Scroll To Top

Add Reply