From owner-freebsd-current@FreeBSD.ORG  Sun Dec 14 15:26:17 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D287C16A4CE
	for <freebsd-current@FreeBSD.ORG>;
	Sun, 14 Dec 2003 15:26:17 -0800 (PST)
Received: from mailhost3.mistral.co.uk (mailhost3.mistral.co.uk
	[217.154.131.6])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 97E8943D33
	for <freebsd-current@FreeBSD.ORG>;
	Sun, 14 Dec 2003 15:26:16 -0800 (PST)
	(envelope-from simoncurrent@mistral.co.uk)
Received: from localhost.localdomain
	(host81-128-183-123.in-addr.btopenworld.com [81.128.183.123])
	by mailhost3.mistral.co.uk (Postfix) with ESMTP id 08E27DA0E2
	for <freebsd-current@FreeBSD.ORG>;
	Sun, 14 Dec 2003 23:26:15 +0000 (GMT)
From: Simon Loader <simoncurrent@mistral.co.uk>
To: freebsd-current@FreeBSD.ORG
In-Reply-To: <200312142213.hBEMDI3Q099167@spider.deepcore.dk>
References: <200312142213.hBEMDI3Q099167@spider.deepcore.dk>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Ximian Evolution 1.0.5 
Date: 14 Dec 2003 23:26:15 +0000
Message-Id: <1071444376.436.8.camel@madoka>
Mime-Version: 1.0
Subject: Re: RTL8139C+ re driver watchdog timeout
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 14 Dec 2003 23:26:17 -0000

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