All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rongqing Li <rongqing.li@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] systemd: ignore qemu output, and check its return code
Date: Mon, 5 Aug 2013 13:21:17 +0800	[thread overview]
Message-ID: <51FF364D.3030908@windriver.com> (raw)
In-Reply-To: <CAJTo0LZn5-59UwuM3byj-LgSr8-SxzSqGaLnrzMpEjmR_O2Ayw@mail.gmail.com>



On 07/26/2013 07:53 PM, Burton, Ross wrote:
> On 24 July 2013 07:15, Rongqing Li <rongqing.li@windriver.com> wrote:
>> qemu is not segfaulting, except error message, it returns 0,
>> and udevadm hwdb finished its task.
>
> A bit of googling takes you to
> https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/758424.
> Key quote:
>
> "We only implement the futex syscalls if CONFIG_USE_NPTL. This isn't
> defined for the i386 target (the necessary support in target-i386 for
> pushing atomic insns up to the linux-user top level loop isn't
> implemented). The upshot is that running multithreaded programs in
> linux-user i386-target isn't supported and this is just one of the
> symptoms."
>
> Not segfaulting != working when multithreaded programs don't have
> futexs.  We'll be seeing this more in the future now that GLib assumes
> you can thread.
>
> Ross
>


I see this bug was not fixed from 2011-11, what should I do?

I know my patch works well on my machine.

-Roy



-- 
Best Reagrds,
Roy | RongQing Li


  reply	other threads:[~2013-08-05  5:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  5:24 [PATCH 0/1] systemd: ignore qemu output, and check its return code rongqing.li
2013-07-24  5:24 ` [PATCH 1/1] " rongqing.li
2013-07-24  5:34   ` Khem Raj
2013-07-24  6:15     ` Rongqing Li
2013-07-26 11:53       ` Burton, Ross
2013-08-05  5:21         ` Rongqing Li [this message]
2013-08-07  7:30   ` Rongqing Li
2013-08-07 11:55     ` Burton, Ross
2013-08-08  8:55       ` Rongqing Li
2013-08-08 10:57         ` Burton, Ross
2013-08-07 18:26     ` Khem Raj
2013-08-08  8:53       ` Rongqing Li

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=51FF364D.3030908@windriver.com \
    --to=rongqing.li@windriver.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.