From owner-freebsd-current@FreeBSD.ORG Wed Sep 29 06:20:18 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 E534116A4CE for ; Wed, 29 Sep 2004 06:20:17 +0000 (GMT) Received: from mail.au.sevenone.com (ppp53-126.lns1.adl2.internode.on.net [150.101.53.126]) by mx1.FreeBSD.org (Postfix) with ESMTP id D25F243D2F for ; Wed, 29 Sep 2004 06:20:16 +0000 (GMT) (envelope-from freebsd@sevenone.com) Received: from email.sevenone.com (bsd2.au.sevenone.com [202.12.71.2]) i8T6KF31091578 for ; Wed, 29 Sep 2004 15:50:15 +0930 (CST) (envelope-from freebsd@sevenone.com) Received: from 143.216.237.212 (SquirrelMail authenticated user matt); by email.sevenone.com with HTTP; Wed, 29 Sep 2004 15:50:15 +0930 (CST) Message-ID: <50228.143.216.237.212.1096438815.squirrel@143.216.237.212> Date: Wed, 29 Sep 2004 15:50:15 +0930 (CST) From: "matt baker" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.3a X-Mailer: SquirrelMail/1.4.3a MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal 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:20:18 -0000 >>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. I am also seeing this error. Was seeing it originally in 5.2.1 and now with 5.3-Beta6. Hope I can help find the problem. With both I was seeing "dc0: failed to force tx and rx to idle state" with 5.3-Beta6 I am also now seeing "dc0: watchdog timeout" dmesg | grep dc0 output: dc0: <82c169 PNIC 10/100BaseTX> port 0x9400-0x94ff mem 0xeb200000-0xeb2000ff irq 17 at device 9.0 on pci0 miibus1: on dc0 dc0: Ethernet address: 00:02:e3:06:a1:8b dc0: [GIANT-LOCKED] I will try the patch above and see if it helps or not. Regards, Matt