Bug 512

Summary: Very slow response after login the system on arm real hardware board
Product: [Build System, Metadata & Runtime] Meta-yocto Reporter: Changhui Liu <changhui.liu>
Component: meta-yoctoAssignee: Ke Yu <ke.yu>
Status: RESOLVED OBSOLETE QA Contact:
Severity: major    
Priority: Medium CC: changhui.liu, jessica.zhang, jiajun.xu, kevin.tian, poky.bs.watcher, poky.watcher, richard.purdie, sgw, xianchao.zhang, yi.zhao
Version: 1.0   
Target Milestone: 1.0 M2   
Hardware: Other   
OS: arm   
Whiteboard:
OS type for building Yocto: --- Type of Regression: ---
Verified: Documentation change: ---

Description Changhui Liu 2010-10-27 02:41:59 UTC
I built the rootfs for beagleboard, and tried to boot up the system, after login
the system, the response was very slow, and I can do nothing except waiting.
The latest comments of the source code I used as follows:

commit 74e47d42d60161a3cab97c923e852a42e1ce5940
Author: Richard Purdie <rpurdie@linux.intel.com>
Date: Sat Oct 23 00:56:38 2010 +0100

rm_work.bbclass: Handle case where pseudo directory doesn't exist

Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>

This bug happened on sato and sdk rootfs, minimal rootfs was ok.The workaround for sato and sdk rootfs is remove the file "/etc/rc5.d/S09xserver-nodm".
Comment 1 Changhui Liu 2010-11-03 01:37:53 UTC
Move importance status to major.
Comment 2 Saul Wold 2010-11-03 14:44:21 UTC
It was pointed out that the reason for this is indeed X attempting to start and then timing out because there is no display device. Since the SDK and Sato images are targeted primarily to devices with displays.

A possible fix would to add a check (if possible) for a display device before starting the X server.
Comment 3 Ke Yu 2010-12-08 21:58:04 UTC
Hi Changhui, 

As bunch of graphic package(xserver, mesa, x lib etc) has been upgraded, could you try again to see if this issue still exist?
Comment 4 Yi Zhao 2011-01-04 21:55:06 UTC
With milestone build 20110101 beagleboard image:
http://autobuilder.pokylinux.org/milestone/20110101-1/qemu/qemubeagleboard/

There is no this issue.
Comment 5 Ke Yu 2011-01-04 21:58:21 UTC
This issue is not exist as Yi observed.