From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Sanity Failures - Segfaults in qemu images
Date: Mon, 08 Apr 2013 16:54:04 +0100 [thread overview]
Message-ID: <1365436444.12407.48.camel@ted> (raw)
In-Reply-To: <CAMKF1sp4L_N6NDG8=qeWTu4sewV2O8T9f7Xzt8s7xCBv_9MtjQ@mail.gmail.com>
On Sun, 2013-04-07 at 15:32 -0700, Khem Raj wrote:
> On Sun, Apr 7, 2013 at 1:23 AM, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> http://autobuilder.yoctoproject.org:8011/builders/nightly-x86-64-lsb/builds/87/steps/Running%20Sanity%20Tests/logs/stdio
>
>
> what does complete dmesg output looks like ? I have seen ld.so
> segfaults on real x86_64 hardware but havent narrowed it down since
> it does not seem to bother my testing.
I don't have the full dmesg output however I have put a wealth of info
about this into:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=4216
Basically these do look like "random" segfaults happening any point on
the system and having a variety of effects. The double fault is
particularly worrying as it suggests the problem is kernel or qemu. I've
put a script which tends to reproduce the issue into the bugzilla.
When you say you've seen ld.so faults on real hardware, have you any
more details? Are they happening often? Just ld.so?
I need to know if this is a qemu issue or on real hardware too since the
latter is a release blocker and extremely serious.
Cheers,
Richard
prev parent reply other threads:[~2013-04-08 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-07 8:23 Sanity Failures - Segfaults in qemu images Richard Purdie
2013-04-07 22:32 ` Khem Raj
2013-04-08 15:54 ` 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=1365436444.12407.48.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox