Hello Experts, I have tried following, 1. I tried changing various virtual memory parameters in /proc/sys/vm/ but didn't have much success. 2. I tried it in ti-processor-sdk-linux-am335x-evm-03.03.00.04 and it seems fail less frequent but it does fail there as well. 3. In 3.12 kernel we had taken two patches mentioned below, which basically freeing some memory,
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/dma/edma.c?id=5ca9e7ce6eebec53362ff779264143860ccf68cd https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/drivers/dma/edma.c?id=e3ddc979465118b7ba46fed7cd10f4421edc3049 Though above patches solved the problem but it took lot of time to extract tar. without this patches it used to take 4m, and with patches it took 1 hour to extract tar, so we couldn't use this patch. 4. Now as those patches are freeing memory in edma.c file I feel there could be memory leak in edma driver but i am unaware of full dma,edma driver so couldn't debug. I saw video about edma controller in TI website but still it is not so easy to go through edma driver. Request someone to suggest how to get to root cause of this issue. Thank you, Regards, Ankur On Wednesday, 31 May 2017 21:25:33 UTC+5:30, Ankur Tank wrote: > > Hi Mr. Nelson, > > if you have any suggestion for this, do let me know. > > Thank you, > > Regards, > Ankur > > On Thursday, 25 May 2017 14:25:20 UTC-4, Ankur Tank wrote: >> >> Hello Experts, >> >> We are seeing fragmentation and resultant eMMC partition corruption when >> extracting tar file with 81000 files of 4k size. >> >> Detailed steps are listed in Test_steps.txt file and other attached tars >> contain required scripts to big tar file and other test scripts. >> >> In test is very simple, >> 1. we have tar with 81000 number of 4k size file >> 2. we ran latest debian from Beagleboard.org from Micro SD Card >> 3. Partitioned eMMC in two partitions >> 4. Then mounted one of the partition and started extracting big tar file >> on that partition. >> >> This results in below Error. >> EXT4-fs error (device mmcblk1p2) in ext4_do_update_inode:4665: Journal >> has aborted >> [12064.194479] EXT4-fs error (device mmcblk1p2) in >> add_dirent_to_buf:1921: Journal has aborted >> [12064.209980] EXT4-fs error (device mmcblk1p2) in >> ext4_do_update_inode:4665: Journal has aborted >> [12064.223765] EXT4-fs error (device mmcblk1p2) in ext4_create:2455: IO >> failure >> [12064.238221] EXT4-fs error (device mmcblk1p2): >> ext4_journal_check_start:56: Detected aborted journal >> [12064.247591] EXT4-fs (mmcblk1p2): Remounting filesystem read-only >> >> >> Strange enough this test works fine on Angstrom OS image >> https://s3.amazonaws.com/angstrom/demo/beaglebone/Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz >> That image has kernel 3.8, while latest debian has kernel 4.4. >> >> I suspect some memory leak in the driver(edma.c). >> >> We see this issue sporadically in field devices so this is not >> unrealistic error. >> We got this use case to reproduce this issue. >> >> Any suggestion, patch to solve this issue ? >> >> Thank you, >> >> Regards, >> Ankur >> >> -- 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/72a2f85e-6301-4066-86b2-87fd8d6720fd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
