Bug 105601 - drm_wait_vblank log spam with reverse PRIME (intel+nouveau)
Summary: drm_wait_vblank log spam with reverse PRIME (intel+nouveau)
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-10-06 21:25 UTC by Matthias Schiffer
Modified: 2015-10-07 07:12 UTC (History)
0 users

See Also:
Kernel Version: 4.2.2
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Matthias Schiffer 2015-10-06 21:25:15 UTC
Setup: I use reverse PRIME with a primary intel and a secondary nouveau card. I have enabled one output on each of the cards. The reverse PRIME (nouveau) output is set as primary output via xrandr.

Whenever there's a DRI user on the reverse PRIME screen, the following message gets written to my kernel log once for each buffer swap:

[drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x7d, supported mask 0x7400003f

Both DRI2 and DRI3 cause this behaviour.

Depending on the exact setup (DRI2/DRI3, different DRI users), I also get slightly different messages:

[drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x15d, supported mask 0x7400003f
[drm:drm_wait_vblank [drm]] *ERROR* Unsupported type value 0x400015d, supported mask 0x7400003f


Hardware:

00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [Quadro NVS 4200M] (rev a1)
Comment 1 Michel Dänzer 2015-10-07 00:23:05 UTC
This is a (xf86-video-nouveau?) userspace bug, it's passing invalid arguments to the DRM_IOCTL_WAIT_VBLANK ioctl.
Comment 2 Matthias Schiffer 2015-10-07 07:12:19 UTC
Thanks for the quick reply, I'll open a bug report there.

Note You need to log in before you can comment on or make changes to this bug.