New Release 2.5.3 - still Beta after 12 weeks?

[greengene]

is anyone using this yet?

any comments on it?

[joepasquariello]

We are using 2.5.3 because of TCP issues in 2.5.2. We had issues with SB70LC modules getting lost somewhere in the TCP code. See the 2.5.3 release notes for a list of the issues, but the line that caught my eye was this one:

- TCP errors in Release 2.5.2 are significant and can (cause) the TCP stack and/or user tasks to permanently hang up.

So far so good with 2.5.3. We made our first release a week ago, and it seems to have solved our problems.

Joe

[greengene]

thanks, joe. as i posted to the beta release announcement above,
that is also our biggest concern.

my mgmt would be a lot happier(?) to roll out this upgrade if it became
NB's official release, so I'm just gonna have to see how long they will
hold out with customer complaints coming in daily now.

i haven't had the recurrence with 2.5.3 here but the problem(s) are
definitely network configuration and activity dependent at customer sites.

my/our fingers are crossed...

[seulater]

I have been using it since it release with no issues.

[tod]

I have been using it for several weeks on a MOD5272. It seems very stable but I have seen one non-repeatable anomaly where I'll get a keep alive error and after that even Auto Update can't find the board. I have to reset the board and then all is well. Too early to say if it's a NB issue, or my code or possibly my PC.

EDIT FOLLOWUP: I replaced the MOD5272 and haven't seen the problem since.

[greengene]

ooooooh!

please let me/us know if/when you run this to ground.

[Forrest]

Hello,

We have been shipping 2.5.3 with new kits, so I guess that qualifies it as out of beta. I'll update the status on the support site to reflect this. Mac beta is ready to go and will replace the current beta on monday or tuesday next week.

[joepasquariello]

hi forrest,

can you tell us anything about what types of TCP activity trigger the issues in 2.5.2. The reason I ask is that although we're doing well with 2.5.3, we obviously need to improve our test procedures. Our bench tests did not show problems with 2.5.2, but our customers began having problems almost immediately.

joe

[greengene]

We shipped a new product release last week for field-upgrade for a couple of customers
that had been complaining about TCP problems. The only changes were rebuilding
with 2.5.3 and a little more stroking of the h/w watchdog. So far, no complaints . . .