From owner-freebsd-stable@FreeBSD.ORG Mon Jan 5 07:23:49 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0FA916A4CE for ; Mon, 5 Jan 2004 07:23:49 -0800 (PST) Received: from mercury.jorsm.com (mercury.jorsm.com [66.170.168.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 305C743D1D for ; Mon, 5 Jan 2004 07:23:48 -0800 (PST) (envelope-from steveb@mercury.jorsm.com) Received: from localhost (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 9B2FB1E1943; Mon, 5 Jan 2004 09:23:47 -0600 (CST) Received: from mercury.jorsm.com (localhost [127.0.0.1]) by localhost (VaMailArmor-2.0.1.16) id 04023-46C4697A; Mon, 05 Jan 2004 09:23:47 -0600 Received: by mercury.jorsm.com (Postfix, from userid 4147) id 75BAB1E193E; Mon, 5 Jan 2004 09:23:47 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mercury.jorsm.com (Postfix) with ESMTP id 743831E193C; Mon, 5 Jan 2004 09:23:47 -0600 (CST) Date: Mon, 5 Jan 2004 09:23:47 -0600 (CST) From: Stephen Bader To: Clint Gilders In-Reply-To: <3FF98026.8070802@onlinehobbyist.com> Message-ID: <20040105092029.Y75732-100000@mercury.jorsm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.23.0.2; VDF: 6.23.0.25; host: jorsm.com) cc: freebsd-stable@freebsd.org Subject: Re: /kernel: em0: Link is Down X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Jan 2004 15:23:49 -0000 Just to verify, I would assume you've checked the following?: - Bad Cable - May not have appeared until it got loaded - Auto Negotiate Issues (check duplex) - Very common - Force to 10mbps to see if it still happens - For to half duplex in both 10 & 100 mbps - Different physical port on the switch I haven't seen any issues on this list with the em driver, but I may be wrong. I don't have em cards, so other than the above, I can't offer much. -Steve ------------------------------------------------------------------------- Stephen Bader JORSM Internet, Regional Internet Services Systems Administrator 7 Area Codes in Chicagoland and NW Indiana steveb@jorsm.com 100Mbps+ Connectivity, 56K-DS3, V.90, ISDN (219) 322-2180 Quality Service, Affordable Prices http://www.jorsm.com Serving Gov, Biz, Indivds Since 1995 ------------------------------------------------------------------------- On Mon, 5 Jan 2004, Clint Gilders wrote: > Hi > > I'm seeing a lot of the error messages below on a dual Xeon 2.5 Ghz running 4.9-STABLE > built on Wed Nov 26 2003. The errors started when I moved a fairly busy database to this > server. > > Jan 4 17:56:50 king7 /kernel: em0: Link is up 100 Mbps Full Duplex > Jan 4 19:04:18 king7 /kernel: em0: Link is Down > Jan 4 19:04:20 king7 /kernel: em0: Link is up 100 Mbps Full Duplex > Jan 4 23:59:06 king7 /kernel: em0: Link is Down > Jan 4 23:59:08 king7 /kernel: em0: Link is up 100 Mbps Full Duplex > Jan 5 01:04:48 king7 /kernel: em0: Link is Down > Jan 5 01:04:50 king7 /kernel: em0: Link is up 100 Mbps Full Duplex > > I found menton of changing '#define EM_REPORT_TX_EARLY 0' to '#define EM_REPORT_TX_EARLY > 1' in /usr/src/sys/dev/em/if_em.h but my if_em.h doesn't have this line > > Anyone have any suggestions on how to remedy this? Is this a known problem that would > have been fixed since my system was compiled in November? > > Thanks > -- > Clint Gilders > Director of Technology Services > OnlineHobbyist.com, Inc. > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >