public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: dormando <dormando@rydia.net>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: BUG: IPv4: Attempt to release TCP socket in state 1
Date: Mon, 04 Mar 2013 21:07:26 -0800	[thread overview]
Message-ID: <1362460046.15793.111.camel@edumazet-glaptop> (raw)
In-Reply-To: <51356AC1.4090302@gmail.com>

On Tue, 2013-03-05 at 11:47 +0800, Cong Wang wrote:
> (Cc'ing the right netdev mailing list...)
> 
> On 03/05/2013 08:01 AM, dormando wrote:
> > Hi!
> >
> > I have a (core lockup?) with 3.7.6+ and 3.8.2 which appears to be under
> > ixgbe. The machine appears to still be up but network stays in a severely
> > hobbled state. Either lagging or not responding to the network at all.
> >
> > On a new box the hang happens within 8-24 hours of giving it production
> > network traffic. On an older machine (6 cores instead of 8, etc) it can
> > run for a week or more before hanging.
> >
> > The hang from 3.7 might be slightly different than 3.8. They seem to be
> > mostly the same aside from 3.8 hanging in the GRO path. Don't see anything
> > obvious in 3.9-rc1 that would fix it, and haven't tried 3.9-rc1.
> >
> > I've not yet figured out how to reproduce outside of production (as
> > always, sigh). This doesn't seem to happen with 3.6.6, but we have
> > different and less frequent kernel panics there.
> >

Dornando, do you use any kind of special setup, external modules, 
or netfilter ? (iptables-save output would help)

Is it a pristine kernel, or a modified one ?

  reply	other threads:[~2013-03-05  5:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.02.1303041547080.7811@localhost6.localdomain6>
2013-03-05  3:47 ` BUG: IPv4: Attempt to release TCP socket in state 1 Cong Wang
2013-03-05  5:07   ` Eric Dumazet [this message]
2013-03-05  5:44     ` dormando
2013-03-05 14:46       ` Eric Dumazet
2013-03-07  0:41         ` dormando
2013-03-07 13:46           ` Eric Dumazet
2013-03-08  7:09             ` dormando
2013-03-14 21:21             ` dormando
2013-03-14 22:56               ` Eric Dumazet
2013-03-14 23:15                 ` dormando
2013-03-14 23:19                   ` Eric Dumazet
2013-03-16 17:36                     ` Eric Dumazet
2013-03-16 17:44                       ` Eric Dumazet
2013-03-16 20:16                         ` dormando
2013-03-17  9:21                         ` dormando
2013-03-17 16:33                           ` Eric Dumazet
2013-03-17 16:52                             ` Eric Dumazet
2013-03-17 19:00                               ` Eric Dumazet
2013-03-17  6:39                       ` Hannes Frederic Sowa
2013-03-17  7:53                         ` Hannes Frederic Sowa

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=1362460046.15793.111.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=dormando@rydia.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /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