From: Andrew Morton <akpm@osdl.org>
To: "Gerrit Visser" <g.visser@msc-africa.co.za>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Net: e1000 driver: TX Hang message
Date: Mon, 16 Jan 2006 02:36:44 -0800 [thread overview]
Message-ID: <20060116023644.3b567f30.akpm@osdl.org> (raw)
In-Reply-To: <C086BA41F8EFC942B7BBBCF09CC95D210E7634@svr.msc-africa.co.za>
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/
next prev parent reply other threads:[~2006-01-16 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 16:21 Gerrit Visser
2006-01-16 10:36 ` Andrew Morton [this message]
2006-01-16 11:08 Gerrit Visser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060116023644.3b567f30.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=g.visser@msc-africa.co.za \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®