just found "Network Adapter Driver for PCI-E Gigabit Network Connections under
Linux*"
version 1.2.20
Intel's Readme suggests that this will fix the driver generated interrupts.
Since our e1000e driver is only version 1.0.2 I'm going to winscp the tarball
provided by Intel to the machine and fol
On Sun, 19 Apr 2009, Andrey Luzgin wrote:
> We have repeating problems on several servers with different versions of
> the driver e1000e with kernel 2.6.28.9 (this version because of tproxy
> is necessary to us). All servers is Intel® Server Systems SR1560SF with
> one additional NIC 82572EI Gigabi
On Thu, 12 Mar 2009 13:59:24 -0700
"Brandeburg, Jesse" wrote:
> re-added the list for tracking...
>
> I think I see the issue, you have more than 4GB ram, and it appears that
> your system doesn't handle dual address cycles correctly, or our adapter
> doesn't work quite right for some reason.
>
c: e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] Detected Tx Unit Hang
so, the 4GB patch will only cause a slight increase in cpu utilization. There
are no other side effects, and you *DO NOT* have to run the TxDescriptorStep
workaround.
I think I might just push the change to no
are working better,
Jesse
From: Gary W. Smith [mailto:g...@primeexalia.com]
Sent: Thursday, March 12, 2009 2:45 PM
To: Gary W. Smith; Brandeburg, Jesse
Cc: e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] Detected Tx Unit Hang
That was a bad example
: Gary W. Smith [mailto:g...@primeexalia.com]
Sent: Thu 3/12/2009 2:32 PM
To: Brandeburg, Jesse
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: [E1000-devel] Detected Tx Unit Hang
Jesse,
Looks better. transfering 50GB to/from the server and I'm not getting the
errors in the log now.
of?
Gary
From: Brandeburg, Jesse [mailto:jesse.brandeb...@intel.com]
Sent: Thu 3/12/2009 1:59 PM
To: Gary W. Smith
Cc: e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] Detected Tx Unit Hang
re-added the list for tracking...
I think I see the issue, you have
Brandeburg, Jesse
Subject: RE: [E1000-devel] Detected Tx Unit Hang
Jesse,
Included is the messages log with the debug patch. It only took a couple
seconds to get it to trigger the problem even with the modprobe.conf changes.
options e1000 TxDescriptorStep=4,4
alias eth0 e1000
alias eth1 e1000
sts.sourceforge.net
Subject: RE: [E1000-devel] Detected Tx Unit Hang
sorry, go to the home page http://sourceforge.net/projects/e1000
click Tracker
click patches
click tx hang debug code (all releases) - 1460945
download the e1000_806_dump.patch, it should apply with fuzz to your e1000
driver directo
Jesse
Cc: e1000-devel@lists.sourceforge.net
Subject: RE: [E1000-devel] Detected Tx Unit Hang
Excuse my ignorance, but which patches? ;). There's a lot of stuff on the
download page. I assume you are talking about the I/OAT driver & kernel patch
but I want to make sure before doing i
Excuse my ignorance, but which patches? ;). There's a lot of stuff on the
download page. I assume you are talking about the I/OAT driver & kernel patch
but I want to make sure before doing it.
>
> Mar 11 18:50:01 vcsoaknas01 kernel: e1000: eth0: e1000_clean_tx_irq:
> Detected Tx Unit Hang
>
On Wed, 11 Mar 2009, Gary W. Smith wrote:
> I asked this last week but didn't get a response. I have a supermicro
apologies for the slow response.
> server with a dual intel nic that uses the e0100 driver. I'm using
> CentOS 5.2 and when I do anything network intensive I lose connectivity
> for
12 matches
Mail list logo
