From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91632] Assert in nouveau_pushbuf_data
Date: Mon, 24 Aug 2015 13:55:18 +0000 [thread overview]
Message-ID: <bug-91632-8800-FuFfCfgF9j@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-91632-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1359 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91632
--- Comment #3 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to Allan Sandfeld from comment #2)
> The original qtwebengine bug is at
> https://bugreports.qt.io/browse/QTBUG-41242
>
> One interesting thing I discovered was that using the EGL/GLES mode instead
> of GLX/GL solved the issue. I assume at your level it shouldn't be that
> different. So it could be a difference in how EGL vs GLX acts.
The issue was happening for me with Unigine Heaven run with DRI3 + DRI_PRIME=1.
Then I started running it with vblank_mode=0 and all my problems disappeared. I
haven't checked whether removing vblank_mode=0 would cause the issues to
reappear. I was happy to blame it on the DRI3 boogeyman and moved on (I tend
not to have a good grasp on these types of issues in the first place...
normally I wouldn't touch DRI3 but it really makes nouveau dev quite a bit
easier with a primary non-nvidia adapter since I can load/unload nouveau/nvidia
at will and still have things display on my regular screen).
Not sure how vsync would cause the problems, but I was getting actual shader
traps reported in dmesg. Do you (or whoever is having the issue) have that as
well?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2221 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2015-08-24 13:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 8:26 [Bug 91632] New: Crash in nouveau bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-91632-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-08-14 8:27 ` [Bug 91632] Assert in nouveau_pushbuf_data bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-24 13:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-24 13:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-08-24 13:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2016-06-28 16:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-30 19:07 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-07-30 19:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-02 20:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-02 23:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-03 4:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-08-03 8:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-10 14:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-11 22:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-05-01 12:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:40 ` 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-91632-8800-FuFfCfgF9j@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.