Just to let you know, this problem is fixed in the latest 6.5.0 io-pkt, so
the only way that we can give you the latest io-pkt is for you to send us
your hardware and source code to your driver. The latest io-pkt requires a
new libc, so the driver needs to be recompiled and tested on your hardware.



On 2016-11-23, 9:29 AM, "Thomas Luetzel" <community-noreply@qnx.com> wrote:

>Hi, yes the VM is connected to the a network but if the VM is running
>without the shell script
>
>run.sh
>===============
>while [ 0 -lt 1 ]
>do
>   df >> /dev/null
>done
>
>the memory increases very fast!
>
>To the answer to Hugh - I am not running any BSP on a target hardware! I
>can reproduce this issue on a VM provided from the QNX homepage. My DUT
>(device under test) is delivered now from QNX, nothing implemented
>installed done from my side!
>
>Attched you will also find the timeline tracelog. I've marked a REPLY
>BLOCED from io-pkt by the df procress. This happens multiple times.
>
>Anything else what I can do to generate log which will help to isolate
>this behaviour.
>
>Thanks in advance
>
>
>
>_______________________________________________
>
>Networking Drivers
>http://community.qnx.com/sf/go/post117176
>To cancel your subscription to this discussion, please e-mail
>drivers-networking-unsubscribe@community.qnx.com