From: Eric Dumazet <eric.dumazet@gmail.com>
To: Phil Oester <kernel@linuxace.com>
Cc: netdev@vger.kernel.org
Subject: Re: 3.7 networking regression - bisected
Date: Fri, 15 Feb 2013 15:43:00 -0800 [thread overview]
Message-ID: <1360971780.19353.26.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130215232752.GA19796@linuxace.com>
On Fri, 2013-02-15 at 15:27 -0800, Phil Oester wrote:
> Since upgrading a box to 3.7, I've been seeing e1000e issues on one box:
>
> e1000e 0000:00:19.0: eth2: Detected Hardware Unit Hang
>
> While 3.6 worked fine. I bisected the problem down to commit
> 69b08f62e17439ee3d436faf0b9a7ca6fffb78db ("net: use bigger pages in
> __netdev_alloc_frag"). Running 3.7.x without that commit is
> currently working fine.
>
> I have other boxes on 3.7 with e1000e that are not experiencing this
> problem. The difference on this box is it runs at 100mb, which
> disables TSO:
>
> e1000e 0000:00:19.0 eth2: 10/100 speed: disabling TSO
>
> So maybe the problem doesn't occur with TSO enabled? Either that,
> or there is something unique about the traffic pattern this box is seeing.
You could try disabling TSO on other boxes.
And CC Intel guys, as it sounds like hardware bug or driver bug.
prev parent reply other threads:[~2013-02-15 23:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 23:27 3.7 networking regression - bisected Phil Oester
2013-02-15 23:43 ` Eric Dumazet [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=1360971780.19353.26.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=kernel@linuxace.com \
--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