From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 69029] New: GT218 (NVA8): GPU lockup since kernel 3.11 upgrade
Date: Fri, 06 Sep 2013 11:35:17 +0000 [thread overview]
Message-ID: <bug-69029-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 989 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=69029
Priority: medium
Bug ID: 69029
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: GT218 (NVA8): GPU lockup since kernel 3.11 upgrade
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: fred-ku13qjcBzYesTnJN9+BGXg@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: git
Component: Driver/nouveau
Product: xorg
Created attachment 85322
--> https://bugs.freedesktop.org/attachment.cgi?id=85322&action=edit
one lockup
on openSUSE Factory (nouveau driver 1.0.9, Mesa 9.2), since kernel was updated
from 3.10.1 to 3.11.0 (rc6 or rc7), I'm getting very often GPU lockup when
using Xorg (GNOME Shell).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2393 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:[~2013-09-06 11:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 11:35 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-69029-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-09-06 11:36 ` [Bug 69029] GT218 (NVA8): GPU lockup since kernel 3.11 upgrade bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 12:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-06 16:16 ` [Bug 69029] [NVA8] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-23 19:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-25 13:20 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 7:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-14 16:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-14 16:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-14 20:48 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-28 3:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-28 9:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-22 8:03 ` 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-69029-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.