This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

mount: page allocation failure.



Hi,

Sometimes we are getting NAND mount failure as shown in below logs,


Feb 13 16:58:03 root user.warn kernel: mount: page allocation failure. order:5, mode:0x40d0
Feb 13 16:58:03 root user.warn kernel: Backtrace:
Feb 13 16:58:03 root user.warn kernel: [<c0052078>] (dump_backtrace+0x0/0x110) from [<c04d403c>] (dump_stack+0x18/0x1c)
Feb 13 16:58:03 root user.warn kernel:  r6:00000001 r5:00000005 r4:000040d0 r3:60000013
Feb 13 16:58:03 root user.warn kernel: [<c04d4024>] (dump_stack+0x0/0x1c) from [<c00b056c>] (__alloc_pages_nodemask+0x4fc/0x560)
Feb 13 16:58:03 root user.warn kernel: [<c00b0070>] (__alloc_pages_nodemask+0x0/0x560) from [<c00b05e8>] (__get_free_pages+0x18/0x34)
Feb 13 16:58:03 root user.warn kernel: [<c00b05d0>] (__get_free_pages+0x0/0x34) from [<c00ce6bc>] (__kmalloc+0x3c/0xc0)
Feb 13 16:58:03 root user.warn kernel: [<c00ce680>] (__kmalloc+0x0/0xc0) from [<c0231ec4>] (jffs2_scan_medium+0xdc/0x119c)
Feb 13 16:58:03 root user.warn kernel:  r8:c0237354 r7:00020000 r6:ea4fe200 r5:00000000 r4:ea4fea00
Feb 13 16:58:03 root user.warn kernel: r3:00000004
Feb 13 16:58:03 root user.warn kernel: [<c0231de8>] (jffs2_scan_medium+0x0/0x119c) from [<c0234d1c>] (jffs2_do_mount_fs+0x180/0x59c)
Feb 13 16:58:03 root user.warn kernel: [<c0234b9c>] (jffs2_do_mount_fs+0x0/0x59c) from [<c0236eac>] (jffs2_do_fill_super+0x154/0x238)
Feb 13 16:58:03 root user.warn kernel:  r8:c0237354 r7:00020000 r6:ea4fe200 r5:00000000 r4:ea4fea00
Feb 13 16:58:03 root user.warn kernel: [<c0236d58>] (jffs2_do_fill_super+0x0/0x238) from [<c0237410>] (jffs2_fill_super+0xbc/0xdc)
Feb 13 16:58:03 root user.warn kernel:  r7:00000000 r6:00000001 r5:ea4fea00 r4:ea4fe200
Feb 13 16:58:03 root user.warn kernel: [<c0237354>] (jffs2_fill_super+0x0/0xdc) from [<c0312a84>] (mount_mtd_aux.clone.0+0x50/0xd4)
Feb 13 16:58:03 root user.warn kernel:  r7:ea4fe200 r6:00000000 r5:00008000 r4:eb3a1c00
Feb 13 16:58:03 root user.warn kernel: [<c0312a34>] (mount_mtd_aux.clone.0+0x0/0xd4) from [<c0312c1c>] (mount_mtd+0x114/0x144)
Feb 13 16:58:03 root user.warn kernel:  r7:00000000 r6:ea68e400 r5:c06a1e34 r4:00008000
Feb 13 16:58:03 root user.warn kernel: [<c0312b08>] (mount_mtd+0x0/0x144) from [<c02370e8>] (jffs2_mount+0x1c/0x28)
Feb 13 16:58:03 root user.warn kernel: [<c02370cc>] (jffs2_mount+0x0/0x28) from [<c00d2d28>] (vfs_kern_mount+0xa4/0x1e4)
Feb 13 16:58:03 root user.warn kernel: [<c00d2c84>] (vfs_kern_mount+0x0/0x1e4) from [<c00d2ec4>] (do_kern_mount+0x3c/0xe4)
Feb 13 16:58:03 root user.warn kernel: [<c00d2e88>] (do_kern_mount+0x0/0xe4) from [<c00e888c>] (do_mount+0x638/0x6a8)
Feb 13 16:58:03 root user.warn kernel:  r8:00000000 r7:00000000 r6:ea68e400 r5:00000020 r4:00000000
Feb 13 16:58:03 root user.warn kernel: r3:00000000
Feb 13 16:58:03 root user.warn kernel: [<c00e8254>] (do_mount+0x0/0x6a8) from [<c00e8b44>] (sys_mount+0x8c/0xcc)
Feb 13 16:58:03 root user.warn kernel: [<c00e8ab8>] (sys_mount+0x0/0xcc) from [<c004e3c0>] (ret_fast_syscall+0x0/0x30)
Feb 13 16:58:03 root user.warn kernel:  r7:00000015 r6:400694d0 r5:beb62bb8 r4:00000000
Feb 13 16:58:03 root user.warn kernel: Mem-info:
Feb 13 16:58:03 root user.warn kernel: Normal per-cpu:
Feb 13 16:58:03 root user.warn kernel: CPU    0: hi:  186, btch:  31 usd:   0
Feb 13 16:58:03 root user.warn kernel: HighMem per-cpu:
Feb 13 16:58:03 root user.warn kernel: CPU    0: hi:   90, btch:  15 usd:   0
Feb 13 16:58:03 root user.warn kernel: active_anon:54915 inactive_anon:44 isolated_anon:7
Feb 13 16:58:03 root user.warn kernel:  active_file:10464 inactive_file:30946 isolated_file:25
Feb 13 16:58:03 root user.warn kernel:  unevictable:0 dirty:0 writeback:0 unstable:0
Feb 13 16:58:03 root user.warn kernel:  free:43717 slab_reclaimable:9128 slab_unreclaimable:2726
Feb 13 16:58:03 root user.warn kernel:  mapped:1218 shmem:51249 pagetables:226 bounce:0
Feb 13 16:58:03 root user.warn kernel: Normal free:172436kB min:2668kB low:3332kB high:4000kB active_anon:145992kB inactive_anon:24kB active_file:8608kB inactive_file:57180kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:444992kB mlocked:0kB dirty:0k
Feb 13 16:58:03 root user.warn kernel: lowmem_reserve[]: 0 1419 1419
Feb 13 16:58:03 root user.warn kernel: HighMem free:2432kB min:176kB low:448kB high:720kB active_anon:73668kB inactive_anon:152kB active_file:33248kB inactive_file:66604kB unevictable:0kB isolated(anon):28kB isolated(file):100kB present:181696kB mlocked:0kB dirty:0k
Feb 13 16:58:03 root user.warn kernel: lowmem_reserve[]: 0 0 0
Feb 13 16:58:03 root user.warn kernel: Normal: 3353*4kB 15208*8kB 2259*16kB 32*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 172436kB
Feb 13 16:58:03 root user.warn kernel: HighMem: 184*4kB 66*8kB 39*16kB 5*32kB 6*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2432kB
Feb 13 16:58:03 root user.warn kernel: 92665 total pagecache pages
Feb 13 16:58:03 root user.warn kernel: 163840 pages of RAM
Feb 13 16:58:03 root user.warn kernel: 44025 free pages
Feb 13 16:58:03 root user.warn kernel: 8515 reserved pages
Feb 13 16:58:03 root user.warn kernel: 11615 slab pages
Feb 13 16:58:03 root user.warn kernel: 46656 pages shared
Feb 13 16:58:03 root user.warn kernel: 0 pages swap cached
Feb 13 16:58:03 root user.err FirmwareUpgradeApp: [Fri Feb 13 16:58:03 2015] : FIRMWARE_UPGRADE : "Error in mount /dev/mtdblock8 block to /3rdeye/oldConfigParition/ directory"


Here we try to mount our /dev/mtdblock8 NAND partition on /3rdeye/oldConfigParition/. This error is coming once in a while or you can say once from twenty time.

As logged by kernel: Normal: 3353*4kB 15208*8kB 2259*16kB 32*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 172436kB. We don't have any 256kB or higher size contiguous block for memory allocation which is causing these issue.

I am using DVRRDK_04.01.00.02 and it's components for DM8148 processor based hardware.

Can any one have solution for these issue? Or any kernel patches will be great full.

Regards,

Ravi Bhuva.

  • Hello Ti-Friends,

    Sometimes we are getting NAND mount failure as shown in below logs,


    Feb 13 16:58:03 root user.warn kernel: mount: page allocation failure. order:5, mode:0x40d0
    Feb 13 16:58:03 root user.warn kernel: Backtrace:
    Feb 13 16:58:03 root user.warn kernel: [<c0052078>] (dump_backtrace+0x0/0x110) from [<c04d403c>] (dump_stack+0x18/0x1c)
    Feb 13 16:58:03 root user.warn kernel:  r6:00000001 r5:00000005 r4:000040d0 r3:60000013
    Feb 13 16:58:03 root user.warn kernel: [<c04d4024>] (dump_stack+0x0/0x1c) from [<c00b056c>] (__alloc_pages_nodemask+0x4fc/0x560)
    Feb 13 16:58:03 root user.warn kernel: [<c00b0070>] (__alloc_pages_nodemask+0x0/0x560) from [<c00b05e8>] (__get_free_pages+0x18/0x34)
    Feb 13 16:58:03 root user.warn kernel: [<c00b05d0>] (__get_free_pages+0x0/0x34) from [<c00ce6bc>] (__kmalloc+0x3c/0xc0)
    Feb 13 16:58:03 root user.warn kernel: [<c00ce680>] (__kmalloc+0x0/0xc0) from [<c0231ec4>] (jffs2_scan_medium+0xdc/0x119c)
    Feb 13 16:58:03 root user.warn kernel:  r8:c0237354 r7:00020000 r6:ea4fe200 r5:00000000 r4:ea4fea00
    Feb 13 16:58:03 root user.warn kernel: r3:00000004
    Feb 13 16:58:03 root user.warn kernel: [<c0231de8>] (jffs2_scan_medium+0x0/0x119c) from [<c0234d1c>] (jffs2_do_mount_fs+0x180/0x59c)
    Feb 13 16:58:03 root user.warn kernel: [<c0234b9c>] (jffs2_do_mount_fs+0x0/0x59c) from [<c0236eac>] (jffs2_do_fill_super+0x154/0x238)
    Feb 13 16:58:03 root user.warn kernel:  r8:c0237354 r7:00020000 r6:ea4fe200 r5:00000000 r4:ea4fea00
    Feb 13 16:58:03 root user.warn kernel: [<c0236d58>] (jffs2_do_fill_super+0x0/0x238) from [<c0237410>] (jffs2_fill_super+0xbc/0xdc)
    Feb 13 16:58:03 root user.warn kernel:  r7:00000000 r6:00000001 r5:ea4fea00 r4:ea4fe200
    Feb 13 16:58:03 root user.warn kernel: [<c0237354>] (jffs2_fill_super+0x0/0xdc) from [<c0312a84>] (mount_mtd_aux.clone.0+0x50/0xd4)
    Feb 13 16:58:03 root user.warn kernel:  r7:ea4fe200 r6:00000000 r5:00008000 r4:eb3a1c00
    Feb 13 16:58:03 root user.warn kernel: [<c0312a34>] (mount_mtd_aux.clone.0+0x0/0xd4) from [<c0312c1c>] (mount_mtd+0x114/0x144)
    Feb 13 16:58:03 root user.warn kernel:  r7:00000000 r6:ea68e400 r5:c06a1e34 r4:00008000
    Feb 13 16:58:03 root user.warn kernel: [<c0312b08>] (mount_mtd+0x0/0x144) from [<c02370e8>] (jffs2_mount+0x1c/0x28)
    Feb 13 16:58:03 root user.warn kernel: [<c02370cc>] (jffs2_mount+0x0/0x28) from [<c00d2d28>] (vfs_kern_mount+0xa4/0x1e4)
    Feb 13 16:58:03 root user.warn kernel: [<c00d2c84>] (vfs_kern_mount+0x0/0x1e4) from [<c00d2ec4>] (do_kern_mount+0x3c/0xe4)
    Feb 13 16:58:03 root user.warn kernel: [<c00d2e88>] (do_kern_mount+0x0/0xe4) from [<c00e888c>] (do_mount+0x638/0x6a8)
    Feb 13 16:58:03 root user.warn kernel:  r8:00000000 r7:00000000 r6:ea68e400 r5:00000020 r4:00000000
    Feb 13 16:58:03 root user.warn kernel: r3:00000000
    Feb 13 16:58:03 root user.warn kernel: [<c00e8254>] (do_mount+0x0/0x6a8) from [<c00e8b44>] (sys_mount+0x8c/0xcc)
    Feb 13 16:58:03 root user.warn kernel: [<c00e8ab8>] (sys_mount+0x0/0xcc) from [<c004e3c0>] (ret_fast_syscall+0x0/0x30)
    Feb 13 16:58:03 root user.warn kernel:  r7:00000015 r6:400694d0 r5:beb62bb8 r4:00000000
    Feb 13 16:58:03 root user.warn kernel: Mem-info:
    Feb 13 16:58:03 root user.warn kernel: Normal per-cpu:
    Feb 13 16:58:03 root user.warn kernel: CPU    0: hi:  186, btch:  31 usd:   0
    Feb 13 16:58:03 root user.warn kernel: HighMem per-cpu:
    Feb 13 16:58:03 root user.warn kernel: CPU    0: hi:   90, btch:  15 usd:   0
    Feb 13 16:58:03 root user.warn kernel: active_anon:54915 inactive_anon:44 isolated_anon:7
    Feb 13 16:58:03 root user.warn kernel:  active_file:10464 inactive_file:30946 isolated_file:25
    Feb 13 16:58:03 root user.warn kernel:  unevictable:0 dirty:0 writeback:0 unstable:0
    Feb 13 16:58:03 root user.warn kernel:  free:43717 slab_reclaimable:9128 slab_unreclaimable:2726
    Feb 13 16:58:03 root user.warn kernel:  mapped:1218 shmem:51249 pagetables:226 bounce:0
    Feb 13 16:58:03 root user.warn kernel: Normal free:172436kB min:2668kB low:3332kB high:4000kB active_anon:145992kB inactive_anon:24kB active_file:8608kB inactive_file:57180kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:444992kB mlocked:0kB dirty:0k
    Feb 13 16:58:03 root user.warn kernel: lowmem_reserve[]: 0 1419 1419
    Feb 13 16:58:03 root user.warn kernel: HighMem free:2432kB min:176kB low:448kB high:720kB active_anon:73668kB inactive_anon:152kB active_file:33248kB inactive_file:66604kB unevictable:0kB isolated(anon):28kB isolated(file):100kB present:181696kB mlocked:0kB dirty:0k
    Feb 13 16:58:03 root user.warn kernel: lowmem_reserve[]: 0 0 0
    Feb 13 16:58:03 root user.warn kernel: Normal: 3353*4kB 15208*8kB 2259*16kB 32*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 172436kB
    Feb 13 16:58:03 root user.warn kernel: HighMem: 184*4kB 66*8kB 39*16kB 5*32kB 6*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 2432kB
    Feb 13 16:58:03 root user.warn kernel: 92665 total pagecache pages
    Feb 13 16:58:03 root user.warn kernel: 163840 pages of RAM
    Feb 13 16:58:03 root user.warn kernel: 44025 free pages
    Feb 13 16:58:03 root user.warn kernel: 8515 reserved pages
    Feb 13 16:58:03 root user.warn kernel: 11615 slab pages
    Feb 13 16:58:03 root user.warn kernel: 46656 pages shared
    Feb 13 16:58:03 root user.warn kernel: 0 pages swap cached
    Feb 13 16:58:03 root user.err FirmwareUpgradeApp: [Fri Feb 13 16:58:03 2015] : FIRMWARE_UPGRADE : "Error in mount /dev/mtdblock8 block to /3rdeye/oldConfigParition/ directory"


    Here we try to mount our /dev/mtdblock8 NAND partition on /3rdeye/oldConfigParition/. This error is coming once in a while or you can say once from twenty time.

    As logged by kernel: Normal: 3353*4kB 15208*8kB 2259*16kB 32*32kB 1*64kB 1*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 172436kB. We don't have any 256kB or higher size contiguous block for memory allocation which is causing these issue.

    I am using DVRRDK_04.01.00.02 and it's components for DM8148 processor based hardware.

    Can any one have solution for these issue? Or any kernel patches will be great full.

    Regards,

    Ravi Bhuva.

  • Moving this post to DM814x
  • Ravi,

    See if you have all the patches from the below branch:

    arago-project.org/.../projects;a=shortlog;h=refs/heads/dvrrdk_kernel_int_branch

    Regards,
    Pavel
  • Experimenting how to mark answered, no spam. Sorry for wrong flag enabling.