All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCHv2] qemu: Upgrade to 2.8.0
Date: Thu, 19 Jan 2017 16:46:31 -0600	[thread overview]
Message-ID: <588141C7.2090504@linux.intel.com> (raw)
In-Reply-To: <587D3E59.30206@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2755 bytes --]



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
> [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
>>
> 
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2017-01-19 22:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 16:19 [PATCHv2] qemu: Upgrade to 2.8.0 Aníbal Limón
2017-01-16 16:36 ` Burton, Ross
2017-01-16 16:43   ` Aníbal Limón
2017-01-16 16:47     ` Burton, Ross
2017-01-16 21:42       ` Aníbal Limón
2017-01-17 12:04         ` Alexander Kanavin
2017-01-17 12:15           ` Burton, Ross
2017-01-19 22:46         ` Aníbal Limón [this message]
2017-01-31 21:52           ` Aníbal Limón

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=588141C7.2090504@linux.intel.com \
    --to=anibal.limon@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.