Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: krkumar2@in.ibm.com
Cc: netdev@vger.kernel.org
Subject: Re: Assertions in latest kernels
Date: Tue, 22 Jan 2008 23:57:23 -0800 (PST)	[thread overview]
Message-ID: <20080122.235723.52174015.davem@davemloft.net> (raw)
In-Reply-To: <OFC47DE839.9B2F85A5-ON652573D9.002BA994-652573D9.002B38BA@in.ibm.com>

From: Krishna Kumar2 <krkumar2@in.ibm.com>
Date: Wed, 23 Jan 2008 13:22:05 +0530

> Sorry for the duplicate bug report, I just saw that Dave Young had already
> reported three of the
> 4 assertions that I was getting. The only different assert I am getting is:
> 
> iperf with multiple threads almost always gets these 4, *especially* when I
> do some batching :).
> 
> static void tcp_fastretrans_alert(struct sock *sk, int pkts_acked, int flag)
> {
>       ...
>       if (WARN_ON(!tp->sacked_out && tp->fackets_out))
>             tp->fackets_out = 0;
>       ...
> }

Does this assertion show up first or do you get the other TCP
ones first?  It might be important, in that if you get the
others ones first that corrupted state might be what leads to
this one.


  reply	other threads:[~2008-01-23  7:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23  6:57 Assertions in latest kernels Krishna Kumar2
2008-01-23  7:52 ` Krishna Kumar2
2008-01-23  7:57   ` David Miller [this message]
2008-01-23  8:22     ` Krishna Kumar2
2008-01-23  9:17       ` Ilpo Järvinen
2008-01-23 10:57         ` David Miller
     [not found] <OF6C895B68.E4A75EFD-ON652573D9.0034E821-652573D9.0034BF2E@in.ibm.com>
2008-01-23  9:53 ` Ilpo Järvinen
2008-01-23 10:38   ` Krishna Kumar2
2008-01-23 10:49   ` Ilpo Järvinen
2008-01-23 11:06     ` David Miller
2008-01-23 11:02   ` Krishna Kumar2
2008-01-23 11:42     ` Ilpo Järvinen

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=20080122.235723.52174015.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=krkumar2@in.ibm.com \
    --cc=netdev@vger.kernel.org \
    /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