Bug 4737 - X server fails to start on qemux86-64
Summary: X server fails to start on qemux86-64
Status: VERIFIED FIXED
Alias: None
Product: OE-Core
Classification: Build System, Metadata & Runtime
Component: graphics (show other bugs)
Version: 1.5
Hardware: x86 Multiple
: Medium+ normal
Target Milestone: 1.5 M2
Assignee: Laurentiu Palcu
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2013-06-17 09:54 UTC by Stefan Stanacar
Modified: 2013-06-28 11:32 UTC (History)
4 users (show)

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

Attachments
Xorg.0.log (7.28 KB, text/x-log)
2013-06-17 09:54 UTC, Stefan Stanacar 		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 Stefan Stanacar 2013-06-17 09:54:50 UTC 
Created attachment 1281 [details]
Xorg.0.log

BB_VERSION        = "1.19.1"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Fedora-18"
TARGET_SYS        = "x86_64-poky-linux"
MACHINE           = "qemux86-64"
DISTRO            = "poky"

master:e023620773df82ba1551bec7fb921e4fef01322e


- build core-image-sato qemux86-64
- runqemu
- X doesn't start

From the log:

[1367830.960] (EE) 
[1367830.962] (EE) Backtrace:
[1367830.985] (EE) 0: /usr/bin/Xorg (xorg_backtrace+0x36) [0x572db6]
[1367830.988] (EE) 1: /usr/bin/Xorg (0x400000+0x176839) [0x576839]
[1367830.991] (EE) 2: /lib/libpthread.so.0 (0x7fb5d723f000+0xfb50) [0x7fb5d724eb50]
[1367830.994] (EE) 3: /lib/ld-linux-x86-64.so.2 (0x7fb5d7cf3000+0x14798) [0x7fb5d7d07798]
[1367830.996] (EE) 4: /lib/ld-linux-x86-64.so.2 (0x7fb5d7cf3000+0xa527) [0x7fb5d7cfd527]
[1367830.998] (EE) 5: /lib/ld-linux-x86-64.so.2 (0x7fb5d7cf3000+0xdd75) [0x7fb5d7d00d75]
[1367831.001] (EE) 6: /lib/ld-linux-x86-64.so.2 (0x7fb5d7cf3000+0x141c5) [0x7fb5d7d071c5]
[1367831.002] (EE) 7: /usr/lib/xorg/modules/drivers/vmware_drv.so (0x7fb5d4fb7000+0x4165) [0x7fb5d4fbb165]
[1367831.004] (EE) 8: /usr/bin/Xorg (InitOutput+0x9e2) [0x477122]
[1367831.006] (EE) 9: /usr/bin/Xorg (0x400000+0x25af6) [0x425af6]
[1367831.007] (EE) 10: /lib/libc.so.6 (__libc_start_main+0xf5) [0x7fb5d60b8a35]
[1367831.009] (EE) 11: /usr/bin/Xorg (0x400000+0x25fd1) [0x425fd1]
[1367831.013] (EE) 
[1367831.017] (EE) Segmentation fault at address 0x20e83905
[1367831.020] 
Fatal server error:
[1367831.021] Caught signal 11 (Segmentation fault). Server aborting
[1367831.022]
Comment 1 Laurentiu Palcu 2013-06-17 10:32:06 UTC 
Stefan,

Just gave this one a test and X booted just fine. The commit I tested with (7abcaf14ec9cd760fe94c777f0cd8426163de2c5) is just one above the one mentioned and it does not contain any X related changes. So, I'm expecting that the build on the commit mentioned by you to work as well.
Comment 2 Laurentiu Palcu 2013-06-17 12:09:25 UTC 
It looks like this works if run using kvm but fails if run without it...
Comment 3 Stefan Stanacar 2013-06-17 17:29:05 UTC 
Like Laurentiu said using runqemu with kvm option this doesn't appear and I'm almost certain that this is related to the qemu 1.5 upgrade.

In the first comment my build was a clean one (clean build and no sstate).
I've also did another bitbake core-image-sato build in a older build dir (pre qemu upgrade) where last week I had built an image which booted and started X just fine. Now running runqemu <old image> gave the same exact backtrace when starting X - and this was an rootfs which worked last week - so that's why I'm pretty sure it's the qemu upgrade (because the newer bitbake built another qemu-native).
Comment 4 Laurentiu Palcu 2013-06-18 10:21:32 UTC 
I confirm that qemu upgrade to 1.5.0 is the cause. Just tested now with and without qemu 1.5.0 and it works just fine with the old version.
Comment 5 Laurentiu Palcu 2013-06-20 14:01:12 UTC 
Backported a fix from upstream. Sent it on the ML.
Comment 7 Stefan Stanacar 2013-06-28 11:32:38 UTC 
Verified.