Date: Wed, 29 Sep 2004 16:01:58 -0500 From: jesse marquez <jmarquez@telenetwork.com> To: Savchuk Taras <taras-s-y@mail.ru> Cc: Stephen McKay <smckay@internode.on.net> Subject: Re: dc0 acting up Message-ID: <415B22C6.3010403@telenetwork.com> In-Reply-To: <200409300018.14616.taras-s-y@mail.ru> References: <002b01c4a576$9b65f1d0$82fda3d1@sanmarcos.x25.net> <200409282025.04107.taras-s-y@mail.ru> <200409290609.i8T69wZD008877@dungeon.home> <200409300018.14616.taras-s-y@mail.ru>
index | next in thread | previous in thread | raw e-mail
Savchuk Taras wrote:
>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.
>>
>>
>
>
>
dc0: <82c169 PNIC 10/100BaseTX> port 0xd800-0xd8ff mem
0xe3000000-0xe30000ff irq 10 at device 9.0 on pci0
miibus0: <MII bus> on dc0
bmtphy0: <BCM5201 10/100baseTX PHY> on miibus0
bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
dc0: Ethernet address: 00:a0:cc:d6:92:ae
dc0: [GIANT-LOCKED]
I'm receiving the same error messege while trying to compile. Hmmm,
maybe we are commenting the wrong thing?
over and out
jesse
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?415B22C6.3010403>