Comment # 4
on bug 99515
from Mauro Rossi
Hi, the problem has disappeared in the last week, I've seen a series of commits for radeonsi, but could some developer point out what changes have been done, which may have corrected a NULL pointer dereference MAPERR at address 0x0 happening at list_add after a destroy_buffer_locked? 11-27 18:00:55.044 3215 3215 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 addr2list output (when issue was present) utente@utente-MS-7576:~/nougat-x86_kernel_49$ addr2line -Cfe out/target/product/x86_64/symbols/system/lib64/dri/gallium_dri.so 245108 list_add /proc/self/cwd/external/mesa/src/util/list.h:62 5eb80e destroy_buffer_locked /proc/self/cwd/external/mesa/src/gallium/auxiliary/pipebuffer/pb_cache.c:50 248872 pb_destroy /proc/self/cwd/external/mesa/src/gallium/auxiliary/pipebuffer/pb_buffer.h:232 250044 r600_fence_reference /proc/self/cwd/external/mesa/src/gallium/drivers/radeon/r600_pipe_common.c:1072 2f5a8c dri_flush /proc/self/cwd/external/mesa/src/gallium/state_trackers/dri/dri_drawable.c:527 ^C Besides closing this bug, the information is important in order to backport bug corrections in mesa 17.0.x and mesa 13.0.x Mauro
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
