Net: e1000 driver: TX Hang message

From: Gerrit Visser (g.visser_at_msc-africa.co.za)
Date: 09/30/05

  • Next message: Andrew Patterson: "Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel"
    Date:	Fri, 30 Sep 2005 18:21:24 +0200
    To: <linux-kernel@vger.kernel.org>
    
    

    Hi,

    I've got a DELL precision 670 that has an Intel Gigabit Ethernet onboard
    NIC (82545GM chipset). It receives packets but keeps on giving "Tx hang"
    messages and doesn't send any packets.

    Both standard Redhat WS4 (kernel 2.6.9) and kernel 2.6.13.2 did the
    same.

    To fix it, I've changed the following in the file e1000_hw.c:

        case E1000_DEV_ID_82545GM_COPPER:
        case E1000_DEV_ID_82545GM_FIBER:
        case E1000_DEV_ID_82545GM_SERDES:
            hw->mac_type = e1000_82545_rev_3;
            break;

    to

        case E1000_DEV_ID_82545GM_COPPER:
        case E1000_DEV_ID_82545GM_FIBER:
        case E1000_DEV_ID_82545GM_SERDES:
            hw->mac_type = e1000_82545;
            break;

    (ie. removed the "_rev_3")

    I'm not certain whether it's necessary to change this for copper, fiber
    and serdes. Mine is a copper (pci id 1026).

    This worked for the Linux e1000 driver from Intel's website, but exactly
    the same piece of code is in the 2.6.13.2 kernel's e1000 driver.

    Best regards,
    Gerrit

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/


  • Next message: Andrew Patterson: "Re: I request inclusion of SAS Transport Layer and AIC-94xx into the kernel"

    Relevant Pages

    • [PATCH 4/4] iseries_veth: Cleanup skbs to prevent unregister_netdevice() hanging
      ... The iseries_veth driver is badly behaved in that it will keep TX packets ... This causes the unregister_netdevice code to wait forever when we try to take ... There's already code to cleanup any un-ACK'ed packets in veth_stop_connection ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [BUG] Tulip for ULi M5263: No packets transmitted
      ... > the tulip driver isn't work out for my ULi M5263 network adapter. ... Running a packet capture on it shows no outbound packets, ... > so I guess the driver thinks the card is screwed up and can't transmit. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: raw sockets and blocking
      ... >> sends to actually down ethernet interface are multicast packets. ... Hello's in broadcast network are multicast. ... It appears to be bug in e100 driver in 2.4.x. ... To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ ...
      (Linux-Kernel)
    • Re: tulip driver: errors instead TX packets?
      ... >> driver on 2.6.1. ... >> the packets sent in the errors field instead of the TX packets field. ... Piotr Kaczuba ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: Filter Hook
      ... the callback routine is been invoked at DISPATCH_LEVEL. ... If you really have to keep such a queue for the packets, then the IP filter driver is not suitable for your needs since you have to process all the packets in the callback routine without any wait actionand return it to the tcpip driver immediately when the callback routine returns. ... What IRQL are you running at when you crash, ...
      (microsoft.public.development.device.drivers)