Re: assert fails in s390x TCG

[Claudio Fontana <cfontana@suse.de>]

On 7/28/23 15:45, Claudio Fontana wrote:
> On 7/28/23 15:33, Richard Henderson wrote:
>> On 7/28/23 06:29, Claudio Fontana wrote:
>>> On 7/27/23 19:41, Richard Henderson wrote:
>>>> On 7/21/23 02:08, Claudio Fontana wrote:
>>>>> Thread 3 "qemu-system-s39" received signal SIGABRT, Aborted.
>>>>> [Switching to Thread 0x7ffff53516c0 (LWP 215975)]
>>>>> (gdb) bt
>>>>> #0  0x00007ffff730dabc in __pthread_kill_implementation () at /lib64/libc.so.6
>>>>> #1  0x00007ffff72bc266 in raise () at /lib64/libc.so.6
>>>>> #2  0x00007ffff72a4897 in abort () at /lib64/libc.so.6
>>>>> #3  0x00007ffff76f0eee in  () at /lib64/libglib-2.0.so.0
>>>>> #4  0x00007ffff775649a in g_assertion_message_expr () at /lib64/libglib-2.0.so.0
>>>>> #5  0x0000555555b96134 in page_unlock__debug (pd=0x7ffee8680440) at ../accel/tcg/tb-maint.c:348
>>>>> #6  0x0000555555b962a9 in page_unlock (pd=0x7ffee8680440) at ../accel/tcg/tb-maint.c:397
>>>>> #7  0x0000555555b96580 in tb_unlock_pages (tb=0x7fffefffeb00) at ../accel/tcg/tb-maint.c:483
>>>>> #8  0x0000555555b94698 in cpu_exec_longjmp_cleanup (cpu=0x555556566a30) at ../accel/tcg/cpu-exec.c:556
>>>>
>>>>
>>>> https://patchew.org/QEMU/20230726201330.357175-1-richard.henderson@linaro.org/
>>>>
>>>>
>>>> r~
>>>
>>> Hi Richard,
>>>
>>> I applied your patch, however I still encounter an assert:
>>>
>>> ERROR:../accel/tcg/tb-maint.c:367:assert_no_pages_locked: assertion failed: (g_hash_table_size(ht_pages_locked_debug) == 0)
>>> Bail out! ERROR:../accel/tcg/tb-maint.c:367:assert_no_pages_locked: assertion failed: (g_hash_table_size(ht_pages_locked_debug) == 0)
>>
>> What's the test case?
>>
>>
>> r~
> 
> It is a test environment for building packages, so the guest at the time of the error is running ./configure for the package swig-v4.1.1.tar.gz
> 
> checking build system type... s390x-ibm-linux-gnu^M
> checking host system type... s390x-ibm-linux-gnu^M
> checking for a BSD-compatible install... /usr/bin/install -c^M
> checking whether build environment is sane... [New Thread 0x7ffea3fff6c0 (LWP 116436)]
> [New Thread 0x7ffec14e26c0 (LWP 116437)]
> [New Thread 0x7ffecf73e6c0 (LWP 116438)]
> [New Thread 0x7ffecde2c6c0 (LWP 116439)]
> [New Thread 0x7ffec2beb6c0 (LWP 116440)]
> yes^M
> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p^M
> checking for gawk... gawk^M
> checking whether make sets $(MAKE)... yes^M
> checking whether make supports nested variables... yes^M
> checking for s390x-ibm-linux-gnu-gcc... gcc^M
> checking whether the C compiler works... **
> 
> So I presume we are in:
> 
> AC_PROG_CC
> 


I am rerunning this over and over, and it seems it always aborts there in the same place.

C