netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: netdev@vger.kernel.org
Subject: Re: e1000e: Avoid wrong check on TX hang
Date: Wed, 21 Mar 2012 22:11:09 -0700	[thread overview]
Message-ID: <1332393069.2906.135.camel@jtkirshe-mobl> (raw)
In-Reply-To: <OF66508452.5C6F589E-ONC12579C8.005ECBB5-C12579C8.005F4640@transmode.se>

[-- Attachment #1: Type: text/plain, Size: 1009 bytes --]

On Wed, 2012-03-21 at 18:20 +0100, Joakim Tjernlund wrote:
> I think commit 09357b00255c233705b1cf6d76a8d147340545b8(e1000e: Avoid wrong check on TX hang)
> needs to be applied in 3.2.x (and 3.0.x) too.
> 
> We have seen this on routers(we got 3):
> e1000e 0000:11:00.0: eth9: Detected Hardware Unit Hang:
>   TDH                  <a4>
>   TDT                  <a7>
>   next_to_use          <a7>
>   next_to_clean        <a4>
> buffer_info[next_to_clean]:
>   time_stamp           <1008e849f>
>   next_to_watch        <a4>
>   jiffies              <1008e85d8>
>   next_to_watch.status <0>
> MAC Status             <80387>
> PHY Status             <792d>
> PHY 1000BASE-T Status  <3800>
> PHY Extended Status    <3000>
> PCI Status             <10>
> 
> Applying the above patch on 3.2.12 makes the error go away.
> 
>    Jocke
> 

Thanks Joakim, I am aware of the issue/fix.  I will submit the fix to
all stable tree's back to 2.6.32.  Look for me posting the patch this
weekend.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

      reply	other threads:[~2012-03-22  5:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 17:20 e1000e: Avoid wrong check on TX hang Joakim Tjernlund
2012-03-22  5:11 ` Jeff Kirsher [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=1332393069.2906.135.camel@jtkirshe-mobl \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=joakim.tjernlund@transmode.se \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).