From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: Eric Dumazet <edumazet@google.com>, netdev@vger.kernel.org
Subject: Re: v3.8.5: "TCP: snd_cwnd is nul, please report this bug."
Date: Mon, 08 Apr 2013 08:18:21 -0700 [thread overview]
Message-ID: <1365434301.3887.14.camel@edumazet-glaptop> (raw)
In-Reply-To: <87li8tyrzs.fsf@nemi.mork.no>
On Mon, 2013-04-08 at 17:14 +0200, Bjørn Mork wrote:
> Eric Dumazet <eric.dumazet@gmail.com> writes:
> > On Mon, 2013-04-08 at 11:06 +0200, Bjørn Mork wrote:
> >
> >> Apr 8 10:58:09 nemi kernel: [152701.980799] TCP: snd_cwnd is nul, please report this bug.
> >> Apr 8 10:58:33 nemi kernel: [152725.176151] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues
> >> Apr 8 10:58:33 nemi kernel: [152725.185713] wlan0: authenticate with 00:22:90:f9:23:a0
> >> Apr 8 10:58:33 nemi kernel: [152725.185738] wlan0: capabilities/regulatory prevented using AP HT/VHT configuration, downgraded
> >> Apr 8 10:58:33 nemi kernel: [152725.190150] wlan0: send auth to 00:22:90:f9:23:a0 (try 1/3)
> >> Apr 8 10:58:33 nemi kernel: [152725.199812] wlan0: authenticated
> >> Apr 8 10:58:33 nemi kernel: [152725.200020] iwlwifi 0000:03:00.0 wlan0: disabling HT as WMM/QoS is not supported by the AP
> >> Apr 8 10:58:33 nemi kernel: [152725.200027] iwlwifi 0000:03:00.0 wlan0: disabling VHT as WMM/QoS is not supported by the AP
> >> Apr 8 10:58:33 nemi kernel: [152725.204033] wlan0: associate with 00:22:90:f9:23:a0 (try 1/3)
> >> Apr 8 10:58:33 nemi kernel: [152725.207317] wlan0: RX AssocResp from 00:22:90:f9:23:a0 (capab=0x421 status=0 aid=12)
> >> Apr 8 10:58:33 nemi kernel: [152725.210745] wlan0: associated
> >>
> >
> > Same issue was reported by Dave Jones on iwlwifi few days ago and I sent
> > following debugging patch, could you try it ?
>
> Will do. The patch only applied on top of net-next, so I assume that's
> what you want me to test it on?
>
> I looked through my logs and the 'fail to flush all tx fifo queues'
> warning from iwlwifi appears very infrequent. The last time before
> today was March 18th... Also accompanied by your warning. That's the
> only two times I've seen that one. And I've been running v3.8-rc7 (where
> you introduced the warning) or newer since Feb 8th.
>
> So don't hold your breath. This may take a few weeks to trigger again.
>
I believe patch applies (with some fuzz) on Linus tree, and maybe on 3.8
too.
next prev parent reply other threads:[~2013-04-08 15:18 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 [this message]
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
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=1365434301.3887.14.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=bjorn@mork.no \
--cc=edumazet@google.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