Bug 53920

Summary: [bge] sluggish TCP connection
Product: Base System Reporter: ktso <ktso>
Component: kernAssignee: Andre Oppermann <andre>
Status: Closed FIXED    
Severity: Affects Only Me CC: ktso
Priority: Normal    
Version: 5.1-RELEASE   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
dumpfile2 none

Description ktso 2003-06-30 10:20:19 UTC 
	The FreeBSD server 137.189.192.36 is connected to Internet using the builtin Broadcom GE NIC.  So, the bge driver is used.  We are running an INN server and we used another news server to feed a large batch of old news into it.  We notice that the TCP connection is sometimes sluggish.  Further investigation showed that the machine is still pingable and new TCP connection can be established when those existing TCP connection become sluggish for a few seconds.  You may have a look at the attached tcpdump file.  I have telnet to the remote host 137.189.192.36 from 137.189.28.103.  I have tried to type the string "abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrst" when the TCP connection is sluggish.  Those characters "abcdef..." are not echoed immediately.  However, ACK was sent immediately after each character is received by the remote host.  When the news feeding is stopped, the TCP connections were no longer sluggish.  We have similar problem in FreeBSD 4.5.  The problem was m!
 ore serious and we can find messages like "watchdog timeout" from the log.

How-To-Repeat: 	Feed a batch of news articles to the FreeBSD server with Broadcom GE NIC.  Then monitor any TCP connection like SSH, telnet, etc.  Sometimes the problem does not exist after the machine is warmed up.  After a reboot, the problem happen again.
Comment 1 Andre Oppermann freebsd_committer freebsd_triage 2003-12-27 16:46:51 UTC 
Responsible Changed
From-To: freebsd-bugs->andre

Take over.
Comment 2 Andre Oppermann freebsd_committer freebsd_triage 2003-12-30 12:36:26 UTC 
State Changed
From-To: open->feedback

Problem believed to be fixed.  Asked Originator to recheck.
Comment 3 oppermann 2003-12-30 12:36:33 UTC 
So,

could you please check again with 5.2RC2 or -CURRENT?

This problem is believed to be fixed in sys/dev/bge/if_bge.c rev 1.49
on Aug.10 2003.

-- 
Andre
Comment 4 ktso 2004-01-02 10:16:16 UTC 
Dear Andre,

Though the innd is not so stable after upgrading to 5.2RC2 (it switched to the
state vmpfw finally), I can still manage to run a casual test.  As
before, I use another news server to feed news to this server.  Then I
ssh to it and run 'top' that refresh every 2 sec.  I can notice that the
screen is sometimes frozen.  However, the symptom is improved a little
bit already.  Thanks for your work.

Regards,
So K T, CUHK

On Tue, Dec 30, 2003 at 01:36:33PM +0100, Andre Oppermann wrote:
> So,
> 
> could you please check again with 5.2RC2 or -CURRENT?
> 
> This problem is believed to be fixed in sys/dev/bge/if_bge.c rev 1.49
> on Aug.10 2003.
> 
> -- 
> Andre
Comment 5 Remko Lodder freebsd_committer freebsd_triage 2006-11-26 20:23:44 UTC 
State Changed
From-To: feedback->open

Steal this PR from Andre to request additional feedback;
Comment 6 Remko Lodder freebsd_committer freebsd_triage 2006-11-26 20:24:40 UTC 
State Changed
From-To: open->feedback

Request for feedback: Dear submitter, a lot had been changed 
in the bge code by andre and others, can you please check 
whether this problem had been resolved all together now 
or? 

If there is no feedback; we need to close the PR due to 
lack of recent information.
Comment 7 Mark Linimon freebsd_committer freebsd_triage 2007-05-13 05:25:44 UTC 
State Changed
From-To: feedback->closed

Feedback timeout.