From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 28 16:34:17 2004 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EE57A16A4CE for ; Sun, 28 Mar 2004 16:34:17 -0800 (PST) Received: from web21502.mail.yahoo.com (web21502.mail.yahoo.com [66.163.169.13]) by mx1.FreeBSD.org (Postfix) with SMTP id C9D7C43D3F for ; Sun, 28 Mar 2004 16:34:17 -0800 (PST) (envelope-from non_secure@yahoo.com) Message-ID: <20040329003417.13842.qmail@web21502.mail.yahoo.com> Received: from [67.174.190.163] by web21502.mail.yahoo.com via HTTP; Sun, 28 Mar 2004 16:34:17 PST Date: Sun, 28 Mar 2004 16:34:17 -0800 (PST) From: Joe Schmoe To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: em0 is still broken - watchdog timeouts, lockups ... workaround please X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Mar 2004 00:34:18 -0000 System is a very vanilla 4.9-RELEASE with fxp and em built into the kernel. It is a dual processor machine with two 550mhz p3s. Its kernel config is very sparse - all USB and pcmcia, etc. have been removed - the only items of note are symbios scsi support, and support for twe (my 3ware IDE raid card). The string acpi/ACPI does not appear in my kernel config file, thanks for asking. Boot up the machine using em0 ... it continually spits out: Jan 4 14:56:50 die /kernel: em0: Link is up 100 Mbps Full Duplex Jan 4 15:04:18 die /kernel: em0: Link is Down Jan 4 15:04:20 die /kernel: em0: Link is up 100 Mbps Full Duplex Jan 4 25:59:06 die /kernel: em0: Link is Down and if I do any kind of file transfer with it, I will get flooded with watchdog timeout errors. Oh, and the machine will lock up at that point as well - no longer pingable. I am happy for a workaround - there are several posts in the archives that mention: changing '#define EM_REPORT_TX_EARLY 0' to '#define EM_REPORT_TX_EARLY 1' in /usr/src/sys/dev/em/if_em.h HOWEVER, my if_em.h does not contain that line, so it is not possible to change it. Further, as this is 4.9-RELEASE, I also do not have that tunable sysctl for em0 either that some folks suggest should be set to zero. So .. is there a workaround ? And further, is Intel dragging their feet on releasing some information on this card, or blocking freebsd-licensed versions of drivers that fix this problem ? I am trying to think of some plausible reason as to why this has been broken _for years_ and never fixed. Search the archives and you will find people complaining about this (specifically on dual cpu systems) as far back as 2002. Help appreciated. __________________________________ Do you Yahoo!? Yahoo! Finance Tax Center - File online. File on time. http://taxes.yahoo.com/filing.html