From owner-freebsd-questions@FreeBSD.ORG Thu Feb 5 22:24:55 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 38EC2106566C for ; Thu, 5 Feb 2009 22:24:55 +0000 (UTC) (envelope-from arab@tangerine-army.co.uk) Received: from smtp-out5.blueyonder.co.uk (smtp-out5.blueyonder.co.uk [195.188.213.8]) by mx1.freebsd.org (Postfix) with ESMTP id DC95E8FC19 for ; Thu, 5 Feb 2009 22:24:54 +0000 (UTC) (envelope-from arab@tangerine-army.co.uk) Received: from [172.23.170.146] (helo=anti-virus03-09) by smtp-out5.blueyonder.co.uk with smtp (Exim 4.52) id 1LVCeT-0002Nw-Pj; Thu, 05 Feb 2009 22:24:53 +0000 Received: from [92.238.154.32] (helo=Mercury.galaxy.lan.lcl) by asmtp-out6.blueyonder.co.uk with esmtp (Exim 4.52) id 1LVCeS-0001ms-Su; Thu, 05 Feb 2009 22:24:53 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Thu, 5 Feb 2009 22:26:13 -0000 Content-class: urn:content-classes:message Message-ID: <01FB8F39BAD0BD49A6D0DA8F78973929562F@Mercury.galaxy.lan.lcl> In-Reply-To: <498A0ECA.2070002@optiksecurite.com> X-MS-Has-Attach: X-MimeOLE: Produced By Microsoft Exchange V6.5 X-MS-TNEF-Correlator: Thread-Topic: Link UP/DOWN problem with re0 on FreeBSD 7.1 Thread-Index: AcmHE2bXik91TWAgQ3qAEbgXtkOftAAzMt0g References: <497DDDB7.4000702@optiksecurite.com><497E07D1.3030604@optiksecurite.com><01FB8F39BAD0BD49A6D0DA8F78973929561F@Mercury.galaxy.lan.lcl><497E24E5.5090701@optiksecurite.com> <498A0ECA.2070002@optiksecurite.com> From: "Graeme Dargie" To: "FreeBSD" Cc: freebsd-questions@freebsd.org Subject: RE: Link UP/DOWN problem with re0 on FreeBSD 7.1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Feb 2009 22:24:55 -0000 -----Original Message----- From: FreeBSD [mailto:freebsd@optiksecurite.com]=20 Sent: 04 February 2009 21:55 Cc: freebsd-questions@freebsd.org Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 FreeBSD a =E9crit : > Graeme Dargie a =E9crit : >> If you do a dmesg are you also showing a watchdog time out for the = nic ? >> >> I only ask as I am having the exact same problem with the exact same=20 >> card and I have yet to find a solution, if I come across something I=20 >> will let you know. >> >> Regards >> Graeme >=20 > Not a single time...sorry. >=20 >> >> -----Original Message----- >> From: FreeBSD [mailto:freebsd@optiksecurite.com] Sent: 26 January = 2009=20 >> 18:58 >> To: freebsd-questions@freebsd.org >> Subject: Re: Link UP/DOWN problem with re0 on FreeBSD 7.1 >> >> FreeBSD a =E9crit : >>> Hi everyone, >>> >>> Just to put you in context, I applied the following patch to make = the=20 >>> card available: >>> >>> SVN rev 186389 on 2008-12-22 00:46:22Z by yongari >>> >>> Since we don't request reset for rlphy(4), the link state 'UP' >>> event from mii(4) may not be delivered if valid link was already >>> established. To address the issue, check current link state after >>> driving MII_TICK. This should fix a regression introduced in >>> r185753 on fast ethernet controllers. >>> >>> --- >>> >>> I don't have any issue related to that anymore. The problem is that = I=20 >>> get link UP/DOWN a few times per hour on 3 identical machines that I = >>> dumped/restored. They are all pluged in a Cisco switch that works=20 >>> fine for every other PCs. >>> >>> Jan 26 06:09:15 term005 kernel: re0: link state changed to DOWN >>> Jan 26 06:09:17 term005 kernel: re0: link state changed to UP >>> >>> I tried to switch cables, but I got the same result. >>> >>> There is the pciconf -lv output: >>> >>> re0@pci0:3:0:0: class=3D0x020000 card=3D0x02831028 chip=3D0x816810ec = >>> rev=3D0x02 hdr=3D0x00 >>> vendor =3D 'Realtek Semiconductor' >>> device =3D 'RTL8168/8111 PCI-E Gigabit Ethernet NIC' >>> class =3D network >>> subclass =3D ethernet >>> >>> There is the output of vmstat -i: >>> >>> interrupt total rate >>> irq18: re0 ehci0++ 63766 0 >>> irq19: atapci0 277001 3 >>> cpu0: timer 156068748 1961 >>> Total 156409515 1966 >>> >>> Could it be related to the fact that there is re0 and ehci0++ on the = >>> same IRQ? >>> >>> Thank you for your help, >>> >>> Martin >> >> I just tried with a brand new Dell 2708 switch and the problem is=20 >> still there. I just confirmed that the UP/DOWN occurs every 10 = minutes=20 >> (+- a few seconds). >> >> Thanks again, >> >> Martin >> Just to follow-up on my own problem... I tried to disable some options of the card with : ifconfig re0 -rxcsum -txcsum -tso -lro -vlanhwtag but nothing as changed. I just tried to download a big file (FreeBSD=20 7.1-REL DVD iso in fact) to see if the deconnection occurs even during a = transfer. The DVD downloaded successfully and I verified that the MD5=20 are OK. BUT, /var/log/messages continue to tell me that: Feb 4 16:09:29 term003 kernel: re0: link state changed to UP Feb 4 16:19:26 term003 kernel: re0: link state changed to DOWN Feb 4 16:19:30 term003 kernel: re0: link state changed to UP Feb 4 16:19:32 term003 kernel: re0: link state changed to DOWN during the transfer (which worked OK). I don't know if that can help=20 someone to help me ;) Thanks, Martin _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to = "freebsd-questions-unsubscribe@freebsd.org" I have a solution to this well a work around. Add -tso to the relevant line in /etc/rc.conf ifconfig_re0=3D"inet 192.168.1.103 netmask 255.255.255.0 -tso" Adding -tso stops the link up / link down problem. Now I am understand = that this may increase cpu if the traffic on the nic is high. I am sure = some one the list will know of any other implications this may have. It is a known problem and I site I read the bug had been submitted so = hopefully it wont exist in 8.0=20 Regards Graeme