Modify

Opened 3 years ago

Last modified 22 months ago

#19043 new defect

WiFi quality drops after 6 days 8 hours and 43 minutes on TL-WDR4300

Reported by: anonymous Owned by: developers
Priority: normal Milestone:
Component: base system Version: Barrier Breaker 14.07
Keywords: Cc:

Description

I have noticed that after about 6 days of uptime wifi on my wdr4300 starts lagging.

There is nothing in the dmesg or logs about this.
When I issue command 'wifi' from console wlan starts to work again for a next 6 days.

I tried to measure exact interval of working wifi by setting up monitoring and writing down timestamps. The interval before lags is pretty stable and equals to 6 days 8 hours and 43 minutes.

I suspect some kind of integer overflow here.

There is 'Baseband watchdog' counter in /sys/kernel/debug/ieee80211/phy0/ath9k/reset increasing, but I do not know how exact moments of this increase are related to the issue.

Attachments (0)

Change History (8)

comment:1 Changed 3 years ago by Nilfred

Did you transfer 4 GiB in this time interval?

comment:2 Changed 3 years ago by anonymous

Overall traffic is small and irregular. My main wifi client is a phone but sometimes there are other devices connected.
A few of 6-day intervals get 4GiB or more data.

comment:3 Changed 3 years ago by Nilfred

15 minutes are enough Transfer 4 GiB to/from your phone. Figure out how to force that traffic and check if there is lag.
There are no time bombs/counters I'm aware of.

comment:4 Changed 3 years ago by anonymous

I tried to transfer large volume of data in both directions using iperf from my notebook. No lags after that.

comment:5 Changed 3 years ago by anonymous

exactly same problem with a Gateworks Laguna & Wireless cards Compex WLM200N5-26ESD
if i type 'top' sirq use 100% of one core CPU and system is very slow.
Wifi bandwitdth decrease from 7,5Mbyres to half (3,5Mbytes)
same problem with Barrier breaker and Trunk release r44077

comment:6 Changed 3 years ago by anonymous

I set beacon_int to 25 after last occurence of lag.
I expected lag period might become shorter, since beacon sending process was accelerated four times and overflow (if any) may be reached early.

After that I have noticed two things:

  • my phone now reply to pings with lower loss rate (it seems that phone does not sleep anymore);
  • expected occurence of lag after change is missed, so lag interval is increased.

comment:7 Changed 3 years ago by anonymous

After a long time I have to add this.

  • Lags occured only on my phone. This is a cheap device with android 2.3.7. Other devices are working with wifi without problems.
  • The overall lagging behaviour is very stable: constant amount of time passes from wifi reset on the router to packet drops by the phone.

So this bug may be closed as not important, but some kind of hidden defect may be still present.

comment:8 Changed 22 months ago by anonymous

I finally have figured out what this time interval means.

Internal wifi time is measured in microseconds (TSF), and 239 microseconds is exactly 6 days and 8:42:35.813888.

Now I think this is entirely my phone issue and it has nothing to do with openwrt.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.