Re: dc0 acting up

From: Savchuk Taras (taras-s-y_at_mail.ru)
Date: 09/30/04

  • Next message: Dieter Franzke: "Re: usb compile issue"
    To: freebsd-current@freebsd.org
    Date: Thu, 30 Sep 2004 00:18:14 +0000
    
    

    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.

    -- 
    Taras
    _______________________________________________
    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"
    

  • Next message: Dieter Franzke: "Re: usb compile issue"

    Relevant Pages

    • Re: [PATCH] x86_64: handle iret faults better
      ... * back to the fixup entrypoint. ... The error code is not always 0, it might be a bad segment value. ... the kernel ought to give accurate information about the fault consistently ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • buildkernel with INVARIANTS, WITNESS, DEBUG_LOCKS, etc. fails
      ... Building a FreeBSD 6.2-RELEASE kernel on an Intel Pentium 4 with the ... following config options causes buildkernel to fail with undefined ... Relevant error messages from make buildkernel (with KERNCONF set to ... *** Error code 1 ...
      (freebsd-questions)
    • Re: our RS/6000, 7026-M80 model server got an abrupt shutdown.:
      ... 3xx Data storage interrupt ... A page fault always begins as a DSI, ... the DSI will cause a system crash. ... showed the error code 888-102-207-0c5 ...
      (comp.unix.aix)
    • Re: How to handle invalid argument with C?
      ... I compile the code with gcc, when I run, it says "Segmentation fault". ... It's a meaningless test, you invoke UB when you read outside the range of the 'ct' object, you invoke UB when you update outside the range of the 's' object. ... return an error code ... Welcome to the real world, there is no VM here, just real machines. ...
      (comp.lang.c)
    • 4.5 RELENG broken with recent patches
      ... make buildworld runs fine, but buildkernel gives ... *** Error code 1 ...
      (freebsd-stable)