On 01/18/2017 01:27 AM, Andreas Färber wrote: > Am 18.01.2017 um 01:00 schrieb Andreas Färber: >> Am 17.01.2017 um 09:21 schrieb Neil Armstrong: >>> The stress-ng package provides this "stress" command and is used to force the kernel to map more memory >>> zones, but I also got the issue while running a fully fledged Desktop Environment thanks to the >>> recently merged DRM driver. >>> You may not be able to trigger the issue since it seems Amlogic reduces this reserved size on GXL/GXM : >>> https://github.com/khadas/linux/commit/698df2c6cfbb0d1a9359743208e83517b31da6ce >>> But it should be confirmed. >> >> Confirming no issues on three runs on meson-gxm-rbox-pro: >> >> boxer:~ # stress-ng --vm 4 --vm-bytes 128M --timeout 10s & >> [1] 2528 >> boxer:~ # stress-ng: info: [2528] dispatching hogs: 4 vm >> stress-ng: info: [2528] cache allocate: default cache size: 256K >> stress-ng: info: [2528] successful run completed in 10.07s >> >> [1]+ Done stress-ng --vm 4 --vm-bytes 128M --timeout 10s >> boxer:~ # stress-ng --vm 4 --vm-bytes 128M --timeout 10s >> stress-ng: info: [2537] dispatching hogs: 4 vm >> stress-ng: info: [2537] cache allocate: default cache size: 256K >> stress-ng: info: [2537] successful run completed in 10.07s >> boxer:~ # stress-ng --vm 4 --vm-bytes 128M --timeout 10s >> stress-ng: info: [2546] dispatching hogs: 4 vm >> stress-ng: info: [2546] cache allocate: default cache size: 256K >> stress-ng: info: [2546] successful run completed in 10.07s >> boxer:~ # > > Similar results on meson-gxbb-vega-s95-telos (except 512K cache size), > with both mainline EFI and vendor U-Boot. > > I notice that I don't have CONFIG_DRM enabled - maybe related? Yes, It may add more pressure on the memory allocation. Neil > > Regards, > Andreas > -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
