; Subject: Re: [lwip-users] Problem with long term running of lwIP.
>
> Taranowski, Thomas (SWCOE) wrote:
> > I've been using the tcpip_input mechanism, which I think Frederic
> > introduced awhile back, which looks to be a precursor to the 1.3
> > mechanism, as th
Taranowski, Thomas (SWCOE) wrote:
> I've been using the tcpip_input mechanism, which I think Frederic
> introduced awhile back, which looks to be a precursor to the 1.3
> mechanism, as the ARP handling is done within the context of tcpip(core)
> thread.
Unless you've already fixed it, in that age
PROTECTED]
On
> Behalf Of Goldschmidt Simon
> Sent: Friday, February 29, 2008 3:35 AM
> To: Mailing list for lwIP users
> Subject: RE: [lwip-users] Problem with long term running of lwIP.
>
> > Another possible cause (I have seen this) is that after the ARP
entry
> expi
Kieran Mansley wrote:
> That so many people are seeing this problem is worrying. Can we try and
> establish if there's anything (port, driver, hardware) in common between
> those who have this issue?
>
I don't know what type of tests to perform. First I must find a way to
make error show itself
Taranowski, Thomas (SWCOE)
Sent: Friday, February 29, 2008 5:22 PM
To: Mailing list for lwIP users
Subject: RE: [lwip-users] Problem with long term running of lwIP.
I'm testing with a pro100. We're gathering some data right now, so
hopefully we'll some something interesting :)
AM
> To: Mailing list for lwIP users
> Subject: RE: [lwip-users] Problem with long term running of lwIP.
>
> On Wed, 2008-02-27 at 19:37 -0500, Taranowski, Thomas (SWCOE) wrote:
> > Thanks for the replies. I've added in some statistics collection
code,
> > and am worki
ith long term running of lwIP.> Date: Fri,
> 29 Feb 2008 12:34:40 +0100> From: [EMAIL PROTECTED]> To:
> lwip-users@nongnu.org> > > Another possible cause (I have seen this) is that
> after the ARP entry> expired,> > and the client sends the pbuf chained, got
> Another possible cause (I have seen this) is that after the ARP entry
expired,
> and the client sends the pbuf chained, got queued in ARP layer, an ARP
request
> is sent. As soon the polling thread gets the ARP REPLY, it then
updates the
> table and try to send the queued data (in the thread itse
preemption in the low_level_output.
Just something I found out, hopefully it could be of help to others.
> Subject: RE: [lwip-users] Problem with long term running of lwIP.> From:
> [EMAIL PROTECTED]> To: lwip-users@nongnu.org> Date: Fri, 29 Feb 2008 09:01:59
> +> &g
On Wed, 2008-02-27 at 19:37 -0500, Taranowski, Thomas (SWCOE) wrote:
> Thanks for the replies. I've added in some statistics collection code,
> and am working with my customer to see if we can figure out the problem.
> I'll post any answers I find.
That so many people are seeing this problem is w
Of Caglar Akyuz
> Sent: Wednesday, February 27, 2008 4:34 PM
> To: Mailing list for lwIP users
> Subject: Re: [lwip-users] Problem with long term running of lwIP.
>
> Pettinato, Jim wrote:
> > I've been fighting something that sounds at least similar - at
> > particular c
Pettinato, Jim wrote:
> I've been fighting something that sounds at least similar - at
> particular customer sites - for over a month. For me, it's locking
> up about every 48-60 hours, with a casually polling Modbus
> TCP connection (~ 200 ms between polls) - and lwIP 1.2.0. It requires a
> power
Wednesday, February 27, 2008 5:31 PM
To: Mailing list for lwIP users
Subject: [lwip-users] Problem with long term running of lwIP.
I have an application in which is receiving and sending UDP traffic over
a long-term period. After about 6 hours, something flakes out. I was
hoping I could get som
I have an application in which is receiving and sending UDP traffic over
a long-term period. After about 6 hours, something flakes out. I was
hoping I could get some input on possible causes. Any ideas here on
what the problem could be? Is anyone else having a similar problem?
Other data:
14 matches
Mail list logo
