Bug 1538 - [multilib]: X window doesn't startup in multilib image randomly
Summary: [multilib]: X window doesn't startup in multilib image randomly
Status: RESOLVED WORKSFORME
Alias: None
Product: Meta-yocto
Classification: Build System, Metadata & Runtime
Component: meta-yocto (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 1.2.1
Assignee: Edwin Zhai
QA Contact:
URL:
Whiteboard: works for me. May 10, 2012
: 1519 2354 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-09-28 09:00 UTC by Dongxiao Xu
Modified: 2012-05-10 07:16 UTC (History)
7 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: ---

Attachments
log.do_rootfs (388.53 KB, text/plain)
2011-09-28 09:00 UTC, Dongxiao Xu 		no flags Details
dmesg.log (15.27 KB, text/plain)
2011-09-28 09:00 UTC, Dongxiao Xu 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dongxiao Xu 2011-09-28 09:00:11 UTC 
Created attachment 264 [details]
log.do_rootfs

[Environment]:
--- local.conf ---
BB_NUMBER_THREADS = "8"
PARALLEL_MAKE = "-j 8"
MACHINE ??= "qemux86-64"
DL_DIR ?= "/home/dongxiao/poky/sources"
DISTRO ?= "poky"
PACKAGE_CLASSES ?= "package_rpm"
EXTRA_IMAGE_FEATURES = "debug-tweaks"
USER_CLASSES ?= "image-prelink image-mklibs"
MULTILIB_IMAGE_INSTALL = "lib32-connman"
CONF_VERSION = "1"
require conf/multilib.conf
MULTILIBS = "multilib:lib32"
DEFAULTTUNE_virtclass-multilib-lib32 = "x86"

bitbake core-sato-image

Sometime After doing rootfs and boot the image, we will find system could not boot up to X window and a lot of segmentation fault happens. Also there are prelink warnings in log.rootfs.

Redo the rootfs, the bug may disappear and system can boot into X correctly with everything in demand installed.

Here I attached the log.rootfs and dmesg info in target OS.
Comment 1 Dongxiao Xu 2011-09-28 09:00:44 UTC 
Created attachment 265 [details]
dmesg.log
Comment 2 Dongxiao Xu 2011-09-28 09:03:01 UTC 
This bug happens occasionally. Not sure this is a prelink issue or multilib issue.

I will try to reproduce it by removing image-prelink in local.conf to see if it still exists.
Comment 3 Dongxiao Xu 2011-09-28 17:38:57 UTC 
Mark, do you have quick idea on this one?
Comment 4 Dongxiao Xu 2011-09-28 18:16:10 UTC 
*** Bug 1519 has been marked as a duplicate of this bug. ***
Comment 5 Dongxiao Xu 2011-09-30 00:08:41 UTC 
I tried 30 times of build with/without prelink feature:

 - with prelink: 5/30 failed.
 - w/o  prelink: none failed.

So suppose it is a prelink issue?
Comment 6 Dongxiao Xu 2012-02-07 16:21:28 UTC 
According to my previous testing result, it seems that this is a bug related with prelink. Can Mark help to take this bug over?
Comment 7 Mark Hatle 2012-02-08 06:04:12 UTC 
With all of the changes to the prelinker since 2011-09-30, this issue may be fixed.

Have you retested it recently?

If I can get a reliably way to reproduce it, then we should be able to determine what the cause it.  If you can generate a "good" filesystem, and a "bad" filesystem, then we can run diffs against the ELF data and see if we're getting bad relocation values.
Comment 8 Jiajun Xu 2012-04-20 05:44:19 UTC 
*** Bug 2354 has been marked as a duplicate of this bug. ***
Comment 9 Edwin Zhai 2012-05-10 07:16:23 UTC 
I have tested with prelink enabled for more than 20 times, and found no issue. Maybe the fix for pango help to resolve this bug.(http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=38467c458fdca97a5b0f2aa91de96f81330dc8de)

I mark it as "works for me". We can reopen it if meet it in future.