Created attachment 130445 [details]
On some actions, like opening a new window or dragging it around, the following message is visible in dmesg:
[drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x111, supported mask 0x7400003f
This is always reproduced, but it only occurs when PRIME output slaving is active, and only when actions are executed on the external monitor connected to the Nvidia GPU (rather than the laptop monitor). Additionally, the external monitor must be primary (xrandr --output DP-1-1 --primary).
Distro: Arch Linux x86_64 (testing repo enabled)
Desktop environment: Plasma 5.9.4-1
Laptop model: Clevo P651RA
Display connector: miniDP (nouveau), eDP (Intel)
$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x8c cap: 0xb, Source Output, Sink Output, Sink Offload crtcs: 4 outputs: 2 associated providers: 1 name:Intel
Provider 1: id: 0x66 cap: 0x7, Source Output, Sink Output, Source Offload crtcs: 4 outputs: 3 associated providers: 1 name:nouveau
Based on the type value (i.e. missing DRM_VBLANK_EVENT) and the call trace (perf trace --call-graph=dwarf -e syscalls:sys_enter_ioctl && perf report points to intel_drv.so), I guess that sna_query_vblank in src/sna/sna_dri2.c is responsible for this spew.
(Maybe it is (or it is not) related to bug 92327.)
Author: Chris Wilson <firstname.lastname@example.org>
Date: Sat Mar 25 01:07:07 2017 +0000
sna: Protect against RROutputPrimary being on a slave
RandR allows the Primary output to belong to a slave GPU, i.e. with the
condition that screen->primaryOutput->screen != screen. When we fallback
to using the PrimaryOutput, we therefore have to check that the output
belong to us before treating it as a sna_output.
Reported-by: Peter Wu <email@example.com>
Signed-off-by: Chris Wilson <firstname.lastname@example.org>
Confirmed fixed with 2.99.917-770-gcb6ba2da, thanks!