On 01/19/2017 04:46 PM, Aníbal Limón wrote:
> 
> 
> On 01/16/2017 03:42 PM, Aníbal Limón wrote:
>>
>>
>> On 01/16/2017 10:47 AM, Burton, Ross wrote:
>>> On 16 January 2017 at 16:43, Aníbal Limón <anibal.limon@linux.intel.com>
>>> wrote:
>>>
>>>> It's weird, i'll review it, but i don't imagine what is failing
>>>> gobject-introspection because a qemu upgrade.
>>>>
>>>
>>> The g-i build runs largely inside a qemu-user instance (the crash is inside
>>> qemu).
>>
>> Hi,
>>
>> I got the stack trace, it's an issue in the PPC TCG some patches in
>> upstream looks like could be cause the problem [1][2][3].
>>
>>
>> (gdb) bt
>> #0  0x000000000086e204 in static_code_gen_buffer ()
>> #1  0x000000000040e922 in cpu_tb_exec (itb=<optimized out>,
>> itb=<optimized out>, cpu=0x29864d0) at
>> /home/alimon/repos/poky/build-ppc/tmp/work/x86_64-linux/qemu-native/2.8.0-r0/qemu-2.8.0/cpu-exec.c:164
>> #2  cpu_loop_exec_tb (sc=<optimized out>, tb_exit=<synthetic pointer>,
>> last_tb=<synthetic pointer>, tb=<optimized out>, cpu=0x29864d0) at
>> /home/alimon/repos/poky/build-ppc/tmp/work/x86_64-linux/qemu-native/2.8.0-r0/qemu-2.8.0/cpu-exec.c:544
>> #3  cpu_exec (cpu=cpu@entry=0x29864d0) at
>> /home/alimon/repos/poky/build-ppc/tmp/work/x86_64-linux/qemu-native/2.8.0-r0/qemu-2.8.0/cpu-exec.c:638
>> #4  0x0000000000445fba in cpu_loop (env=env@entry=0x298e750) at
>> /home/alimon/repos/poky/build-ppc/tmp/work/x86_64-linux/qemu-native/2.8.0-r0/qemu-2.8.0/linux-user/main.c:1359
>> #5  0x0000000000448a95 in clone_func (arg=0x7fffffffa910) at
>> /home/alimon/repos/poky/build-ppc/tmp/work/x86_64-linux/qemu-native/2.8.0-r0/qemu-2.8.0/linux-user/syscall.c:6090
>> #6  0x00007ffff6a750a4 in start_thread (arg=0x7ffff7f4d700) at
>> pthread_create.c:309
>> #7  0x00007ffff67aa62d in clone () at
>> ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
>>
>> (gdb) info threds
>>   Id   Target Id         Frame
>>   1    Thread 0x7ffff7fd0780 (LWP 25006) "qemu-ppc"
>> pthread_cond_wait@@GLIBC_2.3.2 () at
>> ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
>>   2    Thread 0x7ffff647e700 (LWP 25010) "qemu-ppc" syscall () at
>> ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
>> * 3    Thread 0x7ffff7f4d700 (LWP 25011) "qemu-ppc" 0x000000000086e204
>> in static_code_gen_buffer ()
>>
>> I'll send an email to the qemu mailing list.
>>
>> Cheers,
>> 	alimon
>>
>> [1]
>> http://git.qemu.org/?p=qemu.git;a=commit;h=bd6fefe71cec5a0c7d2be4ac96307f25db56abf9

This patch caused the issue, i received a email with the patch for fix
this problem from the qemu-ppc ML.

https://lists.gnu.org/archive/html/qemu-ppc/2017-01/msg00413.html

I tested the patch and send again the qemu upgrade to 2.8.0.

Cheers,
	alimon

>> [2]
>> http://git.qemu.org/?p=qemu.git;a=commit;h=ba4a8df83f474be1ba02510f960e5224f29d229c
>> [3]
>> http://git.qemu.org/?p=qemu.git;a=commit;h=4f5d326046fa522010c0a66f1bcaac9068253085
> 
> I can't get a response from qemu people so i will send a minor upgrade
> 2.7.1 while i debug the issue.
> 
> 	alimon
> 
>>
>>>
>>> Ross
>>>
>>
>>
>>
> 
> 
>