public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Steffen Sledz <sledz@dresearch-fe.de>,
	Christopher Larson <clarson@kergoth.com>,
	Koen Kooi <koen@dominion.thruhere.net>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: fido -> jethro switching problem
Date: Fri, 15 Jan 2016 14:29:35 +0000	[thread overview]
Message-ID: <1452868175.28375.165.camel@linuxfoundation.org> (raw)
In-Reply-To: <56990180.9080407@dresearch-fe.de>

On Fri, 2016-01-15 at 15:26 +0100, Steffen Sledz wrote:
> On 15.01.2016 14:24, Steffen Sledz wrote:
> > And I made another interesting discovery: The exception appears on
> > certain machine types only, e.g with qemuarm it appears, with
> > qemuarm64 or qemux86 not.
> 
> It seems that all machines based on armv5e are affected.

Which is a good data point to have and should help narrow it down.

I know that jethro OE-Core doesn't do this. Its unlikely to be machine
specific if all armv5e including qemuarm are affected. It therefore
sounds like there is something in your distro config related to armv5
is likely the cause...

Cheers,

Richard



      parent reply	other threads:[~2016-01-15 14:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15 12:03 fido -> jethro switching problem Steffen Sledz
2016-01-15 13:06 ` Richard Purdie
2016-01-15 13:24   ` Steffen Sledz
2016-01-15 14:26     ` Steffen Sledz
2016-01-15 14:29       ` Koen Kooi
2016-01-18  8:28         ` Steffen Sledz
2016-01-18  8:41           ` Koen Kooi
2016-01-18 10:10             ` Steffen Sledz
2016-01-18 10:19               ` Koen Kooi
2016-01-18 11:55         ` Steffen Sledz
2016-01-18 12:25           ` Koen Kooi
2016-01-15 14:29       ` Richard Purdie [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=1452868175.28375.165.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=clarson@kergoth.com \
    --cc=koen@dominion.thruhere.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sledz@dresearch-fe.de \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox