[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <309B89C4C689E141A5FF6A0C5FB2118B81F90900@ORSMSX101.amr.corp.intel.com>
Date: Thu, 15 Sep 2016 23:29:34 +0000
From: "Brown, Aaron F" <aaron.f.brown@...el.com>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
CC: John Fastabend <john.fastabend@...il.com>,
"bblanco@...mgrid.com" <bblanco@...mgrid.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"brouer@...hat.com" <brouer@...hat.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"xiyou.wangcong@...il.com" <xiyou.wangcong@...il.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>,
"u9012063@...il.com" <u9012063@...il.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [Intel-wired-lan] [net-next PATCH v3 1/3] e1000: track BQL
bytes regardless of skb or not
> > ------------[ cut here ]------------
> > WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:316
> dev_watchdog+0x1c2/0x1d0
> > NETDEV WATCHDOG: eth1 (e1000): transmit queue 0 timed out
>
> Thanks a lot for the tests! Really appreciate it.
np, I needed to get my old compatibility systems back in running order anyway.
Powered by blists - more mailing lists