From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 20:18:20 2004 Return-Path: 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 7C02316A4CE for ; Wed, 29 Sep 2004 20:18:20 +0000 (GMT) Received: from mx2.mail.ru (mx2.mail.ru [194.67.23.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id 30A9D43D41 for ; Wed, 29 Sep 2004 20:18:20 +0000 (GMT) (envelope-from taras-s-y@mail.ru) Received: from [195.128.97.122] (port=65255 helo=taras.gznet.ru) by mx2.mail.ru with asmtp id 1CCku3-0001iL-00; Thu, 30 Sep 2004 00:18:19 +0400 From: Savchuk Taras Organization: msu To: freebsd-current@freebsd.org Date: Thu, 30 Sep 2004 00:18:14 +0000 User-Agent: KMail/1.7 References: <002b01c4a576$9b65f1d0$82fda3d1@sanmarcos.x25.net> <200409282025.04107.taras-s-y@mail.ru> <200409290609.i8T69wZD008877@dungeon.home> In-Reply-To: <200409290609.i8T69wZD008877@dungeon.home> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1251" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200409300018.14616.taras-s-y@mail.ru> X-Spam: Not detected cc: Stephen McKay Subject: Re: dc0 acting up X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Sep 2004 20:18:20 -0000 On Wednesday 29 September 2004 06:09, Stephen McKay wrote: > On Tuesday, 28th September 2004, Savchuk Taras wrote: > >On Tuesday 28 September 2004 16:17, Jesse Marquez wrote: > > > >FreeBSD5.3-BETA4 > > > >I have the same output during boot: > >> dc0: failed to force tx and rx to idle state > >> dc0: failed to force tx and rx to idle state > >> dc0: failed to force tx and rx to idle state > > This one comes up every year or so and is my fault (more or less). > Maybe we can fix it now that people are reporting it, even though it > is actually pretty harmless. > > What hardware do you have? Ie what other dc0: lines do you find in dmesg? > > If you are willing to edit some code and try again, what happens when > you comment out the entire for loop at line 1379 of sys/pci/if_dc.c, which > looks like this: > > for (i = 0; i < DC_TIMEOUT; i++) { > isr = CSR_READ_4(sc, DC_ISR); > if (isr & DC_ISR_TX_IDLE && > ((isr & DC_ISR_RX_STATE) == DC_RXSTATE_STOPPED > || (isr & DC_ISR_RX_STATE) == DC_RXSTATE_WAIT)) break; > DELAY(10); > } > > if (i == DC_TIMEOUT) > printf("dc%d: failed to force tx and " > "rx to idle state\n", sc->dc_unit); > > Does your network card still work? I have made changes in "sys/pci/if_dc.c" as you said and have had this outout during "buildkernel": ------------------------------------------------------------------------------------------------------------------------------------ n-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys/pci/if_dc.c /usr/src/sys/pci/if_dc.c: In function `dc_setcfg': /usr/src/sys/pci/if_dc.c:1369: warning: unused variable `i' /usr/src/sys/pci/if_dc.c:1370: warning: unused variable `isr' *** Error code 1 Stop in /usr/obj/usr/src/sys/T53-B6. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. root@taras.gznet.ru# ------------------------------------------------------------------------------------------------------------------------------------ > > The long story is that this test is probably unnecessary, though the manual > for the original Intel 21143 requires it. If it was skipped for non-Intel > chips, I think everyone would be happy. It would be nice to have some > experimental verification of this theory though. > > Stephen. -- Taras