From nobody  Wed Jan 27 21:36:52 1999
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id VAA15228;
          Wed, 27 Jan 1999 21:36:52 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199901280536.VAA15228@hub.freebsd.org>
Date: Wed, 27 Jan 1999 21:36:52 -0800 (PST)
From: spam@sporty.org
To: freebsd-gnats-submit@freebsd.org
Subject: tx driver for smc autodetects fine, but network comes up only after 1 packet is sent outbound
X-Send-Pr-Version: www-1.0

>Number:         9742
>Category:       kern
>Synopsis:       tx driver for smc autodetects fine, but network comes up only after 1 packet is sent outbound
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jan 27 21:40:01 PST 1999
>Closed-Date:    Wed Apr 12 15:21:47 PDT 2000
>Last-Modified:  Wed Apr 12 15:22:56 PDT 2000
>Originator:     spencer portee
>Release:        3.0-CURRENT
>Organization:
yard productions
>Environment:
FreeBSD real.yrd.com 3.0-STABLE FreeBSD 3.0-STABLE #1: Thu Jan 28 04:22:01 GMT 1999     root@in.progress.yrd.com:/usr/src/sys/compile/GENERIC  i386
>Description:
using a catalyst cisco switch an an smc nic, the negotiation to full duplex on behalf of the freebsd driver side (switch is configured to do 100-fulld-duplex set), the line status is up, the network is down until any tcpip packet is sent.
>How-To-Repeat:
setup like above, boot up and watch
>Fix:
TEMP. FIX:
in rc.local, put a ping -c 10 -i 60 to somewhere, that will start up the network as a temporary fix
>Release-Note:
>Audit-Trail:

From: Bill Fumerola <billf@jade.chc-chimes.com>
To: spam@sporty.org
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/9742: tx driver for smc autodetects fine, but network comes up only after 1 packet is sent outbound
Date: Thu, 28 Jan 1999 09:47:09 -0500 (EST)

 On Wed, 27 Jan 1999 spam@sporty.org wrote:
 
 > >Synopsis:       tx driver for smc autodetects fine, but network comes up only after 1 packet is sent outbound
 I am experiencing similar funkyness with the fxp driver. The NIC refuses
 connections until there is activity on my other (xl) card.
 
 Wierd.
 
 - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp -
 - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org  -
 
 
 

From: sporty <sporty@sporty.org>
To: Bill Fumerola <billf@jade.chc-chimes.com>
Cc: spam@sporty.org, freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/9742: tx driver for smc autodetects fine, but network comes
 up only after 1 packet is sent outbound
Date: Thu, 28 Jan 1999 17:50:09 -0500 (EST)

 is something being planned about this?  
 
 On Thu, 28 Jan 1999, Bill Fumerola wrote:
 
 > On Wed, 27 Jan 1999 spam@sporty.org wrote:
 > 
 > > >Synopsis:       tx driver for smc autodetects fine, but network comes up only after 1 packet is sent outbound
 > I am experiencing similar funkyness with the fxp driver. The NIC refuses
 > connections until there is activity on my other (xl) card.
 > 
 > Wierd.
 > 
 > - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp -
 > - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org  -
 > 
 > 
 > 
 > 
 

From: Sheldon Hearn <sheldonh@iafrica.com>
To: spencer portee <spam@sporty.org>
Cc: Bill Fumerola <billf@jade.chc-chimes.com>,
	freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/9742: tx driver for smc autodetects fine, but network comes up only after 1 packet is sent outbound
Date: Thu, 11 Mar 1999 14:02:05 +0200

 Hi Spencer,
 
 I'd appreciate it if you'd let me know whether the fix introduced into
 CURRENT for the tx driver on 1999/03/09 fixed the problem you reported
 in PR9742, viewable at
 
 	http://www.freebsd.org/cgi/query-pr.cgi?pr=9742
 
 Thanks,
 Sheldon.
 
State-Changed-From-To: open->closed 
State-Changed-By: semenu 
State-Changed-When: Wed Apr 12 15:21:47 PDT 2000 
State-Changed-Why:  
Fixed. 
>Unformatted:
