On Friday 15 November 2013 16:54:03 Bastian Bittorf wrote:
* Sven Eckelmann s...@open-mesh.com [11.11.2013 11:41]:
On Friday 08 November 2013 11:32:23 Weedy wrote:
Do you have any benches or log dumps that show this fixed it for you?
I am not really sure what you are expecting. I can
On 2013-11-08 18:52, s...@open-mesh.com wrote:
From: Sven Eckelmann s...@open-mesh.com
A small system like the common home router doesn't have 40 MiB per process for
a dirty stack cache. This can easily lead to an overbooking OOM problem and
caused a lot of hangs+reboots on 32 MiB systems
* Sven Eckelmann s...@open-mesh.com [11.11.2013 11:41]:
On Friday 08 November 2013 11:32:23 Weedy wrote:
Do you have any benches or log dumps that show this fixed it for you?
I am not really sure what you are expecting. I can not really show a log of
the reset because the device just
On Friday 08 November 2013 11:32:23 Weedy wrote:
Do you have any benches or log dumps that show this fixed it for you?
I am not really sure what you are expecting. I can not really show a log of
the reset because the device just resets when the oom kicks in or the process
is just killed (so it
From: Sven Eckelmann s...@open-mesh.com
A small system like the common home router doesn't have 40 MiB per process for
a dirty stack cache. This can easily lead to an overbooking OOM problem and
caused a lot of hangs+reboots on 32 MiB systems running nodogsplash.
Not using a stack cache can
On 8 Nov 2013 12:52, s...@open-mesh.com wrote:
From: Sven Eckelmann s...@open-mesh.com
A small system like the common home router doesn't have 40 MiB per
process for
a dirty stack cache. This can easily lead to an overbooking OOM problem
and
caused a lot of hangs+reboots on 32 MiB systems
