[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1421335532.11734.73.camel@edumazet-glaptop2.roam.corp.google.com>
Date: Thu, 15 Jan 2015 07:25:32 -0800
From: Eric Dumazet <eric.dumazet@...il.com>
To: Thomas Jarosch <thomas.jarosch@...ra2net.com>
Cc: 'Linux Netdev List' <netdev@...r.kernel.org>,
Eric Dumazet <edumazet@...gle.com>,
Jeff Kirsher <jeffrey.t.kirsher@...el.com>,
e1000-devel <e1000-devel@...ts.sourceforge.net>
Subject: Re: Re: [bisected regression] e1000e: "Detected Hardware Unit Hang"
On Thu, 2015-01-15 at 15:58 +0100, Thomas Jarosch wrote:
> A colleague mentioned to me he saw the "Hardware Unit Hang" message every
> few days even running on kernel 3.4 (without your patch). Basically I'm
> testing now if that's still the case with 3.19-rc4+ or not.
>
> I'm all for fixing the root cause. I'm just interested if the e1000e
> hang can even be triggered when using a max frag page size of 4096.
> So far it transferred 751.6 GiB without a hiccup.
You told it was forwarding setup.
1) What is the NIC receiving traffic.
2) What happens if you disable GRO on it ?
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists