From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 95095] New: NV46 (G72) Full screen artifacts in Freespace 2 SW OT mod
Date: Sat, 23 Apr 2016 22:28:56 +0000 [thread overview]
Message-ID: <bug-95095-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1169 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95095
Bug ID: 95095
Summary: NV46 (G72) Full screen artifacts in Freespace 2 SW OT
mod
Product: Mesa
Version: git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: issor.oruam-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Hi,
I've seen this problem sometime ago on NV44
and now traced on NV46 (G72)
The GUI and the 3D models become completely corrupted with elements of the GUI
and parts of the model distorted and covering the whole screen.
Looking at the apitrace and errors highlighted by retracer,
I'm not able to judge if it is a mesa problem.
Here is the .trace:
https://drive.google.com/file/d/0B_OFHiIqgpSFampXVVRKYkVzaTQ/view?usp=sharing
Mauro
--
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: 2483 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2016-04-23 22:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-23 22:28 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-95095-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-04-23 22:37 ` [Bug 95095] NV46 (G72) Full screen artifacts in Freespace 2 SW OT mod bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-23 22:47 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-24 13:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-24 18:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-29 13:01 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-29 13:06 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-29 13:49 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-29 15:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:42 ` 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-95095-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.