Re: [E1000-devel] Detected Tx Unit Hang

[Gary W. S. <ga...@pr...>]

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