[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5F14EEE91CB6694A86535A0A028D9C55016AEDF2@tx14exm60.ds.mot.com>
Date: Tue, 1 May 2007 15:09:07 -0500
From: "Isaula Oscar-QOI000" <Oscar.Isaula@...orola.com>
To: "Vlad Yasevich" <vladislav.yasevich@...com>,
<netdev@...r.kernel.org>
Subject: RE: [SCTP] Initialization collision problem
Vlad,
I finally got test results for the changes you suggested. The original
issue is fixed and I have not detected any side effects.
Thanks,
Oscar
-----Original Message-----
From: netdev-owner@...r.kernel.org [mailto:netdev-owner@...r.kernel.org]
On Behalf Of Vlad Yasevich
Sent: Wednesday, April 11, 2007 9:45 AM
To: Isaula Oscar-QOI000
Cc: netdev@...r.kernel.org; linux-kernel@...r.kernel.org
Subject: Re: [SCTP] Initialization collision problem
Hi Oscar
Isaula Oscar-QOI000 wrote:
> I ran into a problem where LKSCTP is reporting a SCTM_COMM_UP
> indication to the User application but is giving back a value of zero
> for the assoc_id.
>
> Attached are the SCTP debugs for the period in question.
>
> A couple of things that I would like to note about my setup. One is
> that I'm running Kernel version 2.6.10 (I know is old but I can't move
> to a newer version due to custom drivers). The second thing is that
> the link between the two SCTP node is a very noisy and some messages
> are getting lost (i.e. the INIT_ACK from the peer in this particular
case).
>
Can you give this patch a try and let me know if this fixes your issue?
Thanks
-vlad
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists