lwip-users
[Top][All Lists]
Advanced

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

R: [lwip-users] lwip_read hanging and wrong sequence number


From: Cristina Marcucci
Subject: R: [lwip-users] lwip_read hanging and wrong sequence number
Date: Fri, 12 Feb 2010 15:49:27 +0100

Hi Martin, thanks a lot for your answer. I tried it (I have
AVR32-SoftwareFramework-AT32UC3-1.5.0) but unfortunately my thread still
hangs.

But is is not encouraging that the software frameversion I am using still
contained this error. I wonder whether there might be anymore errors...

Maybe I will do your suggested upgrades, I will you know.


Cordiali saluti
Cristina Marcucci
______________________________
mail to: address@hidden
Tel. +39.02.67493347 (PicoSoft)




-----Messaggio originale-----
Da: address@hidden
[mailto:address@hidden
r conto di Martin Persich
Inviato: Friday, February 12, 2010 2:23 PM
A: Mailing list for lwIP users
Oggetto: Re: [lwip-users] lwip_read hanging and wrong sequence number


Hi,
I had similar problem on AVR32 UC3A with thread "hang-up".
Do you have corrected problem mentioned in
http://lists.gnu.org/archive/html/lwip-users/2009-12/msg00043.html   ?
Only Atmel Software Framework version 1.7 is ok.
Martin


----- Original Message -----
From: "Cristina Marcucci" <address@hidden>
To: <address@hidden>
Sent: Friday, February 12, 2010 12:28 PM
Subject: [lwip-users] lwip_read hanging and wrong sequence number



Hi everybody, I am new to both lwip and lwip-users.

I am using lwip with AVR32 (Atmel AT32UC3A) and have two big problems which
I can reproduce quite easily:

1. My thread reads data with lwip_read (I have set a timeout of 36 seconds
as a socket option, but the problem occurs also without the timeout
directive). After working fine for some time, my thread "hangs" on the
lwip_read, no more data received or a timeout happening. But the incoming
messages are are still being processed and acked at TCP level all the time.
My window size of course shrinks more an more, and finally my receive queue
gets full, proving that my thread is not receiving anylonger. Wireshark
trace attached.

2. In a different scenario, after running fine for some time, my application
sends a wrong sequence number. Wireshark trace attached.

Can anybody please help me?

Thank you and best regrads
cristina



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





reply via email to

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