From: David Miller <davem@davemloft.net>
To: auke-jan.h.kok@intel.com
Cc: akpm@osdl.org, jesse.brandeburg@intel.com,
netdev@vger.kernel.org, pstaszewski@artcom.pl,
bugme-daemon@bugzilla.kernel.org
Subject: Re: [Bugme-new] [Bug 7450] New: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang
Date: Thu, 02 Nov 2006 23:13:05 -0800 (PST) [thread overview]
Message-ID: <20061102.231305.74560981.davem@davemloft.net> (raw)
In-Reply-To: <454A67C0.6040201@intel.com>
From: Auke Kok <auke-jan.h.kok@intel.com>
Date: Thu, 02 Nov 2006 13:48:48 -0800
> the hang is caused by a bad eeprom bit. A script that fixes it for
> 82573-series with eeproms that need this bit fixed is attached to
> the bugreport. It detects the proper chipset and patches if required
> (uses ethtool).
Those third party card makers, they always mess up the eeprom
making things hard to support. :-)
prev parent reply other threads:[~2006-11-03 7:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 19:20 Fw: [Bugme-new] [Bug 7450] New: e1000: eth0: e1000_clean_tx_irq: Detected Tx Unit Hang Andrew Morton
2006-11-02 21:48 ` Auke Kok
2006-11-03 7:13 ` David Miller [this message]
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=20061102.231305.74560981.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=auke-jan.h.kok@intel.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pstaszewski@artcom.pl \
/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;
as well as URLs for NNTP newsgroup(s).