From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 95031] New: [NVE4] Random GPU lockups
Date: Wed, 20 Apr 2016 07:44:15 +0000 [thread overview]
Message-ID: <bug-95031-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1499 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=95031
Bug ID: 95031
Summary: [NVE4] Random GPU lockups
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: lucasout-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 123085
--> https://bugs.freedesktop.org/attachment.cgi?id=123085&action=edit
nouveau bugs
Having random lockups on a GTX 660 Ti (NVE4), since kernel 4.1 I guess, using
DRI2.
[ 0.267666] nouveau 0000:02:00.0: NVIDIA GK104 (0e4030a2)
[ 0.378583] nouveau 0000:02:00.0: bios: version 80.04.4b.00.1a
[ 0.379302] nouveau 0000:02:00.0: fb: 2048 MiB GDDR5
Now on gentoo ~amd64 using:
sys-kernel/gentoo-sources-4.5.1
x11-base/xorg-server-1.18.3
x11-drivers/xf86-video-nouveau-1.0.12
Also tried Karol Herbst reclocking branch v4
(https://github.com/karolherbst/nouveau/tree/stable_reclocking_kepler_v4),
reclocked to pstate 07 and tried all 3 boost states. All hang sooner or later.
Will continue testing other pstates and boost configurations.
Sometimes the kernel log becomes corrupted, but I managed to get a working log
(attached).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2893 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-20 7:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 7:44 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-95031-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2016-04-20 7:52 ` [Bug 95031] [NVE4] Random GPU lockups bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-20 13:06 ` [Bug 95031] [NVE4] 660 Ti " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-20 20:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-20 20:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 3:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 4:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 6:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 8:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-04-21 17:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-05-26 23:43 ` 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-95031-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.