From: Trevor Woerner <trevor.woerner@linaro.org>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: wandboard-dual, master-next, Xorg segfault
Date: Thu, 02 Oct 2014 15:09:16 -0400 [thread overview]
Message-ID: <542DA2DC.4040805@linaro.org> (raw)
Hi,
I haven't been playing with my wandboard-dual in a while, but last night
I built a new image for it and tested. Coincidentally I started by
running whatever was leftover on my CF card, and it ran fine (i.e. I ran
glxgears, etc).
With the new image, however, the Xorg server segfaults very quickly
after starting. Here is what I found in its log file:
[3512951.484] (EE)
Backtrace:
[3512951.484]
(EE)
[3512951.484] (EE) Segmentation fault at address
0xd8
[3512951.484]
(EE)
Fatal server
error:
[3512951.484] (EE) Caught signal 11 (Segmentation fault). Server
aborting
[3512951.484]
(EE)
[3512951.484] (EE)
Has anyone else seen this or have any ideas what I can try?
Best regards,
Trevor
Build Configuration:
BB_VERSION = "1.24.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "openSUSE-project-13.1"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "wandboard-dual"
DISTRO = "poky"
DISTRO_VERSION = "1.7"
TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU = "vfp-neon"
meta
meta-yocto =
"(detachedfrom0389b3b):0389b3b7e8004373320689750ecf877ae5cc6da9"
meta-oe =
"(detachedfrom0d01e1b):0d01e1b72333f49c29d1a27ad844c4cd9f90341c"
meta-fsl-arm =
"(detachedfromda9230e):da9230ee148e192ac8613f587c0f29a73d2da107"
meta-fsl-arm-extra =
"(detachedfrom8f2c0ff):8f2c0ffc973e0ac0e520a6f57d7bbef63e0a4d6a"
meta-fsl-demos =
"contrib/tlwoerner/glive_install_fix:16199439a1cfe4685532954d047c8cfdc1105107"
next reply other threads:[~2014-10-02 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 19:09 Trevor Woerner [this message]
2014-10-02 19:17 ` wandboard-dual, master-next, Xorg segfault John Weber
2014-10-02 19:36 ` Otavio Salvador
2014-10-02 22:06 ` Trevor Woerner
2014-10-02 22:26 ` John Weber
2014-10-03 13:25 ` Trevor Woerner
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=542DA2DC.4040805@linaro.org \
--to=trevor.woerner@linaro.org \
--cc=meta-freescale@yoctoproject.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.