On Thu, Mar 12, 2015 at 03:11:32PM +, Fujinaka, Todd wrote:
> The most likely answer is because you're using a development kernel. Can you
> try the latest stable kernel?
>
> The only recent change to e1000 should only be hit if you're changing the MTU.
This is rarely seen, i've hit it twice
todd.fujin...@intel.com
(503) 712-4565
-Original Message-
From: Erik Hugne [mailto:erik.hu...@ericsson.com]
Sent: Thursday, March 12, 2015 5:49 AM
To: e1000-devel@lists.sourceforge.net
Subject: [E1000-devel] e1000 tx queue timeout
I got this trace with a recent net-next kernel ( 169bf9121b19 ) ru
I got this trace with a recent net-next kernel ( 169bf9121b19 ) running
on a KVM host (2 cores). The traffic pattern is low intensity TIPC traffic
(and an SSH session).
node1 ~ # [ 2099.839503] [ cut here ]
[ 2099.840138] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:30
