Testing Env: Host: Ubuntu 10.04 LTS Kernel: 2.6.32-21-generic-pae Poky gitinfo(used to build qemu-native): aa416b6133bd55b5ba4d2fb6f5faef274ba511a0 (git.pokylinux.org:poky-wr +yocto-kernel-clean) Qemuarm images (both sato & sdk) from M1 build on autobuilder, http://autobuilder.pokylinux.org/milestone/20100710-1/. When booting qemumips images with the latest images built for M1, kernel reports OOM(out of memory) error. The error does not impact qemu booting. After waiting for a while, I can get login prompt. command to start qemu ###### /home/jxu49/wr/new/poky-wr/build/tmp/sysroots/i686-linux/usr/bin/qemu-system-ppc -kernel /home/jxu49/test/M1-20100710/zImage-2.6.34+r1+git0+63a07cb64ccc3ceae619d3298545d602ab5ecd38-r1-qemuppc-20100710075758.bin -net nic,vlan=0 -net tap,vlan=0,ifname=tap0,script=/home/jxu49/wr/new/poky-wr/scripts/poky-qemu-ifup,downscript=/home/jxu49/wr/new/poky-wr/scripts/poky-qemu-ifdown -cpu 603e -M prep -bios powerpc_rom.bin -hda /home/jxu49/test/M1-20100710/poky-image-sdk-qemuppc-20100710075758.rootfs.ext3 -no-reboot -show-cursor -usb -usbdevice wacom-tablet -nographic --append root=/dev/hda console=ttyS0 console=tty0 ip=192.168.7.2::192.168.7.1:255.255.255.0 mem=64M ###### Qemu error message: ###### EXT3-fs (hda): warning: feature flags set on rev 0 fs, running e2fsck is recommended EXT3-fs (hda): mounted filesystem with writeback data mode VFS: Mounted root (ext3 filesystem) readonly on device 3:0. Freeing unused kernel memory: 184k init kjournald starting. Commit interval 5 seconds EXT3-fs (hda): warning: updating to rev 1 because of new feature flag, running e2fsck is recommended EXT3-fs (hda): using internal journal localedef invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0 Call Trace: [c3b47bf0] [c0008834] show_stack+0x48/0x15c (unreliable) [c3b47c20] [c00882b4] dump_header+0x58/0x150 [c3b47c50] [c008842c] oom_kill_process+0x80/0x130 [c3b47c70] [c0088a54] __out_of_memory+0x118/0x1bc [c3b47cb0] [c0088b6c] out_of_memory+0x74/0x110 [c3b47ce0] [c008c5a8] __alloc_pages_nodemask+0x634/0x644 [c3b47d80] [c008e460] __do_page_cache_readahead+0x134/0x290 [c3b47de0] [c0086154] filemap_fault+0x3cc/0x434 [c3b47e20] [c009e2e0] __do_fault+0x64/0x4ec [c3b47e70] [c0015d00] do_page_fault+0x32c/0x5c4 [c3b47f40] [c001237c] handle_page_fault+0xc/0x80 --- Exception: 401 at 0xff0e350 LR = 0x100225a0 Mem-Info: DMA per-cpu: CPU 0: hi: 18, btch: 3 usd: 2 active_anon:6872 inactive_anon:6879 isolated_anon:0 active_file:0 inactive_file:45 isolated_file:0 unevictable:0 dirty:0 writeback:0 unstable:0 free:252 slab_reclaimable:214 slab_unreclaimable:583 mapped:11 shmem:7 pagetables:62 bounce:0 DMA free:1008kB min:1016kB low:1268kB high:1524kB active_anon:27488kB inactive_anon:27516kB active_file:0kB inactive_file:180kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:65024kB mlocked:0kB dirty:0kB writeback:0kB mapped:44kB shmem:28kB slab_reclaimable:856kB slab_unreclaimable:2332kB kernel_stack:264kB pagetables:248kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:17 all_unreclaimable? no lowmem_reserve[]: 0 0 0 DMA: 0*4kB 0*8kB 1*16kB 1*32kB 1*64kB 1*128kB 1*256kB 1*512kB 0*1024kB 0*2048kB 0*4096kB = 1008kB 52 total pagecache pages 0 pages in swap cache Swap cache stats: add 0, delete 0, find 0/0 Free swap = 0kB Total swap = 0kB 16384 pages RAM 1331 pages reserved 35 pages shared 14739 pages non-shared Out of memory: kill process 1210 (portmap) score 467 or a child Killed process 1210 (portmap) vsz:1868kB, anon-rss:72kB, file-rss:0kB ######
Sorry that I made a mistake, the issue is for qemuppc, not for qemumips. Change the title.
http://git.pokylinux.org/cgit.cgi/poky/commit/?id=bd19169a60d5aaadc278439578d06c8027cfecf3 should fix this (it was occurring on qemumips and qemuppc)
(In reply to comment #2) > http://git.pokylinux.org/cgit.cgi/poky/commit/?id=bd19169a60d5aaadc278439578d06c8027cfecf3 > should fix this (it was occurring on qemumips and qemuppc) Richard, The OOM issue is fixed. But the first time I boot up qemuppc image may cost more than 5 minutes. I am using the weekly build 20100721, http://yoctobuild01.jf.intel.com/build-areas/weekly-release/build/build/tmp/deploy/images/.
First boot speed is a separate issue and locale generation does take a while. I'm going to mark this particular bug as resolved fixed. We can open a new feature enhancement bug with the task of having locale generation at build time.
Mark the bug as verified, it has gone with weekly build 20100721, http://yoctobuild01.jf.intel.com/build-areas/weekly-release/build/build/tmp/deploy/images/.