From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 92438] Segfault in pushbuf_kref when running the android emulator (qemu) on nv50
Date: Fri, 04 Dec 2015 14:41:55 +0000 [thread overview]
Message-ID: <bug-92438-8800-sLUiLtreOJ@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92438-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
[-- Attachment #1.1: Type: text/plain, Size: 939 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92438
--- Comment #36 from Emil Velikov <emil.l.velikov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Gabriele Svelto from comment #35)
> I've updated mesa again and running from the current master I encounter the
> segfault again. This time though this is the only message that pops up in
> the kernel log:
>
> [ 4684.326211] emulator-x86[19034]: segfault at 4 ip 00000000f5f49403 sp
> 00000000ac6fc660 error 4 in libdrm_nouveau.so.2.0.0[f5f46000+7000]
>
> I'm wondering if running a master mesa with a non-master libdrm is supported
> at all.
If it build again given libdrm{,-nouveau} version it should work. Bugs on the
other hand are something that occasionally exist.
Which version (sha) is the above libdrm-nouveau ? Can you disassemble at the
given offset ?
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1842 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2015-12-04 14:41 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 12:59 [Bug 92438] New: Segfault in pushbuf_kref when running the android emulator (qemu) on nv50 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
[not found] ` <bug-92438-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-10-12 13:00 ` [Bug 92438] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-12 17:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-12 20:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-13 6:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-13 7:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-13 7:46 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-13 12:08 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-13 20:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-13 20:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-13 20:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-13 20:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-15 19:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-15 19:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-15 19:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-15 19:42 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-15 19:53 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-16 9:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-21 22:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-24 12:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-30 13:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-30 13:26 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-31 14:15 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-31 15:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-31 16:19 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-31 17:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-31 22:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-10-31 23:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-01 7:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-01 7:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-01 7:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-01 16:52 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-01 21:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-23 5:30 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-23 9:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-23 10:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-11-23 14:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-04 13:10 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-04 14:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-12-04 14:45 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-04 15:24 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-04 15:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-15 4:09 ` [Bug 92438] Segfault in pushbuf_kref on nv50 when rendering from multiple threads bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-09-15 4:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-10 14:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2016-12-11 22:29 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-01-02 7:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:41 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-09-18 20:41 ` 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-92438-8800-sLUiLtreOJ@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.