From: "Bjørn Mork" <bjorn@mork.no>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Yuchung Cheng <ycheng@google.com>,
Neal Cardwell <ncardwell@google.com>
Subject: Re: v3.8.5: "TCP: snd_cwnd is nul, please report this bug."
Date: Sun, 02 Jun 2013 21:21:59 +0200 [thread overview]
Message-ID: <874ndg71yg.fsf@nemi.mork.no> (raw)
In-Reply-To: <1370182956.24311.34.camel@edumazet-glaptop> (Eric Dumazet's message of "Sun, 02 Jun 2013 07:22:36 -0700")
Eric Dumazet <eric.dumazet@gmail.com> writes:
> On Sun, 2013-06-02 at 12:19 +0200, Bjørn Mork wrote:
>
>> Just FYI, in case you wondered what happened here...
>>
>> I've been running with the debug patch since you sent it to me, and
>> still is. But the warning has not yet reappeared.
>>
>> I'll continue using the patch for a while, but will eventually drop it
>> if the warning cannot be reproduced in another couple of weeks time.
>> There have been a few fixes to iwlwifi in the meantime, and I do not
>> rule out the possibility that some of these removed the triggering
>> event.
>>
>
> What exact tree are you running ?
I am currently testing the mainline v3.10-rcX releases. I.e. v3.10-rc4
right now.
> F-RTO code was replaced by Yuching Cheng, and it might very well have
> solved these issues.
>
> commit e33099f96d99c391b3325caa9c44258de04aae86
> ("tcp: implement RFC5682 F-RTO")
>
> commit ab42d9ee3d215ab74a49818ffc53771a88ce7ddf
> ("tcp: refactor CA_Loss state processing")
>
> commit 9b44190dc114c1720b34975b5bfc65aece112ced
> ("tcp: refactor F-RTO")
Right.
I'll assume the problem is fixed then. Will drop the debug patch for
now, but resurrect it and let you know if I ever see the warning again.
Bjørn
prev parent reply other threads:[~2013-06-02 19:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 9:06 v3.8.5: "TCP: snd_cwnd is nul, please report this bug." Bjørn Mork
2013-04-08 14:30 ` Eric Dumazet
2013-04-08 15:14 ` Bjørn Mork
2013-04-08 15:18 ` Eric Dumazet
2013-04-08 15:42 ` Bjørn Mork
2013-06-02 10:19 ` Bjørn Mork
2013-06-02 14:22 ` Eric Dumazet
2013-06-02 14:24 ` Eric Dumazet
2013-06-02 19:21 ` Bjørn Mork [this message]
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=874ndg71yg.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=ycheng@google.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