Re: v3.8.5: "TCP: snd_cwnd is nul, please report this bug."

["Bjørn Mork" <bjorn@mork.no>]

Eric Dumazet <eric.dumazet@gmail.com> writes:
> 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.

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.


Thanks,
Bjørn