Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1692339 - Assert at src/gallium/drivers/llvmpipe/lp_rast_tri_tmp.h:237 fires
Summary: Assert at src/gallium/drivers/llvmpipe/lp_rast_tri_tmp.h:237 fires
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: mesa
Version: 29
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-25 12:07 UTC by Stephan Bergmann
Modified: 2019-03-25 15:09 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Stephan Bergmann 2019-03-25 12:07:03 UTC
Since switching to GNOME X11 this morning (due to bug 1692279), gnome-shell sporadically crashes for me, always with

> Core was generated by `/usr/bin/gnome-shell'.
> Program terminated with signal SIGABRT, Aborted.
> #0  raise (sig=6) at /usr/src/debug/glibc-2.28-60-g4d7af7815a/sysdeps/unix/sysv/linux/raise.c:50
> 50	  return ret;
> [Current thread is 1 (Thread 0x7fe543fff700 (LWP 2536))]
> (gdb) bt
> #0  0x00007fe572b90ecf in raise (sig=6) at /usr/src/debug/glibc-2.28-60-g4d7af7815a/sysdeps/unix/sysv/linux/raise.c:50
> #1  0x000055c7dee3e253 in dump_gjs_stack_on_signal_handler (signo=6) at /usr/src/debug/gnome-shell-3.30.2-1.fc29.x86_64/src/main.c:345
> #2  0x00007fe572b91030 in <signal handler called> () at /lib64/libpthread.so.0
> #3  0x00007fe5729f053f in __GI_raise (sig=sig@entry=6) at /usr/src/debug/glibc-2.28-60-g4d7af7815a/sysdeps/unix/sysv/linux/raise.c:50
> #4  0x00007fe5729da895 in __GI_abort () at /usr/src/debug/glibc-2.28-60-g4d7af7815a/stdlib/abort.c:79
> #5  0x00007fe55a1fa400 in _debug_assert_fail (expr=expr@entry=0x7fe55aae8f18 "(c[j] >> (int64_t)8) > (int32_t)0xb0000000 && (c[j] >> (int64_t)8) < (int32_t)0x3fffffff", file=file@entry=0x7fe55aae8ee0 "../src/gallium/drivers/llvmpipe/lp_rast_tri_tmp.h", line=line@entry=237, function=function@entry=0x7fe55aae9290 <__func__.20084> "lp_rast_triangle_4") at /usr/src/debug/mesa-18.3.4-1.fc29.x86_64/src/util/u_debug.c:317
> #6  0x00007fe55a2af2d7 in lp_rast_triangle_4 (task=0x55c7e0ba32d8, arg=...) at /usr/src/debug/mesa-18.3.4-1.fc29.x86_64/src/gallium/drivers/llvmpipe/lp_rast_tri_tmp.h:67
> #7  0x00007fe55a2aa685 in do_rasterize_bin (bin=<optimized out>, x=<optimized out>, y=<optimized out>, task=<optimized out>) at /usr/src/debug/mesa-18.3.4-1.fc29.x86_64/src/gallium/drivers/llvmpipe/lp_rast.c:608
> #8  0x00007fe55a2aa685 in rasterize_bin (y=<optimized out>, x=<optimized out>, bin=<optimized out>, task=0x55c7e0ba32d8) at /usr/src/debug/mesa-18.3.4-1.fc29.x86_64/src/gallium/drivers/llvmpipe/lp_rast.c:627
> #9  0x00007fe55a2aa685 in rasterize_scene (task=0x55c7e0ba32d8, scene=0x55c7e0dc6630) at /usr/src/debug/mesa-18.3.4-1.fc29.x86_64/src/gallium/drivers/llvmpipe/lp_rast.c:687
> #10 0x00007fe55a2aa8ea in thread_function (init_data=init_data@entry=0x55c7e0ba32d8) at /usr/src/debug/mesa-18.3.4-1.fc29.x86_64/src/gallium/drivers/llvmpipe/lp_rast.c:828
> #11 0x00007fe55a2aa38b in impl_thrd_routine (p=<optimized out>) at /usr/src/debug/mesa-18.3.4-1.fc29.x86_64/include/c11/threads_posix.h:87
> #12 0x00007fe572b8658e in start_thread (arg=<optimized out>) at /usr/src/debug/glibc-2.28-60-g4d7af7815a/nptl/pthread_create.c:486
> #13 0x00007fe572ab56a3 in clone () at /usr/src/debug/glibc-2.28-60-g4d7af7815a/sysdeps/unix/sysv/linux/x86_64/clone.S:95


mesa-dri-drivers-18.3.4-1.fc29.x86_64

Comment 1 Stephan Bergmann 2019-03-25 15:09:46 UTC
Still happens with update-testing's mesa-dri-drivers-18.3.5-1.fc29.x86_64.  (One way to provoke it appears to be trying to resize a window with the mouse.)


Note You need to log in before you can comment on or make changes to this bug.