Forgot to copy kernel messages for 4.1 kernel
[ 4531.561953] mmcqd/1: page allocation failure: order:3, mode:0x204020 [ 4531.561989] CPU: 0 PID: 607 Comm: mmcqd/1 Not tainted 4.1.18-005-ts-armv7l #2 [ 4531.562001] Hardware name: Generic AM33XX (Flattened Device Tree) [ 4531.562063] [<c0013cac>] (unwind_backtrace) from [<c0011f08>] (show_stack +0x10/0x14) [ 4531.562090] [<c0011f08>] (show_stack) from [<c0091710>] ( warn_alloc_failed+0xe4/0x120) [ 4531.562115] [<c0091710>] (warn_alloc_failed) from [<c0093d50>] ( __alloc_pages_nodemask+0x53c/0x83c) [ 4531.562139] [<c0093d50>] (__alloc_pages_nodemask) from [<c00bf0d8>] ( cache_alloc_refill+0x2c8/0x53c) [ 4531.562159] [<c00bf0d8>] (cache_alloc_refill) from [<c00bf4c0>] ( __kmalloc+0xa8/0xe8) [ 4531.562191] [<c00bf4c0>] (__kmalloc) from [<c023c4c0>] ( edma_prep_slave_sg+0x8c/0x2d4) [ 4531.562221] [<c023c4c0>] (edma_prep_slave_sg) from [<c032673c>] ( omap_hsmmc_request+0x420/0x50c) [ 4531.562254] [<c032673c>] (omap_hsmmc_request) from [<c0311f94>] ( mmc_start_request+0xf4/0x11c) [ 4531.562277] [<c0311f94>] (mmc_start_request) from [<c0312c18>] ( mmc_start_req+0x288/0x394) [ 4531.562308] [<c0312c18>] (mmc_start_req) from [<c03200b0>] ( mmc_blk_issue_rw_rq+0xb4/0xaac) [ 4531.562332] [<c03200b0>] (mmc_blk_issue_rw_rq) from [<c0320ba0>] ( mmc_blk_issue_rq+0xf8/0x4a8) [ 4531.562351] [<c0320ba0>] (mmc_blk_issue_rq) from [<c0322318>] ( mmc_queue_thread+0x94/0x130) [ 4531.562377] [<c0322318>] (mmc_queue_thread) from [<c0049600>] (kthread+ 0xd4/0xec) [ 4531.562399] [<c0049600>] (kthread) from [<c000f0c8>] (ret_from_fork+0x14/ 0x2c) [ 4531.562409] Mem-Info: [ 4531.562437] active_anon:4260 inactive_anon:17 isolated_anon:0 [ 4531.562437] active_file:13673 inactive_file:38058 isolated_file:0 [ 4531.562437] unevictable:422 dirty:1384 writeback:695 unstable:0 [ 4531.562437] slab_reclaimable:1709 slab_unreclaimable:1539 [ 4531.562437] mapped:1154 shmem:39 pagetables:170 bounce:0 [ 4531.562437] free:2420 free_pcp:54 free_cma:1600 [ 4531.562496] Normal free:9680kB min:2004kB low:2504kB high:3004kB active_anon:17040kB inactive_anon:68kB active_file:54692kB inactive_file: 152232kB unevictable:1688kB isolated(anon):0kB isolated(file):0kB present: 261120kB managed:251972kB mlocked:1688kB dirty:5536kB writeback:2780kB mapped:4616kB shmem:156kB slab_reclaimable:6836kB slab_unreclaimable:6156kB kernel_stack:880kB pagetables:680kB unstable:0kB bounce:0kB free_pcp:216kB local_pcp:216kB free_cma:6400kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no [ 4531.562509] lowmem_reserve[]: 0 0 0 [ 4531.562527] Normal: 606*4kB (UEMRC) 453*8kB (UMRC) 165*16kB (C) 29*32kB ( C) 1*64kB (C) 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB 0*8192kB = 9680kB [ 4531.562584] 52118 total pagecache pages [ 4531.562600] 0 pages in swap cache [ 4531.562609] Swap cache stats: add 0, delete 0, find 0/0 [ 4531.562617] Free swap = 0kB [ 4531.562624] Total swap = 0kB [ 4531.562631] 65280 pages RAM [ 4531.562639] 0 pages HighMem/MovableOnly [ 4531.562646] 4294965487 pages reserved [ 4531.562654] 4096 pages cma reserved [ 4531.562696] edma-dma-engine edma-dma-engine.0: edma_prep_slave_sg: Failed to allocate a descriptor [ 4531.562714] omap_hsmmc 481d8000.mmc: prep_slave_sg() failed [ 4531.562726] omap_hsmmc 481d8000.mmc: MMC start dma failure [ 4531.571575] mmcblk0: unknown error -1 sending read/write command, card status 0x900 [ 4531.571679] mmc1: tried to reset card [ 4531.571696] blk_update_request: 229 callbacks suppressed [ 4531.571707] blk_update_request: I/O error, dev mmcblk0, sector 1357784 [ 4531.571734] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71780 (offset 0 size 0 starting block 678895) [ 4531.571751] buffer_io_error: 396 callbacks suppressed [ 4531.571764] Buffer I/O error on device mmcblk0p16, logical block 138220 [ 4531.571775] Buffer I/O error on device mmcblk0p16, logical block 138221 [ 4531.571786] Buffer I/O error on device mmcblk0p16, logical block 138222 [ 4531.572243] blk_update_request: I/O error, dev mmcblk0, sector 1357790 [ 4531.572265] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71781 (offset 0 size 0 starting block 678898) [ 4531.572282] Buffer I/O error on device mmcblk0p16, logical block 138223 [ 4531.572293] Buffer I/O error on device mmcblk0p16, logical block 138224 [ 4531.572304] Buffer I/O error on device mmcblk0p16, logical block 138225 [ 4531.572498] blk_update_request: I/O error, dev mmcblk0, sector 1357796 [ 4531.572518] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71782 (offset 0 size 0 starting block 678901) [ 4531.572534] Buffer I/O error on device mmcblk0p16, logical block 138226 [ 4531.572545] Buffer I/O error on device mmcblk0p16, logical block 138227 [ 4531.572556] Buffer I/O error on device mmcblk0p16, logical block 138228 [ 4531.572703] blk_update_request: I/O error, dev mmcblk0, sector 1357802 [ 4531.572720] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71785 (offset 0 size 0 starting block 678904) [ 4531.572734] Buffer I/O error on device mmcblk0p16, logical block 138229 [ 4531.572863] blk_update_request: I/O error, dev mmcblk0, sector 1357808 [ 4531.572881] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71786 (offset 0 size 0 starting block 678907) [ 4531.573010] blk_update_request: I/O error, dev mmcblk0, sector 1357814 [ 4531.573027] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71787 (offset 0 size 0 starting block 678910) [ 4531.573155] blk_update_request: I/O error, dev mmcblk0, sector 1357820 [ 4531.573172] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71788 (offset 0 size 0 starting block 678913) [ 4531.573299] blk_update_request: I/O error, dev mmcblk0, sector 1357826 [ 4531.573316] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71789 (offset 0 size 0 starting block 678916) [ 4531.573442] blk_update_request: I/O error, dev mmcblk0, sector 1357832 [ 4531.573459] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71790 (offset 0 size 0 starting block 678919) [ 4531.573583] blk_update_request: I/O error, dev mmcblk0, sector 1357838 [ 4531.573600] EXT4-fs warning (device mmcblk0p16): ext4_end_bio:332: I/O error -5 writing to inode 71791 (offset 0 size 0 starting block 678922) On Monday, 29 August 2016 20:54:55 UTC+5:30, Ankur Tank wrote: > > Hello Mr.Nelson, > > This issue is reproducible in 4.1 kernel also. > I found the use case where it is almost every time reproducible. > > 1. Conider that we have two RFS partition, and current root is > /dev/mmcblk0p15. Another RFS partition /dev/mmcblk0p16 is not in use. > 2. Create RFS tar of 390MB(compressed size. Uncompressed size is 487MB) of > size. I had include some big files in it. (I had copied 35 files of size > 10MB each). > 3. Copy this big tar e.g. rootfs.tar.gz to board. > 4. Mount unused partition i.e. /dev/mmcblk0p16 to /mnt/rfs_test. > 5. Delete content from /mnt/rfs_test/, using command > rm -rf /mnt/rfs_test/* > 6. Untar rootfs.tar.gz to /mnt/rfs_test/ > tar -xzvf /home/rootfs.tar.gz -C /mnt/rfs_test/ > 7. From another ssh terminal run > while [ true ];do dd if=/dev/mmcblk0p16 of=/dev/null bs=1M; done > 8. From yet another terminal observe the syslog, or dmesg > while [ ture ] ; do clear; dmesg | tail -n 30; sleep 2;done > 9. Before tar extraction completes you will see error reproduced. > > So It doesn't seem to be mmc driver issue, isn't it ? > Do you have any suggestion/pointer for me ? > > Thank you, > > Regards, > Ankur > > On Tuesday, 19 July 2016 22:38:25 UTC+5:30, RobertCNelson wrote: >> >> >> >> On Tue, Jul 19, 2016 at 11:11 AM, Ankur Tank <art...@gmail.com> wrote: >> >>> >>> We are using BeagleBoneBlack based custom Linux board. >>> It has 256MB of RAM and 4GB of eMMC. >>> Currently RFS size of the project is 163MB. While RFS partition size is >>> 500MB. >>> For testing, we added 20 number of big files(10MB size) and started >>> firmware upgrade process. >>> >>> During the firmware Upgrade process we see following error when roofs is >>> being written, >>> >>> We could solve it by changing >>> /proc/sys/vm/min_free_kbytes >>> >>> from *2005* to *4096*. >>> >>> *But now my doubt is what should be the ideal value for that, what >>> factors we should consider while calculating it. From the kernel >>> documentation I don't get that information, * >>> *but I could understand one thing that is this value can not be too low >>> or too high or else system will break.* >>> >>> Any suggestion/pointer ? >>> >>> [ 6676.674219] mmcqd/1: page allocation failure: order:1, mode: >>> 0x200020 >>> [ 6676.674256] CPU: 0 PID: 612 Comm: mmcqd/1 Tainted: P O >>> 3.12.10-005-ts-armv7l #2 >>> [ 6676.674321] [<c0012d24>] (unwind_backtrace+0x0/0xf4) from [< >>> c0011130>] (show_stack+0x10/0x14) >>> [ 6676.674355] [<c0011130>] (show_stack+0x10/0x14) from [<c0087548>] >>> (warn_alloc_failed+0xe0/0x118) >>> [ 6676.674383] [<c0087548>] (warn_alloc_failed+0xe0/0x118) from [< >>> c008a3ac>] (__alloc_pages_nodemask+0x74c/0x8f8) >>> [ 6676.674413] [<c008a3ac>] (__alloc_pages_nodemask+0x74c/0x8f8) >>> from [<c00b2e8c>] (cache_alloc_refill+0x328/0x620) >>> [ 6676.674436] [<c00b2e8c>] (cache_alloc_refill+0x328/0x620) from [< >>> c00b3224>] (__kmalloc+0xa0/0xe8) >>> [ 6676.674471] [<c00b3224>] (__kmalloc+0xa0/0xe8) from [<c0212904>] >>> (edma_prep_slave_sg+0x84/0x388) >>> [ 6676.674505] [<c0212904>] (edma_prep_slave_sg+0x84/0x388) from [< >>> c02ec0a0>] (omap_hsmmc_request+0x414/0x508) >>> [ 6676.674544] [<c02ec0a0>] (omap_hsmmc_request+0x414/0x508) from [< >>> c02d6748>] (mmc_start_request+0xc4/0xe0) >>> [ 6676.674568] [<c02d6748>] (mmc_start_request+0xc4/0xe0) from [< >>> c02d7530>] (mmc_start_req+0x2d8/0x38c) >>> [ 6676.674589] [<c02d7530>] (mmc_start_req+0x2d8/0x38c) from [< >>> c02e4818>] (mmc_blk_issue_rw_rq+0xb4/0x9d8) >>> [ 6676.674611] [<c02e4818>] (mmc_blk_issue_rw_rq+0xb4/0x9d8) from [< >>> c02e52e0>] (mmc_blk_issue_rq+0x1a4/0x468) >>> [ 6676.674631] [<c02e52e0>] (mmc_blk_issue_rq+0x1a4/0x468) from [< >>> c02e5c68>] (mmc_queue_thread+0x88/0x118) >>> [ 6676.674657] [<c02e5c68>] (mmc_queue_thread+0x88/0x118) from [< >>> c004d8b8>] (kthread+0xb4/0xb8) >>> [ 6676.674681] [<c004d8b8>] (kthread+0xb4/0xb8) from [<c000e298>] ( >>> ret_from_fork+0x14/0x3c) >>> >> >> This actually smells very much like the random mmc issues we saw on >> "3.8.x" based images... mmc wasn't really fixed/solid till the 3.14.x >> timeline... Not sure how much of that was back-ported to 3.12.10... >> >> Regards, >> >> -- >> Robert Nelson >> https://rcn-ee.com/ >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9f9dc142-778d-4cab-a72a-06e5d0004caa%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
