Date: Wed, 29 Sep 2004 16:09:58 +1000 From: Stephen McKay <smckay@internode.on.net> To: current@freebsd.org Cc: Stephen McKay <smckay@internode.on.net> Subject: Re: dc0 acting up Message-ID: <200409290609.i8T69wZD008877@dungeon.home> In-Reply-To: <200409282025.04107.taras-s-y@mail.ru> from Savchuk Taras at "Tue, 28 Sep 2004 20:25:03 %2B0000" References: <002b01c4a576$9b65f1d0$82fda3d1@sanmarcos.x25.net> <200409282025.04107.taras-s-y@mail.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200409290609.i8T69wZD008877>