From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 92327] New: Tearing and drm_wait_vblank kernel log spam with reverse PRIME (intel+nouveau)
Date: Wed, 07 Oct 2015 07:22:33 +0000 [thread overview]
Message-ID: <bug-92327-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2037 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92327
Bug ID: 92327
Summary: Tearing and drm_wait_vblank kernel log spam with
reverse PRIME (intel+nouveau)
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: mschiffer+misc-Nyw9WiXk/RKXhJHkyCwd5uTW4wlIGRCZ@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
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. I also see tearing on the nouveau
output.
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)
Software:
* xserver 1.17.2
* xf86-video-intel 2.99.917-476-g4e668dd
* xf86-video-nouveau 1.0.11-31-g1ff13a9
I opened a bug report for the kernel first (see
https://bugzilla.kernel.org/show_bug.cgi?id=105601 ), but was told that this is
a userspace bug.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3327 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-10-07 7:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 7:22 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-92327-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-10-07 8:26 ` [Bug 92327] Tearing and drm_wait_vblank kernel log spam with reverse PRIME (intel+nouveau) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-92327-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.