From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 76605] New: Screen corruption and crashes in bastion on NVS-140M (G86)
Date: Tue, 25 Mar 2014 20:40:13 +0000 [thread overview]
Message-ID: <bug-76605-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1252 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76605
Priority: medium
Bug ID: 76605
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: Screen corruption and crashes in bastion on NVS-140M
(G86)
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: matthias-eXl60zzu3X2b9/CCa1Sigw@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: 10.1
Component: Drivers/DRI/nouveau
Product: Mesa
Created attachment 96381
--> https://bugs.freedesktop.org/attachment.cgi?id=96381&action=edit
dmesg
When I run the game bastion there is screen corruption, and after some time the
computer locks up.
The menu renders OK-ish (with only some flickering corruption). When ingame,
the screen flickers between (mostly) uncorrupted and corrupted at random
intervals. After some time the computer crashes. Before the crash there is a
lot of output in dmesg by nouveau.
I am running archlinux.
Versions:
xorg 1.15.0
mesa 10.1.0
xf86-video-nouveau 1.0.10
nouveau-dri 10.1.0
linux 3.13.7
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2593 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2014-03-25 20:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 20:40 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-76605-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-03-25 20:51 ` [Bug 76605] Screen corruption and crashes in bastion on NVS-140M (G86) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 20:51 ` [Bug 76605] [NV86] Screen corruption and crashes in bastion on NVS-140M bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 22:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 22:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 22:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 22:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 22:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 23:13 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-03-25 23:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-15 14:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-15 14:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:39 ` 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-76605-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.