Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: experiences with images based on current layer heads
Date: Fri, 5 Apr 2013 10:54:32 -0500	[thread overview]
Message-ID: <515EF3B8.5080205@windriver.com> (raw)
In-Reply-To: <CALbNGRS4MTJny0yqf-oYx1S12O-ZETo4g9x+7BuRVh8pbuBW0g@mail.gmail.com>

If you are unable to look into this yourself, can you please file a bug on the 
bugzilla.yoctoproject.org website?  This issue is likely to get more attention 
if there is an active bug with reproducer steps.  (What you have below may be 
enough for someone who understands X and xfce to reproduce it, but I'm not sure.)

(I've very lightly used X under oe-core master, but I've not done anything more 
then xterms myself.)

It would of course be even better if you could figure out a proper test case to 
reproduce this, but that's not required...

--Mark

On 4/4/13 5:29 PM, Andreas Müller wrote:
> On Wed, Apr 3, 2013 at 4:02 PM, Andreas Müller
> <schnitzeltony@googlemail.com> wrote:
>> Hi,
>>
>> when migration of systemd to oe-core turned to unbuildable I decided
>> to freeze my images and stopped further tests. Now that many issues
>> were fixed and we are close to another release I built my standard
>> xfce-based image based on latest layer HEADs. With this I face some
>> issues which I would like to share:
>>
>> 1. X sessions crash with OOM. This is reproducible by opening
>> google-maps with midori and changing to satellite view. In
>> Xorg.0.log.old I see only
>>
>> | (EE)
>> | (EE) Backtrace:
>> | (EE)
>> | (EE) Segmentation fault at address 0x9
>> | (EE) BUG: triggered 'if (inSignalContext)'
>> | (EE) BUG: log.c:502 in LogVMessageVerb()
>> | (EE) Warning: attempting to log data in a signal unsafe manner while
>> in signal context.
>> | Please update to check inSignalContext and/or use
>> LogMessageVerbSigSafe() or ErrorFSigSafe().
>> | The offending log format message is:
>> |
>> | Fatal server error:
>> |
>> | (EE)
>> | (EE) Backtrace:
>> | (EE)
>>
> seems we are not alone [1]
>
> [1] http://www.raspberrypi.org/phpBB3/viewtopic.php?t=38568&p=321298
>
> Andreas
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>




  reply	other threads:[~2013-04-05 16:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-03 14:02 experiences with images based on current layer heads Andreas Müller
2013-04-04 13:25 ` Richard Purdie
2013-04-04 22:29 ` Andreas Müller
2013-04-05 15:54   ` Mark Hatle [this message]
2013-04-06 10:23     ` Andreas Müller
2013-04-16 12:17 ` Andreas Müller
2013-04-16 21:17   ` Richard Purdie

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=515EF3B8.5080205@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox