From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 102349] nv4x crashing with plasmashell - gdb log included
Date: Wed, 23 Aug 2017 05:10:37 +0000 [thread overview]
Message-ID: <bug-102349-8800-kyJn7ouHFL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-102349-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 678 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=102349
--- Comment #1 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
Created attachment 133709
--> https://bugs.freedesktop.org/attachment.cgi?id=133709&action=edit
hackpatch
OK, so it looks like a PUSH_RESET happens when there's no bufctx is bound. I
can definitely see how that can happen, unfortunately -- if a context becomes
active and is then deleted, then the screen's pushbuf->user_priv = NULL. Then a
PUSH_RESET comes in, and *boom*. This is a giant hack, but I suspect this patch
could resolve the issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1633 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2017-08-23 5:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 22:11 [Bug 102349] New: nv4x crashing with plasmashell - gdb log included bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-102349-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-08-21 22:12 ` [Bug 102349] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-23 5:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-08-23 21:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-23 21:39 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-24 3:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-24 3:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-24 16:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-03 16:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-23 22:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-29 13:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-07-27 21:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-08-12 22:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-11-02 10:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-27 3:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-27 4:57 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-12-31 5:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-02 22:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-02 22:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-01-03 17:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:30 ` 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-102349-8800-kyJn7ouHFL@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.