[poky] qemuarm hangs

[Bruce Ashfield]

On 11-05-11 02:39 PM, Gary Thomas wrote:
> On 05/11/2011 12:34 PM, Bruce Ashfield wrote:
>> On Wed, May 11, 2011 at 2:29 PM, Gary Thomas<gary at mlbassoc.com> wrote:
>>> Building from master, updated earlier today.
>>>
>>> OE Build Configuration:
>>> BB_VERSION = "1.11.0"
>>> METADATA_BRANCH = "my_master"
>>> METADATA_REVISION = "2e4518bf18d977e1249ef7e7cd384df66e7b4801"
>>> TARGET_ARCH = "arm"
>>> TARGET_OS = "linux-gnueabi"
>>> MACHINE = "qemuarm"
>>> DISTRO = "poky"
>>> DISTRO_VERSION = "1.0+snapshot-20110511"
>>> TARGET_FPU = "soft"
>>>
>>> When I runqemu on core-image-sato, it brings up the simulated
>>> video screen and the Yocto splash shows. The progress bar goes
>>> to about 60% and then it just hangs there forever.
>>>
>>> core-image-minimal boots to a login prompt
>>>
>>> Ideas? How can I figure out where it's bombing out?
>>
>> When I saw this go by:
>>
>> commit a2e232e2313ee267076bb8de32a1a604dbebc33b
>> Author: Zhai Edwin<edwin.zhai at intel.com>
>> Date: Tue May 10 14:02:35 2011 +0800
>>
>> qemu: Upgrade qemu git to the latest 0.14 branch
>>
>> Also add missing patch to build qemu-git
>>
>> [YOCTO #1013] got fixed
>>
>> (From OE-Core rev: 9b80846152931bed018f33baaaf1ba253e756867)
>>
>> Signed-off-by: Zhai Edwin<edwin.zhai at intel.com>
>> Signed-off-by: Richard Purdie<richard.purdie at linuxfoundation.org>
>>
>> I wondered about compatibility. Have you tried with the older qemu ?
>
> I believe so. I ran the same test a few days ago and it worked fine.
> I'm trying qemux86 now with this latest tree. After that, I could
> try reverting the change you mention.
>
> Any clues how to get "under the covers" when booting a qemu image?
> Once it brings up the video/splash screen, I'm in the dark as to
> what's going on.

Typically I'd redirect the console to another tty, but you
could use SERIAL_LOGFILE as an option to your qemu launch
to log the tty output to something you can watch while the
splash screen takes over. But I must warn, that I've never
actually used that option with poky :)

Alternately, removing psplash (or disabling it) in your
sato rootfs would get you more information, and let you
know if it is just the graphics causing a problem.

Bruce

>