On 11 September 2017 at 10:28, Robert Yang <liezhi.y...@windriver.com> wrote:
> The qemumips or qemumips64 can't be boot with 512M. > > *Fixed when no QB_MEM is set: > - runqemu qemumips nographic core-image-minimal > [ 0.000000] Call Trace: > [ 0.000000] [<8011c010>] clear_page+0x0/0x128 > [ 0.000000] [<8022b818>] get_page_from_freelist+0xa1c/0xb48 > [ 0.000000] [<8022c00c>] __alloc_pages_nodemask+0xd8/0xf0c > [ 0.000000] [<8022ce58>] __get_free_pages+0x18/0x60 > [ 0.000000] [<80118674>] setup_zero_pages+0x1c/0x98 > [ 0.000000] [<80bd23e4>] mem_init+0x44/0x54 > [ 0.000000] [<80bca964>] start_kernel+0x20c/0x4bc > [ 0.000000] [<80920090>] kernel_entry+0x0/0x40 > [ 0.000000] Code: 00000000 00000000 00000000 <34860f80> cc9e0000 > cc9e0010 cc9e0020 cc9e0030 cc9e0040 > [ 0.000000] > [ 0.000000] ---[ end trace 0000000000000000 ]--- > [ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task! > [ 0.000000] ---[ end Kernel panic - not syncing: Attempted to kill the > idle task! > This only happens after removing the QB_MEM assignment from qemuboot-mips.inc right? It seems to be that handling machine-specific quirks like this should be done in the machine configuration instead of starting to have a maze of special cases in runqemu again... Ross
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
