Thanks. I'll get this in sometime this afternoon.
Hopefully we can have some information from the server tonight.
Gary
Sent via BlackBerry by AT&T
-----Original Message-----
From: "Brandeburg, Jesse" <jesse.brandeb...@intel.com>
Date: Thu, 12 Mar 2009 09:33:21
To: Gary W. Smith<g...@primeexalia.com>
Cc: e1000-devel@lists.sourceforge.net<e1000-devel@lists.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 directory with the command
download file.patch...
patch -d e1000-8.0.* -p1 < file.patch
here is the download link
https://sourceforge.net/tracker2/download.php?group_id=42302&atid=447451&file_id=298629&aid=1460945
________________________________
From: Gary W. Smith [mailto:g...@primeexalia.com]
Sent: Thursday, March 12, 2009 9:16 AM
To: Brandeburg, 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 it.
>
> Mar 11 18:50:01 vcsoaknas01 kernel: e1000: eth0: e1000_clean_tx_irq:
> Detected Tx Unit Hang
> Mar 11 18:50:01 vcsoaknas01 kernel: Tx Queue <0>
> Mar 11 18:50:01 vcsoaknas01 kernel: TDH <f7>
> Mar 11 18:50:01 vcsoaknas01 kernel: TDT <f7>
> Mar 11 18:50:01 vcsoaknas01 kernel: next_to_use <f7>
> Mar 11 18:50:01 vcsoaknas01 kernel: next_to_clean <24>
> Mar 11 18:50:01 vcsoaknas01 kernel: buffer_info[next_to_clean]
> Mar 11 18:50:01 vcsoaknas01 kernel: time_stamp <1004de0b1>
> Mar 11 18:50:01 vcsoaknas01 kernel: next_to_watch <24>
> Mar 11 18:50:01 vcsoaknas01 kernel: jiffies <1004dec18>
> Mar 11 18:50:01 vcsoaknas01 kernel: next_to_watch.status <0>
this really indicates that the adapter is finishing all the work but that
the descriptor is not making it back to main memory indicating the work
was completed. We have seen this a lot with AMD systems, in particular
ones with VIA chipsets. There is a bad bug in those machines when an IO
device and the processor both write to the same cache line.
also, if the above workaround doesn't help we'll want you to install the
dump patch from the patches section of e1000.sourceforge.net and send us
the output when you get a tx hang.
hope this helps,
Jesse
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
E1000-devel mailing list
E1000-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/e1000-devel
