Hi Kieran, I have been delving into this problem a bit more and have found an identical issue in the archive. In the archive thread the user was having problems with ethernetif_input() being interrupted by a timer interrupt that called tcp_slowtmr() and resulted in the corruption of the internal packet lists.
In my application I have the reverse condition. tcp_slowtmr() is called periodically from main() with ethernetif_input() called from the Ethernet interrupt. I am assuming if the Ethernet interrupt occurs during tcp_slowtmr() this could possibly be the cause of the corrupted packet lists. Am I correct in this assumption? Thanks, Tony -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kieran Mansley Sent: 13 January 2011 09:36 To: Mailing list for lwIP users Subject: RE: [lwip-users] Lock-up issue with tcp_receive() and tcp_output() On Thu, 2011-01-13 at 08:37 +0000, Carr, Anthony wrote: > I understand it is better to prevent the issue occurring but is there > any way to recover from this condition. No, sorry - once corrupted it's impossible to recover. Kieran _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users _______________________________________________ lwip-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lwip-users
