2008-11-10 07:05:10 BF-548 kernel crash
Maha lakshmi (INDIA)
Message: 64922
Hi,
I got the "page allocation failure. order:6, mode:0x40d0" when I tried to launch my application. Please look at the attached file.
The meminfo list the following output.
root:/home/FlashMem> cat /proc/meminfo
MemTotal: 60504 kB
MemFree: 28508 kB
Buffers: 4 kB
Cached: 25236 kB
SwapCached: 0 kB
Active: 12752 kB
Inactive: 12488 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 0 kB
Mapped: 0 kB
Slab: 3292 kB
SReclaimable: 2132 kB
SUnreclaim: 1160 kB
PageTables: 0 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
CommitLimit: 30252 kB
Committed_AS: 0 kB
VmallocTotal: 0 kB
VmallocUsed: 0 kB
VmallocChunk: 0 kB
Please tell me what are the causes for it and how to overcome this?
Thanks,
Maha
root:/home/FlashMem> ./saplayer ../harry.swf
saplayer: page allocation failure. order:6, mode:0x40d0
Hardware Trace:
0 Target : <0x0000476c> { _dump_stack + 0x0 }
Source : <0x0002c94c> { ___alloc_pages + 0x180 }
1 Target : <0x0002c94c> { ___alloc_pages + 0x180 }
Source : <0x0000cdfe> { _printk + 0x16 }
2 Target : <0x0000cdfa> { _printk + 0x12 }
Source : <0x0000ccb0> { _vprintk + 0x1b8 }
3 Target : <0x0000cca4> { _vprintk + 0x1ac }
Source : <0xffa00c82> { __common_int_entry + 0xca }
4 Target : <0xffa00c20> { __common_int_entry + 0x68 }
Source : <0xffa00a60> { _return_from_int + 0x58 }
5 Target : <0xffa00a60> { _return_from_int + 0x58 }
Source : <0xffa00a36> { _return_from_int + 0x2e }
6 Target : <0xffa00a08> { _return_from_int + 0x0 }
Source : <0xffa00c1c> { __common_int_entry + 0x64 }
7 Target : <0xffa00c1a> { __common_int_entry + 0x62 }
Source : <0xffa003a0> { _asm_do_IRQ + 0x68 }
8 Target : <0xffa00398> { _asm_do_IRQ + 0x60 }
Source : <0x00010ebe> { __local_bh_enable + 0x3e }
9 Target : <0x00010e80> { __local_bh_enable + 0x0 }
Source : <0x00010fc8> { ___do_softirq + 0x94 }
10 Target : <0x00010fc0> { ___do_softirq + 0x8c }
Source : <0x00010fa0> { ___do_softirq + 0x6c }
11 Target : <0x00010f94> { ___do_softirq + 0x60 }
Source : <0x000110ac> { _tasklet_action + 0x7c }
12 Target : <0x000110a6> { _tasklet_action + 0x76 }
Source : <0x00011082> { _tasklet_action + 0x52 }
13 Target : <0x00011080> { _tasklet_action + 0x50 }
Source : <0x0001aaa6> { ___rcu_process_callbacks + 0xb6 }
14 Target : <0x0001aaa0> { ___rcu_process_callbacks + 0xb0 }
Source : <0x0001aa36> { ___rcu_process_callbacks + 0x46 }
15 Target : <0x0001aa32> { ___rcu_process_callbacks + 0x42 }
Source : <0x0001aace> { ___rcu_process_callbacks + 0xde }
Stack from 035e1e18:
03dded00 0002c950 00000000 00000001 000040d0 03ddee8c 00000006 000040d0
00000000 0023076c 00000000 000240d0 035e0000 00000000 00000000 00000073
0002ca22 00029000 00029000 020e1f00 00000000 04000021 00000000 00000000
000324fe 00029000 00230768 0003265c 00000001 00000000 008b91a0 04000021
008bb398 0349da80 00029fff 035e1ea0 00000000 00010f94 008b73e4 02d7f558
00003a2c 00000000 00029000 005218a8 035e0000 04000021 00000000 00000003
Call Trace:
[<000039e4>] _sys_mmap2+0x0/0x80
[<00008000>] _bfin_demux_gpio_irq+0x54/0x94
[<00029000>] _wait_on_page_bit+0x48/0x70
[<00029000>] _wait_on_page_bit+0x48/0x70
Mem-info:
DMA per-cpu:
CPU 0: Hot: hi: 18, btch: 3 usd: 17 Cold: hi: 6, btch: 1 usd: 5
Active:2863 inactive:3444 dirty:0 writeback:0 unstable:0
free:468 slab:959 mapped:0 pagetables:0 bounce:0
DMA free:1872kB min:1000kB low:1248kB high:1500kB active:11452kB inactive:13776kB present:62992kB pages_scanned:0 all_unreclolowmem_reserve[]: 0 0
DMA: 126*4kB 49*8kB 11*16kB 3*32kB 7*64kB 0*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB 0*32768kB = B15871 pages of RAM
524 free pages
745 reserved pages
1 pages shared
0 pages swap cached
Allocation of length 167936 from process 311 failed
DMA per-cpu:
CPU 0: Hot: hi: 18, btch: 3 usd: 17 Cold: hi: 6, btch: 1 usd: 5
Active:2863 inactive:3444 dirty:0 writeback:0 unstable:0
free:468 slab:959 mapped:0 pagetables:0 bounce:0
DMA free:1872kB min:1000kB low:1248kB high:1500kB active:11452kB inactive:13776kB present:62992kB pages_scanned:0 all_unreclolowmem_reserve[]: 0 0
DMA: 126*4kB 49*8kB 11*16kB 3*32kB 7*64kB 0*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB 0*32768kB = Bsaplayer: page allocation failure. order:6, mode:0x40d0
Hardware Trace:
0 Target : <0x0000476c> { _dump_stack + 0x0 }
Source : <0x0002c94c> { ___alloc_pages + 0x180 }
1 Target : <0x0002c94c> { ___alloc_pages + 0x180 }
Source : <0x0000cdfe> { _printk + 0x16 }
2 Target : <0x0000cdfa> { _printk + 0x12 }
Source : <0x0000ccb0> { _vprintk + 0x1b8 }
3 Target : <0x0000cca4> { _vprintk + 0x1ac }
Source : <0xffa00c82> { __common_int_entry + 0xca }
4 Target : <0xffa00c20> { __common_int_entry + 0x68 }
Source : <0xffa00a60> { _return_from_int + 0x58 }
5 Target : <0xffa00a60> { _return_from_int + 0x58 }
Source : <0xffa00a36> { _return_from_int + 0x2e }
6 Target : <0xffa00a08> { _return_from_int + 0x0 }
Source : <0xffa00c1c> { __common_int_entry + 0x64 }
7 Target : <0xffa00c1a> { __common_int_entry + 0x62 }
Source : <0xffa003a0> { _asm_do_IRQ + 0x68 }
8 Target : <0xffa00398> { _asm_do_IRQ + 0x60 }
Source : <0x00010ebe> { __local_bh_enable + 0x3e }
9 Target : <0x00010e80> { __local_bh_enable + 0x0 }
Source : <0x00010fc8> { ___do_softirq + 0x94 }
10 Target : <0x00010fc0> { ___do_softirq + 0x8c }
Source : <0x00010fa0> { ___do_softirq + 0x6c }
11 Target : <0x00010f94> { ___do_softirq + 0x60 }
Source : <0x000110ac> { _tasklet_action + 0x7c }
12 Target : <0x000110a6> { _tasklet_action + 0x76 }
Source : <0x00011082> { _tasklet_action + 0x52 }
13 Target : <0x00011080> { _tasklet_action + 0x50 }
Source : <0x0001aaa6> { ___rcu_process_callbacks + 0xb6 }
14 Target : <0x0001aaa0> { ___rcu_process_callbacks + 0xb0 }
Source : <0x0001aa36> { ___rcu_process_callbacks + 0x46 }
15 Target : <0x0001aa32> { ___rcu_process_callbacks + 0x42 }
Source : <0x0001aace> { ___rcu_process_callbacks + 0xde }
Stack from 035e1e18:
03dded00 0002c950 00000000 00000001 000040d0 03ddee8c 00000006 000040d0
00000000 0023076c 00000000 000240d0 035e0000 00000000 00000000 00000073
0002ca22 00029000 00029000 020e1f00 00000000 04000021 00000000 00000000
000324fe 00029000 00230768 0003265c 00000001 00029000 00000137 04000021
008bb398 0349da80 00029fff 035e1ea0 00000000 00010f94 008b73e4 02d7f558
00003a2c 00000000 00029000 005218a8 035e0000 04000021 00000000 00000003
Call Trace:
[<000039e4>] _sys_mmap2+0x0/0x80
[<0000fffe>] _alarm_setitimer+0x36/0x50
[<00008000>] _bfin_demux_gpio_irq+0x54/0x94
[<00029000>] _wait_on_page_bit+0x48/0x70
[<00029000>] _wait_on_page_bit+0x48/0x70
Mem-info:
DMA per-cpu:
CPU 0: Hot: hi: 18, btch: 3 usd: 15 Cold: hi: 6, btch: 1 usd: 5
Active:3141 inactive:3167 dirty:0 writeback:0 unstable:0
free:561 slab:867 mapped:0 pagetables:0 bounce:0
DMA free:2244kB min:1000kB low:1248kB high:1500kB active:12564kB inactive:12668kB present:62992kB pages_scanned:0 all_unreclolowmem_reserve[]: 0 0
DMA: 121*4kB 54*8kB 25*16kB 7*32kB 7*64kB 0*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB 0*32768kB = B15871 pages of RAM
615 free pages
745 reserved pages
1 pages shared
0 pages swap cached
Allocation of length 167936 from process 311 failed
DMA per-cpu:
CPU 0: Hot: hi: 18, btch: 3 usd: 15 Cold: hi: 6, btch: 1 usd: 5
Active:3141 inactive:3167 dirty:0 writeback:0 unstable:0
free:561 slab:867 mapped:0 pagetables:0 bounce:0
DMA free:2244kB min:1000kB low:1248kB high:1500kB active:12564kB inactive:12668kB present:62992kB pages_scanned:0 all_unreclolowmem_reserve[]: 0 0
DMA: 121*4kB 54*8kB 25*16kB 7*32kB 7*64kB 0*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB 0*16384kB 0*32768kB = B
crash.doc
QuoteReplyEditDelete
2008-11-10 09:12:49 Re: BF-548 kernel crash
Mike Frysinger (UNITED STATES)
Message: 64931
it means your application tried to allocate a 256k chunk of memory but there was no contiguous region that large available
you'll have to modify the application to not allocate/free large allocations, or add more memory to your system
QuoteReplyEditDelete
2008-11-11 09:00:08 Re: BF-548 kernel crash
Maha lakshmi (INDIA)
Message: 65028
Mike,
Thanks for your reply but I don't understand. How do I add more memory to my system? Do u mean to reduce the kernel filesystem size??
Thanks,
Maha
QuoteReplyEditDelete
2008-11-11 09:06:41 Re: BF-548 kernel crash
Mike Frysinger (UNITED STATES)
Message: 65029
you can analyze where memory is being used and free some things, or you will have to put more physical memory on the board
the kernel boot log tells you the initial memory map and you can look at runtime usage with /proc/maps and /proc/<pid>/maps