All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 76605] [NV86] Screen corruption and crashes in bastion on NVS-140M
Date: Tue, 15 Apr 2014 14:10:22 +0000	[thread overview]
Message-ID: <bug-76605-8800-R3A04qIAdt@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76605-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 505 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=76605

--- Comment #9 from Matthias Blankertz <matthias-eXl60zzu3X2b9/CCa1Sigw@public.gmane.org> ---
As of linux 3.14.1 (mesa version unchanged) the rendering errors in the menu
are gone, the rendering errors in game are still present but the system no
longer crashes.

Attaching new dmesg.

Versions:
xorg 1.15.1
mesa 10.1.0
xf86-video-nouveau 1.0.10
nouveau-dri 10.1.0
linux 3.14.1

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1281 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-04-15 14:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25 20:40 [Bug 76605] New: Screen corruption and crashes in bastion on NVS-140M (G86) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-76605-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-03-25 20:51   ` [Bug 76605] " 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 [this message]
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-R3A04qIAdt@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.