From: Thomas Jarosch <thomas.jarosch@intra2net.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: 'Linux Netdev List' <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
e1000-devel <e1000-devel@lists.sourceforge.net>
Subject: Re: [bisected regression] e1000e: "Detected Hardware Unit Hang"
Date: Thu, 15 Jan 2015 11:11:09 +0100 [thread overview]
Message-ID: <5229621.KczjbIR22Q@storm> (raw)
In-Reply-To: <1421256052.11734.22.camel@edumazet-glaptop2.roam.corp.google.com>
On Wednesday, 14. January 2015 09:20:52 Eric Dumazet wrote:
> I would try to use lower data per txd. I am not sure 24KB is really
> supported.
>
> ( check commit d821a4c4d11ad160925dab2bb009b8444beff484 for details)
>
> diff --git a/drivers/net/ethernet/intel/e1000e/netdev.c
> b/drivers/net/ethernet/intel/e1000e/netdev.c index
> e14fd85f64eb..8d973f7edfbd 100644
> --- a/drivers/net/ethernet/intel/e1000e/netdev.c
> +++ b/drivers/net/ethernet/intel/e1000e/netdev.c
> @@ -3897,7 +3897,7 @@ void e1000e_reset(struct e1000_adapter *adapter)
> * limit of 24KB due to receive synchronization limitations.
> */
> adapter->tx_fifo_limit = min_t(u32, ((er32(PBA) >> 16) << 10) - 96,
> - 24 << 10);
> + 8 << 10);
>
> /* Disable Adaptive Interrupt Moderation if 2 full packets cannot
> * fit in receive buffer.
Thanks for checking!
I just tried that change on top of git f800c25 (git HEAD), same problem.
Let's see what the Intel wizards come up with.
What "works" is to decrease the page size in git HEAD, too:
diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h
index 85ab7d7..9f0ef97 100644
--- a/include/linux/skbuff.h
+++ b/include/linux/skbuff.h
@@ -2108,7 +2108,7 @@ static inline void __skb_queue_purge(struct
sk_buff_head *list)
kfree_skb(skb);
}
-#define NETDEV_FRAG_PAGE_MAX_ORDER get_order(32768)
+#define NETDEV_FRAG_PAGE_MAX_ORDER get_order(4096)
#define NETDEV_FRAG_PAGE_MAX_SIZE (PAGE_SIZE << NETDEV_FRAG_PAGE_MAX_ORDER)
#define NETDEV_PAGECNT_MAX_BIAS NETDEV_FRAG_PAGE_MAX_SIZE
When I try a page size of 8192, it starts failing again. I'll now run
a stress test with 4096 to see if the problem is really gone
or just happens more rarely.
Cheers,
Thomas
next prev parent reply other threads:[~2015-01-15 10:11 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 15:32 [bisected regression] e1000e: "Detected Hardware Unit Hang" Thomas Jarosch
2015-01-14 17:20 ` Eric Dumazet
2015-01-15 10:11 ` Thomas Jarosch [this message]
2015-01-15 14:43 ` Eric Dumazet
2015-01-15 14:58 ` Thomas Jarosch
2015-01-15 15:25 ` Eric Dumazet
2015-01-15 15:48 ` Thomas Jarosch
2015-01-15 16:00 ` Eric Dumazet
2015-01-15 17:04 ` Thomas Jarosch
2015-01-15 17:20 ` Eric Dumazet
2015-01-15 17:37 ` Thomas Jarosch
2015-01-15 18:24 ` Re: Re: Re: " Eric Dumazet
2015-01-19 16:49 ` Thomas Jarosch
2015-01-15 14:59 ` Jeff Kirsher
2015-02-11 11:23 ` Thomas Jarosch
2015-02-11 11:34 ` Jeff Kirsher
2015-02-12 23:28 ` Brown, Aaron F
2015-02-13 16:14 ` Thomas Jarosch
2015-02-21 1:59 ` Brown, Aaron F
2015-03-23 13:58 ` Thomas Jarosch
2015-03-23 22:37 ` Brown, Aaron F
2015-05-27 16:00 ` Thomas Jarosch
2015-05-30 1:18 ` Brown, Aaron F
2015-07-29 8:51 ` Thomas Jarosch
2019-05-02 12:58 ` Juliana Rodrigueiro
2015-02-12 1:18 ` nick
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=5229621.KczjbIR22Q@storm \
--to=thomas.jarosch@intra2net.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=jeffrey.t.kirsher@intel.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;
as well as URLs for NNTP newsgroup(s).