尝试为imx6ul主板移植安卓镜像时内核死机
尝试为imx6ul主板移植安卓镜像时内核死机
提问于 2019-06-14 21:47:11
我正在尝试为恩智浦imx6ul板构建安卓镜像。我从github下载了android_O8.0.0_1.0.0 tar，创建了mx6ul目录，并为imx6ul构建了它。目前恩智浦还不支持imx6ul的安卓系统，所以我自己试着看着sabresd板。
我对android和Linux非常陌生。我按照恩智浦文档创建了映像。生成已成功完成。当我尝试在SD卡上下载并启动时，它给出了以下日志
uuc invoked oom-killer: gfp_mask=0x24200ca(GFP_HIGHUSER_MOVABLE), nodemask=0, order=0, oom_score_adj=0
CPU: 0 PID: 102 Comm: uuc Not tainted 4.9.11+ #1
Hardware name: Freescale i.MX6 UltraLite (Device Tree)
[<8010ed50>] (unwind_backtrace) from [<8010b274>] (show_stack+0x10/0x14)
[<8010b274>] (show_stack) from [<803aea6c>] (dump_stack+0x80/0x9c)
[<803aea6c>] (dump_stack) from [<801feb98>] (dump_header.constprop.4+0x64/0x1a0)
[<801feb98>] (dump_header.constprop.4) from [<801bf2cc>] (oom_kill_process+0x2d0/0x4b4)
[<801bf2cc>] (oom_kill_process) from [<801bf784>] (out_of_memory+0xd8/0x41c)
[<801bf784>] (out_of_memory) from [<801c3d4c>] (__alloc_pages_nodemask+0xb5c/0xbb8)
[<801c3d4c>] (__alloc_pages_nodemask) from [<801d251c>] (shmem_getpage_gfp.constprop.7+0x504/0xa00)
[<801d251c>] (shmem_getpage_gfp.constprop.7) from [<801bb354>] (generic_perform_write+0xb8/0x1a0)
[<801bb354>] (generic_perform_write) from [<801bcb18>] (__generic_file_write_iter+0x100/0x1f0)
[<801bcb18>] (__generic_file_write_iter) from [<801bccfc>] (generic_file_write_iter+0xf4/0x208)
[<801bccfc>] (generic_file_write_iter) from [<80201140>] (__vfs_write+0xbc/0x114)
[<80201140>] (__vfs_write) from [<80201e98>] (vfs_write+0xa0/0x168)
[<80201e98>] (vfs_write) from [<80202bec>] (SyS_write+0x3c/0x90)
[<80202bec>] (SyS_write) from [<801076c0>] (ret_fast_syscall+0x0/0x3c)
Mem-Info:
active_anon:2018 inactive_anon:114206 isolated_anon:0
active_file:0 inactive_file:0 isolated_file:0
unevictable:0 dirty:0 writeback:0 unstable:0
slab_reclaimable:471 slab_unreclaimable:987
mapped:559 shmem:116160 pagetables:12 bounce:0
free:408 free_pcp:40 free_cma:0
Node 0 active_anon:8072kB inactive_anon:456824kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:2236kB dirty:0kB writeback:0kB shmem:464640kB writeback_tmp:0kB unstable:0kB pages_scanned:0 all_unreclaimable? yes
Normal free:1632kB min:1652kB low:2064kB high:2476kB active_anon:8072kB inactive_anon:456824kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:524288kB managed:507900kB mlocked:0kB slab_reclaimable:1884kB slab_unreclaimable:3948kB kernel_stack:544kB pagetables:48kB bounce:0kB free_pcp:160kB local_pcp:160kB free_cma:0kB
lowmem_reserve[]: 0 0 0
Normal: 4*4kB (UE) 4*8kB (UM) 5*16kB (UM) 29*32kB (UM) 9*64kB (U) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB 0*32768kB = 1632kB
116160 total pagecache pages
0 pages in swap cache
Swap cache stats: add 0, delete 0, find 0/0
Free swap = 0kB
Total swap = 0kB
131072 pages RAM
0 pages HighMem/MovableOnly
4097 pages reserved
81920 pages cma reserved
[ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name
[ 102] 0 102 467 316 6 0 0 0 uuc
Out of memory: Kill process 102 (uuc) score 2 or sacrifice child
Killed process 102 (uuc) total-vm:1868kB, anon-rss:132kB, file-rss:4kB, shmem-rss:1128kB
oom_reaper: reaped process 102 (uuc), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
/linuxrc: line 44: 102 Killed uuc
file-storage invoked oom-killer: gfp_mask=0x24002c2(GFP_KERNEL|__GFP_HIGHMEM|__GFP_NOWARN), nodemask=0, order=0, oom_score_adj=0
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00008900
---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00008900
CPU: 0 PID: 82 Comm: file-storage Not tainted 4.9.11+ #1
Hardware name: Freescale i.MX6 UltraLite (Device Tree)
[<8010ed50>] (unwind_backtrace) from [<8010b274>] (show_stack+0x10/0x14)
[<8010b274>] (show_stack) from [<803aea6c>] (dump_stack+0x80/0x9c)
[<803aea6c>] (dump_stack) from [<801feb98>] (dump_header.constprop.4+0x64/0x1a0)
[<801feb98>] (dump_header.constprop.4) from [<801bfa3c>] (out_of_memory+0x390/0x41c)
[<801bfa3c>] (out_of_memory) from [<801c3d4c>] (__alloc_pages_nodemask+0xb5c/0xbb8)
[<801c3d4c>] (__alloc_pages_nodemask) from [<801ef38c>] (__vmalloc_node_range+0xec/0x20c)
[<801ef38c>] (__vmalloc_node_range) from [<801ef73c>] (__vmalloc_node.constprop.13+0x40/0x50)
[<801ef73c>] (__vmalloc_node.constprop.13) from [<801ef7d8>] (vmalloc+0x24/0x34)
[<801ef7d8>] (vmalloc) from [<8058eda4>] (utp_user_data_alloc+0x14/0x60)
[<8058eda4>] (utp_user_data_alloc) from [<80591410>] (fsg_main_thread+0x608/0x22f8)
[<80591410>] (fsg_main_thread) from [<8014a9b4>] (kthread+0xd0/0xf0)
[<8014a9b4>] (kthread) from [<80107778>] (ret_from_fork+0x14/0x3c)
Mem-Info:
active_anon:1948 inactive_anon:114211 isolated_anon:0
active_file:0 inactive_file:0 isolated_file:0
unevictable:0 dirty:0 writeback:0 unstable:0
slab_reclaimable:471 slab_unreclaimable:987
mapped:4 shmem:116160 pagetables:5 bounce:0
free:412 free_pcp:37 free_cma:0uuc正在召唤杀手。正如我在互联网上读到的，这是因为内存耗尽或优化something.Can有人请帮我指出，有什么可能的解决方案，任何帮助都将不胜感激。
谢谢，阿斯玛
回答 1
Stack Overflow用户
发布于 2019-06-25 04:55:40
看起来确实像是调用了OOM杀手。你有没有尝试过创建一个更精简(更小)的Android镜像，或者阻止一些程序在启动时启动？
你可以尝试几个选项：-在启动时禁用Zygote -构建并运行“微型安卓”：$ BUILD_TINY_ANDROID=true make -j4
有关更多想法，请参阅this thread。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/56599517
复制相关文章
相似问题