From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Sterrett Subject: Re: 3.10.0 network trace Date: Sat, 13 Jul 2013 17:10:52 -0400 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: netdev To: Yuchung Cheng Return-path: Received: from mail-pd0-f174.google.com ([209.85.192.174]:64564 "EHLO mail-pd0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750925Ab3GMVKx (ORCPT ); Sat, 13 Jul 2013 17:10:53 -0400 Received: by mail-pd0-f174.google.com with SMTP id 10so9603956pdc.19 for ; Sat, 13 Jul 2013 14:10:52 -0700 (PDT) In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: After changing those two sysctl settings the WARN hasn't reappeared. I'm willing to mess around with this box though if you want to try to narrow down the root cause with different settings and/or patches. On Fri, Jul 12, 2013 at 5:39 PM, Yuchung Cheng wrote: > On Fri, Jul 12, 2013 at 2:33 PM, Michael Sterrett wrote: >> Thanks for the reply. The sysctl -a output is attached. > > Hi Michael: my guess is some of the recent changes like TLP or F-RTO > rewrite has bugs. It'd be best if you can provide tcp traces that > triggers this. If not and this WARN appears frequently enough, please > try i) sysctl tcp_early_retrans=2 ii) sysctl tcp_frto=0 and see if > that WARN goes away. Thanks.