From owner-freebsd-stable@FreeBSD.ORG Thu Dec 2 01:42:49 2010 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CDD511065693 for ; Thu, 2 Dec 2010 01:42:49 +0000 (UTC) (envelope-from karl@denninger.net) Received: from FS.denninger.net (wsip-70-169-168-7.pn.at.cox.net [70.169.168.7]) by mx1.freebsd.org (Postfix) with ESMTP id 869828FC12 for ; Thu, 2 Dec 2010 01:42:49 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) by FS.denninger.net (8.14.4/8.13.1) with ESMTP id oB21gnIn002685 for ; Wed, 1 Dec 2010 19:42:49 -0600 (CST) (envelope-from karl@denninger.net) Received: from [127.0.0.1] [192.168.1.40] by Spamblock-sys (LOCAL); Wed Dec 1 19:42:49 2010 Message-ID: <4CF6F947.4000803@denninger.net> Date: Wed, 01 Dec 2010 19:41:27 -0600 From: Karl Denninger User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <4CF6E41F.8060101@denninger.net> <20101202004447.GD8893@michelle.cdnetworks.com> In-Reply-To: <20101202004447.GD8893@michelle.cdnetworks.com> X-Enigmail-Version: 1.1.1 Content-Type: multipart/mixed; boundary="------------050702000301090009000000" X-Antivirus: avast! (VPS 101201-1, 12/01/2010), Outbound message X-Antivirus-Status: Clean X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Uh, fxp driver broken in current -STABLE build?! X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Dec 2010 01:42:49 -0000 This is a multi-part message in MIME format. --------------050702000301090009000000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 12/1/2010 6:44 PM, Pyun YongHyeon wrote: > On Wed, Dec 01, 2010 at 06:11:11PM -0600, Karl Denninger wrote: >> Works in this kernel, checked out on that day: >> >> FreeBSD 8.1-STABLE #10: Mon Aug 30 06:44:40 CDT 2010 >> karl@FS.denninger.net:/usr/obj/usr/src/sys/KSD-SMP >> >> fxp0: port 0x1000-0x101f mem >> 0x94000000-0x94000fff,0x94100000-0x941fffff irq 21 at device 0.0 on pci6 >> fxp0: Enabling Rx lock-up workaround >> miibus0: on fxp0 >> fxp0: Ethernet address: 00:a0:c9:a4:78:c3 >> fxp0: [ITHREAD] >> >> (and has been running for months, and for a very long time before that) >> >> Tried to update to today's check-out and got hosed. >> >> The driver now keeps resetting and sending out "down" and "up" messages >> repeatedly, and no traffic flows.... >> >> This is the ident I have on the current build: >> >> fxp0: port 0x1000-0x101f mem >> 0x94000000-0x94000fff,0x94100000-0x941fffff irq 21 at device 0.0 on pci6 >> fxp0: Enabling Rx lock-up workaround >> miibus0: on fxp0 >> fxp0: Ethernet address: 00:a0:c9:a4:78:c3 >> fxp0: [ITHREAD] >> >> Looks the same..... >> >> Something was touched though on Nov 30 in the CVS tree. >> >> It looks like there was a fairly serious commit posted on 10-15, and >> some other smaller ones related to VLANs and flow control (which don't >> apply to this configuration.) >> >> I can't find anything else related...... anyone know what's up here? >> >> Probably need to find this as we're going into the 8.2 RELEASE cycle..... >> >> DMESG from the failed kernel boot is attached. >> > Thanks for reporting. Try attached patch. It seems there is a bug > in RX lockup detection logic. Your controller is known to RX > lockup free so the workaround should not be enabled. Otherwise > fxp(4) reinitializes the controller every 15 seconds. > > > _______________________________________________ > 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" The patch was successful. I have another problem with the new kernel in that it is not properly blocking on reads from an attached GPS (NTPD) but I'll see what I can find out there and update as necessary. This probably needs to be committed so it doesn't bite other people. -- Karl --------------050702000301090009000000--