From owner-freebsd-current@FreeBSD.ORG Wed Oct 6 17:35:25 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 C34B716A4D3 for ; Wed, 6 Oct 2004 17:35:25 +0000 (GMT) Received: from tron.telenetwork.com (tron.telenetwork.com [204.57.81.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id BF13343D5A for ; Wed, 6 Oct 2004 17:35:10 +0000 (GMT) (envelope-from jmarquez@x25.net) Received: from [209.163.253.130] (helo=tni1411) by tron.telenetwork.com with esmtp (Exim 3.35 #1 (Debian)) id 1CFFh0-0006oK-00; Wed, 06 Oct 2004 12:35:10 -0500 From: "Jesse Marquez" To: "'Stephen McKay'" , Date: Wed, 6 Oct 2004 12:35:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 In-Reply-To: <200409290609.i8T69wZD008877@dungeon.home> Thread-Index: AcSl6w3DRMDyIG+zT6u4NBo7BzmJFAF36eKQ Message-Id: cc: 'Savchuk Taras' 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, 06 Oct 2004 17:35:26 -0000 Was anyone able to get this to work? Over and out jesse -----Original Message----- From: owner-freebsd-current@freebsd.org [mailto:owner-freebsd-current@freebsd.org] On Behalf Of Stephen McKay Sent: Wednesday, September 29, 2004 12:10 AM To: current@freebsd.org Cc: Savchuk Taras; Stephen McKay Subject: Re: dc0 acting up 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. _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"