Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Dec 2003 09:44:35 +0800
From:      Deng XueFeng <dsnofe@hotmail.com>
To:        freebsd-current@freebsd.org
Subject:   Re: RTL8139C+ re driver watchdog timeout
Message-ID:  <20031215094410.AC7D.DSNOFE@hotmail.com>
In-Reply-To: <1071444376.436.8.camel@madoka>
References:  <200312142213.hBEMDI3Q099167@spider.deepcore.dk> <1071444376.436.8.camel@madoka>

next in thread | previous in thread | raw e-mail | index | archive | help
The same with me. 
but when remove media and mediaopt set.  it's seems work right.
timeouts not appear frequently.
> On Sun, 2003-12-14 at 22:13, Soren Schmidt wrote:
> > It seems Russell Jackson wrote:
> > > Ever since 8139C+ support was seperated from the rl driver into the re 
> > > driver, I have had timeout problems. The interface simply stops 
> > > responding randomly. I never had this problem with the rl driver. At 
> > > first I thought this might be do to ACPI not initializing the NIC 
> > > correctly, but I have the same problem with ACPI disabled. Ifconfig 
> > > doesn't correctly display media status either. It shows media (none) 
> > > even though a cable is connected, and the interface will work (however 
> > > with the timeout problem).
> > > 
> > > re0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> > >         options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
> > >         inet 192.168.0.4 netmask 0xffffff00 broadcast 192.168.0.255
> > >         ether 00:08:02:d0:21:4e
> > >         media: Ethernet 100baseTX <full-duplex> (none)
> > > 
> > > Note that I set the media type and mediaopt manually with ifconfig. It 
> > > still shows a status of none.
> > > 
> > > Also note that this same hardware did work perfectly before with the old 
> > > rl driver.
> > 
> > Just a "me too" entry here, I've put an ifconfig down/up in crontab
> > every minute, that seems to keep the interface up :)
> 
> 
> yes another me too with a bit more info
> 
> But I can get this to happen almost every time with a cvsup. (this is
> current). 
> 
> What happens is it eventually the chip must stop responding or the code
> is not removing mbufs correctly as sc->rl_ldata.rl_tx_free <= 4 in
> re_encap causes it to stop.
> 
> HTH
> 
> 
> -- 
> Simon Loader 
> 
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"


Sincerely,
XueFeng Deng
----------------------------------------
MSN  Messenger: dsnofe@hotmail.com
Yahoo Messager: dsnofe@yahoo.com.cn
----------------------------------------




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031215094410.AC7D.DSNOFE>