Hello!
Since I upgraded to kernel 2.2.19 RHSA-2001:047-03, the tsm-client
ceased to work, it runs nicely for about two minutes, but then it
suddenly becomes *very* slow (1MB/5minutes).

---stdout-------------
ANS1809E Session is lost; initializing session reopen procedure.
ANS1809E Session is lost; initializing session reopen procedure.
A Reconnection attempt will be made in 00:00:14 ... successful
Normal File-->        23.810.250 /home/rds/mail/saved-messages  ** Unsuccessful 
**

ANS1809E Session is lost; initializing session reopen procedure.
A Reconnection attempt will be made in 00:00:14 ... successful
Retry # 1  Normal File-->        23.810.250 /home/rds/mail/saved-messages  ** 
Unsuccessful **
----------------------
-------error log------
-------error log------
2001-05-01 13:25:51 TcpRead: Zero byte buffer read.
2001-05-01 13:25:51 TcpRead: Zero byte buffer read.
2001-05-01 13:25:51 sessRecvVerb: Error -50 from call to 'readRtn'.
2001-05-01 13:25:51 cuConfirm: Received rc: -50 trying to receive ConfirmResp 
verb
2001-05-01 13:25:51 ANS1809E Session is lost; initializing session reopen 
procedure.
2001-05-01 13:25:51 ANS1809E Session is lost; initializing session reopen 
procedure.
2001-05-01 13:26:06 ANS1810E TSM session has been reestablished.
2001-05-01 13:30:05 TcpFlush: Error 32 sending data on Tcp/Ip socket 7.
2001-05-01 13:30:05 sessSendVerb: Error sending Verb, rc: -50
2001-05-01 13:30:05 TcpFlush: Error 32 sending data on Tcp/Ip socket 7.
----------------------
---logfile on tsm-server---------------------------
---logfile on tsm-server---------------------------
04/22/2001 02:43:42  ANR0481W Session 10621 for node XXXXXXXXXXXXXXXXXXXXXXXXX
04/22/2001 02:43:42  ANR0481W Session 10621 for node XXXXXXXXXXXXXXXXXXXXXXXXX
                      (Linux86) terminated - client did not respond within 180
                      seconds.
---------------------------------------------------
System Information
System Information
RH Linux 6.2+Updates
TSM-Client 3.7.2.0-1. The upgrade to 4.1.2-1 did not help.
I have not noticed any other network problems, the filesystems to
backup are ext2.
                cu andreas