dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 93301] ns2_linux32: radeon VM fault / VM_CONTEXT1_PROTECTION_FAULT_ADDR
Date: Wed, 09 Dec 2015 10:39:35 +0000	[thread overview]
Message-ID: <bug-93301-502-ID7j5dKE6d@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-93301-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1078 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=93301

--- Comment #10 from Thomas DEBESSE <dev@illwieckz.net> ---
So, I added a gdb backtrace, I guess the interesting part is:

---8<-------------
Thread 31 (Thread 0xe04e8b40 (LWP 26311)):
#0  0xf7fd9be5 in __kernel_vsyscall ()
No symbol table info available.
#1  0xf478025c in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
No symbol table info available.
#2  0xe2e9cabc in radeon_drm_cs_emit_ioctl (param=0x8386300) at
../../../../../../../include/c11/threads_posix.h:159
        ws = 0x8386300
        cs = <optimized out>
        i = <optimized out>
#3  0xe2e9c117 in impl_thrd_routine (p=0x856a708) at
../../../../../../../include/c11/threads_posix.h:87
        pack = {func = 0xe2e9ca60 <radeon_drm_cs_emit_ioctl>, arg = 0x8386300}
#4  0xf477b1aa in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
No symbol table info available.
#5  0xf44b5fde in clone () from /lib/i386-linux-gnu/libc.so.6
------------->8---

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1906 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-12-09 10:39 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  4:10 [Bug 93301] ns2_linux32: radeon VM fault / VM_CONTEXT1_PROTECTION_FAULT_ADDR bugzilla-daemon
2015-12-09  5:48 ` bugzilla-daemon
2015-12-09  5:52 ` bugzilla-daemon
2015-12-09  6:22 ` bugzilla-daemon
2015-12-09  9:21 ` bugzilla-daemon
2015-12-09  9:23 ` bugzilla-daemon
2015-12-09  9:39 ` bugzilla-daemon
2015-12-09  9:44 ` bugzilla-daemon
2015-12-09  9:52 ` bugzilla-daemon
2015-12-09 10:18 ` bugzilla-daemon
2015-12-09 10:37 ` bugzilla-daemon
2015-12-09 10:39 ` bugzilla-daemon [this message]
2015-12-09 12:37 ` [Bug 93301] ns2_linux32: radeon VM fault on Hawaii w/ DCC enabled (+mmap errors) bugzilla-daemon
2015-12-09 12:39 ` [Bug 93301] ns2_linux32: radeon VM fault on Hawaii " bugzilla-daemon
2015-12-09 12:51 ` bugzilla-daemon
2015-12-09 14:18 ` bugzilla-daemon
2015-12-09 14:35 ` bugzilla-daemon
2015-12-09 20:28 ` bugzilla-daemon
2015-12-09 21:05 ` bugzilla-daemon
2015-12-09 21:56 ` bugzilla-daemon
2015-12-10  1:46 ` bugzilla-daemon
2015-12-10  1:47 ` bugzilla-daemon
2015-12-10  1:48 ` bugzilla-daemon
2015-12-10 11:35 ` bugzilla-daemon
2015-12-10 13:01 ` bugzilla-daemon
2015-12-10 14:41 ` bugzilla-daemon
2017-01-14 19:54 ` bugzilla-daemon
2017-01-14 20:25 ` bugzilla-daemon
2017-01-14 22:31 ` bugzilla-daemon
2017-01-14 23:00 ` bugzilla-daemon
2017-01-15  1:59 ` bugzilla-daemon
2017-08-24 21:02 ` bugzilla-daemon
2017-08-25  8:36 ` bugzilla-daemon
2017-10-09 15:34 ` bugzilla-daemon

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-93301-502-ID7j5dKE6d@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).