From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 100435] New: Nouveau 1.0.14 crashes randomly
Date: Tue, 28 Mar 2017 18:10:37 +0000 [thread overview]
Message-ID: <bug-100435-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1201 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100435
Bug ID: 100435
Summary: Nouveau 1.0.14 crashes randomly
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: skaistis-fOEEimlCFOXk1uMJSBkQmQ@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 130509
--> https://bugs.freedesktop.org/attachment.cgi?id=130509&action=edit
dmesg output
After upgrading to nouveau 1.0.14, I've been experiencing random crashes. It's
happened a couple of times switching desktops in the Gnome shell, but other
times appear to be pretty random. At that point the system is unresponsive and
has to be power-cycled. Downgrading to 1.0.13 stabilizes things.
Attaching dmesg, lspci, and some of the trace information that I was able to
get out of the logs.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2590 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:[~2017-03-28 18:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 18:10 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-100435-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-03-28 18:11 ` [Bug 100435] Nouveau 1.0.14 crashes randomly bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-28 18:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-28 18:15 ` [Bug 100435] [GM107] Kernel 4.10(.6) nouveau_fence_sync -> ... dma_fence_default_wait, null spinlock error bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-03-28 18:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-05 13:51 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:26 ` 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-100435-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.