All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ricardo Ribalda Delgado <ricardo.ribalda@gmail.com>
To: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: update_font_cache intercept: qemu: uncaught target signal 4 (Illegal instruction)
Date: Fri, 16 Sep 2016 12:25:58 +0200	[thread overview]
Message-ID: <CAPybu_2AtV3MX60jVqOiLVrVtHYgN9UvQ+wwmW0azUiUj2gywA@mail.gmail.com> (raw)
In-Reply-To: <CAJTo0LYM0OX4A3512Q1Y7TnmdWuj7ROxGYB+Drr2Dh5T4-urGA@mail.gmail.com>

Hi Ross

That was the issue! thanks

For the record, this fixes the problem for bobcat architecture (at least for me)

QEMU_EXTRAOPTIONS_bobcat-64 = "-cpu Opteron_G3,check=false"


Thanks!

On Thu, Sep 15, 2016 at 6:27 PM, Burton, Ross <ross.burton@intel.com> wrote:
> On 15 September 2016 at 09:34, Ricardo Ribalda Delgado <
> ricardo.ribalda@gmail.com> wrote:
>
>> MACHINE is qt5022, which is:
>>
>> x86_64 + -march=btver1 -mtune=btver1
>>
>
> So the compiler is probably using instructions that qemu doesn't recognise.
>
> If qemu can pretend to be that machine then you can pass the relevant
> options to qemu in your BSP, see the QEMU_EXTRAOPTIONS variable assignments
> in e.g. tune-corei7.inc.  If qemu can't execute target code then you can
> either ignore the messages or extend qemu.bbclass so that it is possible to
> say "qemu doesn't work" in a BSP.
>
> Ross
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel



-- 
Ricardo Ribalda


      reply	other threads:[~2016-09-16 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 15:27 update_font_cache intercept: qemu: uncaught target signal 4 (Illegal instruction) Ricardo Ribalda Delgado
2016-09-13 16:03 ` Burton, Ross
2016-09-15  8:34   ` Ricardo Ribalda Delgado
2016-09-15 16:27     ` Burton, Ross
2016-09-16 10:25       ` Ricardo Ribalda Delgado [this message]

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=CAPybu_2AtV3MX60jVqOiLVrVtHYgN9UvQ+wwmW0azUiUj2gywA@mail.gmail.com \
    --to=ricardo.ribalda@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.