mbox.err is used in the OS-interface layer only. My implementation (FreeRTOS) increments it if sending a message fails or if the mailbox is not empty when deleted.
Jan On 08.08.2017 10:58, Mohsin Madki wrote: > SYS > sem.used: 6 > sem.max: 11 > sem.err: 0 > mutex.used: 0 > mutex.max: 0 > mutex.err: 0 > mbox.used: 6 > mbox.max: 11 > mbox.err: 1 > > > what is mbox.err? > > On Tue, Aug 8, 2017 at 2:14 PM, Mohsin Madki <m.mohsin...@gmail.com > <mailto:m.mohsin...@gmail.com>> wrote: > > here is the data got from lwip_stats when ethernet stopped working. > > LINK > xmit: 0 > recv: 0 > fw: 0 > drop: 0 > chkerr: 0 > lenerr: 0 > memerr: 0 > rterr: 0 > proterr: 0 > opterr: 0 > err: 0 > cachehit: 0 > > ETHARP > xmit: 10 > recv: 5291 > fw: 0 > drop: 5 > chkerr: 0 > lenerr: 0 > memerr: 0 > rterr: 0 > proterr: 5 > opterr: 0 > err: 0 > cachehit: 5609 > > IP > xmit: 8322 > recv: 45383 > fw: 0 > drop: 0 > chkerr: 0 > lenerr: 0 > memerr: 0 > rterr: 0 > proterr: 0 > opterr: 0 > err: 0 > cachehit: 0 > > ICMP > xmit: 1279 > recv: 1279 > fw: 0 > drop: 0 > chkerr: 0 > lenerr: 0 > memerr: 0 > rterr: 0 > proterr: 0 > opterr: 0 > err: 0 > cachehit: 0 > > UDP > xmit: 0 > recv: 3797 > fw: 0 > drop: 0 > chkerr: 0 > lenerr: 0 > memerr: 0 > rterr: 0 > proterr: 0 > opterr: 0 > err: 0 > cachehit: 0 > > TCP > xmit: 63169 > recv: 39686 > fw: 0 > drop: 1417 > chkerr: 0 > lenerr: 0 > memerr: 0 > rterr: 0 > proterr: 1417 > opterr: 0 > err: 0 > cachehit: 0 > > MEM HEAP > avail: 10240 > used: 0 > max: 2508 > err: 0 > > MEM RAW_PCB > avail: 4 > used: 0 > max: 0 > err: 0 > > MEM UDP_PCB > avail: 6 > used: 0 > max: 0 > err: 0 > > MEM TCP_PCB > avail: 10 > used: 0 > max: 10 > err: 0 > > MEM TCP_PCB_LISTEN > avail: 10 > used: 5 > max: 5 > err: 0 > > MEM TCP_SEG > avail: 20 > used: 0 > max: 18 > err: 0 > > MEM NETBUF > avail: 6 > used: 0 > max: 5 > err: 0 > > MEM NETCONN > avail: 10 > used: 5 > max: 10 > err: 0 > > MEM TCPIP_MSG_API > avail: 8 > used: 0 > max: 0 > err: 0 > > MEM TCPIP_MSG_INPKT > avail: 8 > used: 0 > max: 6 > err: 0 > > MEM SYS_TIMEOUT > avail: 10 > used: 4 > max: 5 > err: 0 > > MEM PBUF_REF/ROM > avail: 64 > used: 0 > max: 22 > err: 0 > > MEM PBUF_POOL > avail: 12 > used: 0 > max: 6 > err: 0 > > SYS > sem.used: 6 > sem.max: 11 > sem.err: 0 > mutex.used: 0 > mutex.max: 0 > mutex.err: 0 > mbox.used: 6 > mbox.max: 11 > mbox.err: 0 > > On Tue, Aug 8, 2017 at 10:32 AM, Mohsin Madki <m.mohsin...@gmail.com > <mailto:m.mohsin...@gmail.com>> wrote: > > Thanks Simon, > I mean rest of the processes are working but only ethernet > related functions stops working. > It's my first project with LwIP so dont know from where to start > debug. > Now as you suggested I'll try to get data from lwip_stats first. > > Thanks again. > > > On Tue, Aug 8, 2017 at 10:02 AM, Simon Goldschmidt > <goldsi...@gmx.de <mailto:goldsi...@gmx.de>> wrote: > > Mohsin Madki wrote: > > can anybody reply to this email. > > That's hard. First, I don't know what "stops working" means. > Then: no way to tell from here. Get a debugger and start > searching what's wrong. "lwip_stats" might help you. > > > Simon > > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org <mailto:lwip-users@nongnu.org> > https://lists.nongnu.org/mailman/listinfo/lwip-users > <https://lists.nongnu.org/mailman/listinfo/lwip-users> > > > > > > > _______________________________________________ > lwip-users mailing list > lwip-users@nongnu.org > https://lists.nongnu.org/mailman/listinfo/lwip-users > _______________________________________________ lwip-users mailing list lwip-users@nongnu.org https://lists.nongnu.org/mailman/listinfo/lwip-users