Prime synchronization breaks on kernel 5.4.0-9

[Doug McMahon]

Test case:
Optimus hardware
20.04 updated
Install 440 driver
Enable nvidia_drm modeset either thru kernel parameter or a modeprobe.d file.
reboot.

Seen here -
uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset

Linux doug-Lenovo-IdeaPad-Y510P 5.4.0-9-generic #12-Ubuntu SMP Mon Dec 16 22:34:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
 PRIME Synchronization: 0
 PRIME Synchronization: 1
 PRIME Synchronization: 1
[sudo] password for doug:
Y

While same machine, ect. while booting to previous 5.3.0-24 kernel
uname -a && xrandr --verbose |grep PRIME && sudo cat /sys/module/nvidia_drm/parameters/modeset

Linux doug-Lenovo-IdeaPad-Y510P 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
 PRIME Synchronization: 1
 PRIME Synchronization: 1
 PRIME Synchronization: 1
[sudo] password for doug:
Y

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvidia-driver-440 440.44-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sun Jan 12 14:55:34 2020
InstallationDate: Installed on 2019-12-18 (25 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
SourcePackage: nvidia-graphics-drivers-440
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: doug 1680 F.... pulseaudio
 /dev/snd/controlC1: doug 1680 F.... pulseaudio
 /dev/snd/controlC0: doug 1680 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-01-13 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
MachineType: LENOVO 20217
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=35a0dfe1-ac73-4c26-9a62-8e7b3a0838ad ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-9-generic N/A
 linux-backports-modules-5.4.0-9-generic N/A
 linux-firmware 1.184
Tags: focal
Uname: Linux 5.4.0-9-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.sku: LENOVO_BI_IDEAPAD
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO

[Daniel van Vugt (vanvugt)]

Bug 1858709 sounds like it could potentially be related.

[Daniel van Vugt (vanvugt)]

In the previous discussion you said it was kernel 5.4 that had the problem. Which one is it?

https://discourse.ubuntu.com/t/kernel-5-4-0-9-breaks-prime-synchronization/13910

[Doug McMahon (mc3man)]

I didn't directly mention, it was the 4.15 kernel
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752739

[Doug McMahon (mc3man)]

Oops - titled wrong, breaks on the 5.4.0-9 kernel
As far as other bug - if that would suggest this would work on earlier driver, no such luck.

Did as fresh install updated, used the 435 driver.
Same result, prime sync works on the 5.3.x kernel, fails on the current 5.4.x kernel

[Daniel van Vugt (vanvugt)]

Thanks. Sounds like we should be focusing on the kernel then and not waiting for an Nvidia update.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1859357

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

apport information

[Doug McMahon (mc3man)]

Though would like to (re)mention that previously when same symptoms occurred it was fixed via a dkms_nvidia patch *as seen in report posted in comment #4

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This change was made by a bot.

[berglh (berglh)]

See my latest comment here, it should be resolved by the latest packages.

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1857271