lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [lwip-devel] long term stability - ping no response after fewdays -


From: Pettinato, Jim
Subject: RE: [lwip-devel] long term stability - ping no response after fewdays - HELP ME
Date: Thu, 6 Nov 2008 08:20:53 -0500

 
As far as I recall, all of the problems reported that were related to
long-term stability ended up being either driver issues or application
issues... i.e. not handling incoming packet buffer overruns properly,
not properly protecting critical code (both resulting in a corrupt pbuf
pool) or having application execution paths which did not free received
pbufs properly in all cases (memory leaks eventually leading to pool
depletion).

Since these issues are often hard to nail down as they take time to
occur, I would suggest enabling the stats, and checking that you aren't
slowly leaking pools by exercising each application and verifying the
pbuf pool count returns to starting conditions afterward.

If the instability is a result of broadcast traffic only, I'd suspect a
hole in the driver...

If you do get the error to occur on your debug setup, if your stats show
that you should have pbufs remaining in the pool but your pbuf_pool
pointer is NULL (resulting in pbuf_alloc() always failing) - that's a
sure sign of pool corruption.


  
__

James M. Pettinato, Jr.
Software Engineer
E: address@hidden | P: 814 898 5250 

FMC Technologies Measurement Solutions Inc.
1602 Wagner Avenue | Erie PA | 16510 USA 
Phone: 814 898 5000 | Fax: 814 899-3414
www.fmctechnologies.com 

 

-----Original Message-----
From: address@hidden
[mailto:address@hidden On Behalf
Of Kieran Mansley
Sent: Thursday, November 06, 2008 3:49 AM
To: lwip-devel
Subject: Re: [lwip-devel] long term stability - ping no response after
fewdays - HELP ME

On Thu, 2008-11-06 at 09:22 +0100, Piero 74 wrote:

> Now, i want to know if some bugs found in lwip 130 and fixed in head 
> version could be related to my trouble: ANY IDEA???

There was another issue reported a bit like this a few months ago.
Unfortunately I can't remember what the problem or solution was in more
detail, but searching the mailing lists might bring something up.

Kieran



_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel




reply via email to

[Prev in Thread] Current Thread [Next in Thread]