Net: e1000 driver: TX Hang message

Net: e1000 driver: TX Hang message

[Gerrit Visser]

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

Re: Net: e1000 driver: TX Hang message

[Andrew Morton]

If this bug is still present in 2.6.15 could you please create a report
(against 2.6.15) at bugzilla.kenrel.org?

Thanks.

"Gerrit Visser" <g.visser@msc-africa.co.za> wrote:
>
> 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/

RE: Net: e1000 driver: TX Hang message

[Gerrit Visser]

Hi,

I've sent an update about it a while ago. 

In short, when I tested them later, both the standard kernel driver and
the one on Intel's website worked without problems.

In between the point where they didn't work and then worked, I've
installed Windows XP 32-bit on it, and the standard driver on the
windows CD didn't work either. I've loaded an updated driver from Intel,
and then it worked on windows.

Thank you.

Best regards,
Gerrit

-----Original Message-----
From: Andrew Morton [mailto:akpm@osdl.org] 
Sent: 16 January 2006 01:00 PM
To: Gerrit Visser
Cc: linux-kernel@vger.kernel.org
Subject: Re: Net: e1000 driver: TX Hang message


If this bug is still present in 2.6.15 could you please create a report
(against 2.6.15) at bugzilla.kenrel.org?

Thanks.

"Gerrit Visser" <g.visser@msc-africa.co.za> wrote:
>
> 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/