From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 06:10:02 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 2265016A4CE for ; Wed, 29 Sep 2004 06:10:02 +0000 (GMT) Received: from smtp1.adl2.internode.on.net (smtp1.adl2.internode.on.net [203.16.214.181]) by mx1.FreeBSD.org (Postfix) with ESMTP id 79B9243D46 for ; Wed, 29 Sep 2004 06:10:01 +0000 (GMT) (envelope-from smckay@internode.on.net) Received: from dungeon.home (ppp238-227.lns1.bne3.internode.on.net [203.122.238.227])i8T69x4Y017040; Wed, 29 Sep 2004 15:39:59 +0930 (CST) Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.12.8p2/8.11.6) with ESMTP id i8T69wZD008877; Wed, 29 Sep 2004 16:09:58 +1000 (EST) (envelope-from mckay) Message-Id: <200409290609.i8T69wZD008877@dungeon.home> To: current@freebsd.org References: <002b01c4a576$9b65f1d0$82fda3d1@sanmarcos.x25.net> <200409282025.04107.taras-s-y@mail.ru> In-Reply-To: <200409282025.04107.taras-s-y@mail.ru> from Savchuk Taras at "Tue, 28 Sep 2004 20:25:03 +0000" Date: Wed, 29 Sep 2004 16:09:58 +1000 From: Stephen McKay cc: Savchuk Taras 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 06:10:02 -0000 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? 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.