page allocation failure
This log indicates that total chunk memory is starved.
<4>[480188.689067 04-22 03:32:58.097] m.lge.launcher2: page allocation failure: order:1, mode:0xd0
<4>[480188.689123 04-22 03:32:58.097] [<c0016960>] (unwind_backtrace+0x0/0x144) from [<c083a788>] (dump_stack+0x20/0x24)
<4>[480188.689148 04-22 03:32:58.097] [<c083a788>] (dump_stack+0x20/0x24) from [<c011ebb4>] (warn_alloc_failed+0xd0/0x110)
<4>[480188.689170 04-22 03:32:58.097] [<c011ebb4>] (warn_alloc_failed+0xd0/0x110) from [<c01218b4>] (__alloc_pages_nodemask+0x5f0/0x828)
<4>[480188.689196 04-22 03:32:58.097] [<c01218b4>] (__alloc_pages_nodemask+0x5f0/0x828) from [<c00755ec>] (copy_process+0xe8/0xf04)
<4>[480188.689218 04-22 03:32:58.097] [<c00755ec>] (copy_process+0xe8/0xf04) from [<c0076534>] (do_fork+0xf0/0x358)
<4>[480188.689235 04-22 03:32:58.097] [<c0076534>] (do_fork+0xf0/0x358) from [<c0012eb4>] (sys_clone+0x3c/0x44)
<4>[480188.689254 04-22 03:32:58.097] [<c0012eb4>] (sys_clone+0x3c/0x44) from [<c000f040>] (ret_fast_syscall+0x0/0x30)
<4>[480188.689266 04-22 03:32:58.097] Mem-info:
<4>[480188.689274 04-22 03:32:58.097] Normal per-cpu:
<4>[480188.689286 04-22 03:32:58.097] CPU 0: hi: 186, btch: 31 usd: 0
<4>[480188.689297 04-22 03:32:58.097] CPU 1: hi: 186, btch: 31 usd: 0
<4>[480188.689343 04-22 03:32:58.097] CPU 2: hi: 186, btch: 31 usd: 0
<4>[480188.689355 04-22 03:32:58.097] CPU 3: hi: 186, btch: 31 usd: 0
<4>[480188.689367 04-22 03:32:58.097] HighMem per-cpu:
<4>[480188.689376 04-22 03:32:58.097] CPU 0: hi: 90, btch: 15 usd: 0
<4>[480188.689385 04-22 03:32:58.097] CPU 1: hi: 90, btch: 15 usd: 0
<4>[480188.689396 04-22 03:32:58.097] CPU 2: hi: 90, btch: 15 usd: 0
<4>[480188.689406 04-22 03:32:58.097] CPU 3: hi: 90, btch: 15 usd: 0
<4>[480188.689422 04-22 03:32:58.097] active_anon:105900 inactive_anon:11988 isolated_anon:5
<4>[480188.689429 04-22 03:32:58.097] active_file:6691 inactive_file:7685 isolated_file:0
<4>[480188.689434 04-22 03:32:58.097] unevictable:916 dirty:17 writeback:2 unstable:0
<4>[480188.689440 04-22 03:32:58.097] free:3538 slab_reclaimable:3458 slab_unreclaimable:6362
<4>[480188.689446 04-22 03:32:58.097] mapped:20938 shmem:12043 pagetables:1854 bounce:0
<4>[480188.689476 04-22 03:32:58.097] Normal free:13700kB min:2756kB low:3444kB high:4132kB active_anon:258628kB inactive_anon:1428kB active_file:17704kB inactive_file:20184kB unevictable:3628kB isolated(anon):20kB isolated(file):0kB present:576520kB mlocked:0kB dirty:60kB writeback:0kB mapped:24640kB shmem:1512kB slab_reclaimable:13832kB slab_unreclaimable:25448kB kernel_stack:4360kB pagetables:7416kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
<4>[480188.689502 04-22 03:32:58.097] lowmem_reserve[]: 0 2426 2426
<4>[480188.689530 04-22 03:32:58.097] HighMem free:452kB min:300kB low:668kB high:1040kB active_anon:164972kB inactive_anon:46524kB active_file:9060kB inactive_file:10556kB unevictable:36kB isolated(anon):0kB isolated(file):0kB present:310552kB mlocked:0kB dirty:8kB writeback:8kB mapped:59112kB shmem:46660kB slab_reclaimable:0kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
<4>[480188.689557 04-22 03:32:58.097] lowmem_reserve[]: 0 0 0
<4>[480188.689572 04-22 03:32:58.097] Normal: 3404*4kB 7*8kB 2*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 13704kB
<4>[480188.689611 04-22 03:32:58.097] HighMem: 136*4kB 5*8kB 0*16kB 0*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 584kB
<4>[480188.689652 04-22 03:32:58.100] 27287 total pagecache pages
lowmemorykiller
The most popular log seen in the kernel log showing that lowmemory log is working.
<6>[480190.602177 04-22 03:33:00.012] lowmemorykiller: send sigkill to 3020 (m.lge.launcher2<zygote>), adj 0, size 6943
<6>[480190.684210 04-22 03:33:00.094] lowmemorykiller: send sigkill to 3033 (gle.android.gms<zygote>), adj 0, size 6812
<6>[480190.685726 04-22 03:33:00.096] lowmemorykiller: send sigkill to 3001 (u.browser.inter<zygote>), adj 0, size 6404
SysRq : Show Blocked State
The watchdog daemon in the userspace triggers this message via /proc/sysrq-trigger.
With this log, the call stack of uninterruptbile process is accessible.
<6>[483676.051211 04-22 04:31:05.461] SysRq : Show Blocked State
<6>[483676.051232 04-22 04:31:05.461] task PC stack pid father
<6>[483676.051251 04-22 04:31:05.461] bbc-pm D c0841ddc 0 36 2 0x00000000
<4>[483676.051310 04-22 04:31:05.461] [<c0841ddc>] (__schedule+0x410/0x890) from [<c08423ac>] (schedule+0x40/0x80)
<4>[483676.051339 04-22 04:31:05.462] [<c08423ac>] (schedule+0x40/0x80) from [<c0067260>] (tegra_bb_emc_dvfs_thread+0x80/0x6ec)
<4>[483676.051368 04-22 04:31:05.462] [<c0067260>] (tegra_bb_emc_dvfs_thread+0x80/0x6ec) from [<c0098530>] (kthread+0xb0/0xbc)
<4>[483676.051396 04-22 04:31:05.462] [<c0098530>] (kthread+0xb0/0xbc) from [<c000fca4>] (kernel_thread_exit+0x0/0x8)
'Core BSP 분석 > 리눅스 커널 핵심 분석' 카테고리의 다른 글
커널패닉 - ext4 파일 시스템 (0) | 2023.05.05 |
---|---|
copy_mm()함수 (0) | 2023.05.05 |
hrtimer_restart, alarm timer (0) | 2023.05.05 |
바인더가 깨질 때의 콜 스택 (0) | 2023.05.05 |
아이노드 오퍼레이션 - ext4 파일 시스템 (0) | 2023.05.05 |