Skip to contentSkip to conversation

qemuarm hangs

DISCUSSION Gary Thomas 6 participants 9 messages May 11, 2011

lore
Share & tools
lore

Gary Thomas

author
#0 lore raw

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?

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 13 lines · Gary Thomas

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"

Quoted 7 lines

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 <[email protected]>
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 <[email protected]>
Signed-off-by Richard Purdie <[email protected]>

I wondered about compatibility. Have you tried with the older qemu ?

Bruce

Quoted 11 lines

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
_______________________________________________
poky mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/poky

Signature · 2 lines
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"
author
#2 lore raw
Quoted 32 lines · Bruce Ashfield
Quoted 13 lines · Gary Thomas

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"
Quoted 7 lines

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<[email protected]>
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

Quoted 8 lines

[YOCTO #1013] got fixed

(From OE-Core rev: 9b80846152931bed018f33baaaf1ba253e756867)

Signed-off-by Zhai Edwin<[email protected]>
Signed-off-by Richard Purdie<[email protected]>

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.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#3 lore raw
Quoted 42 lines · Gary Thomas
Quoted 32 lines · Bruce Ashfield
Quoted 13 lines · Gary Thomas

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"

Quoted 7 lines

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<[email protected]>
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

Quoted 8 lines

[YOCTO #1013] got fixed

(From OE-Core rev: 9b80846152931bed018f33baaaf1ba253e756867)

Signed-off-by Zhai Edwin<[email protected]>
Signed-off-by Richard Purdie<[email protected]>

I wondered about compatibility. Have you tried with the older qemu ?

Quoted 7 lines

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

Quoted 1 line
#6 lore raw
In reply to Bruce Ashfield
Quoted 32 lines · Bruce Ashfield
Quoted 13 lines · Gary Thomas

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"
Quoted 7 lines

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 <[email protected]>
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

Quoted 8 lines

[YOCTO #1013] got fixed

(From OE-Core rev: 9b80846152931bed018f33baaaf1ba253e756867)

Signed-off-by Zhai Edwin <[email protected]>
Signed-off-by Richard Purdie <[email protected]>

I wondered about compatibility. Have you tried with the older qemu ?

Note that this is the git recipe, not the released version. I've just realised that it should have a DEFAULT_PREFERENCE = "-1" and doesn't though. These git versions used to be great for testing upstream changes before they hit releases but they shouldn't be the default and I suspect this on has slipped to become default due to the PV change.

It is of course a worry if the upstream version is broken but that is a different problem :/.

Cheers,

Richard

#4 lore raw
In reply to Gary Thomas
Quoted 42 lines · Gary Thomas
Quoted 32 lines · Bruce Ashfield
Quoted 13 lines · Gary Thomas

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"
Quoted 7 lines

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<[email protected]>
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

Quoted 8 lines

[YOCTO #1013] got fixed

(From OE-Core rev: 9b80846152931bed018f33baaaf1ba253e756867)

Signed-off-by Zhai Edwin<[email protected]>
Signed-off-by Richard Purdie<[email protected]>

I wondered about compatibility. Have you tried with the older qemu ?

Quoted 7 lines

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.

Several ways:

a) You can redirect the console as Bruce mentions

b) there is an option you can add to the kernel commandline to disable psplash (psplash=false)

c) you can switch the console as you normally would under Linux which triggers psplash to terminate (Something like Crtl+Alt+F2 then Ctrl+Alt +F1 again but I can't remember the exact combination off the top of my head)

Cheers,

Richard

author
#5 lore raw
Quoted 55 lines · Richard Purdie
Quoted 42 lines · Gary Thomas
Quoted 32 lines · Bruce Ashfield
Quoted 13 lines · Gary Thomas

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"
Quoted 7 lines

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<[email protected]>
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

Quoted 8 lines

[YOCTO #1013] got fixed

(From OE-Core rev: 9b80846152931bed018f33baaaf1ba253e756867)

Signed-off-by Zhai Edwin<[email protected]>
Signed-off-by Richard Purdie<[email protected]>

I wondered about compatibility. Have you tried with the older qemu ?

Quoted 7 lines

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.

Several ways:

a) You can redirect the console as Bruce mentions

Quoted 7 lines

b) there is an option you can add to the kernel commandline to disable psplash (psplash=false)

c) you can switch the console as you normally would under Linux which triggers psplash to terminate (Something like Crtl+Alt+F2 then Ctrl+Alt +F1 again but I can't remember the exact combination off the top of my head)

Disabling the psplash screen, I see this error:
Running postinst /etc/rpm-postinsts/gthumb.sh
Failed to load file "/etc/gconf/gconf.xml.defaults/%gconf-tree-pl.xml": Error on line 363 char 9: Element 'dir' was closed, no element is currently open
I think this was a result of an incomplete [previous] startup, so I
tried with a fresh image. This time, it made it all the way to X,
so I guess I was just too impatient (of course, it took almost 8 minutes
to get to X on a 2.4GHz Core-2 Duo!)

I'll continue with my experiment to see how this runs on qemux86

Sorry for the noise. I do think a slight improvement in the runqemu script can help with situations like this. I had to edit the scripts to add the 'psplash=false' kernel option. With the attached patch, you can do it directly:
% SCRIPT_KERNEL_OPT='psplash=false ' runqemu qemuarm

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
scripts/runqemu +1 -1
index a09362c..2c3f6f4 100755
@@ -51,7 +51,7 @@ ROOTFS=""
 LAZY_ROOTFS=""
 SCRIPT_QEMU_OPT=""
 SCRIPT_QEMU_EXTRA_OPT=""
-SCRIPT_KERNEL_OPT=""
+SCRIPT_KERNEL_OPT=${SCRIPT_KERNEL_OPT:-""}
 
 TMPDIR=""
#8 lore raw

Re: Yocto Project text mail archives don't seem to be text

In reply to Bob Cochran

Hi Bob - excellent catch! That's a lot of 8-bit stuff, must be something misconfigured in mailman. I'll check it out.

Quoted 7 lines · Bob Cochran

After gunzipping the archives, the text files don't seem to be text: https://lists.yoctoproject.org/pipermail/yocto/

_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto

Signature · 2 lines
Jeff Osier-Mixon http://jefro.net/blog
Yocto Project Community Manager @Intel http://yoctoproject.org