OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category Kernel
  • Assigned To No-one
  • Operating System All
  • Severity Critical
  • Priority Very Low
  • Reported Version lede-17.01
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by kiwipuppeh - 11.12.2017

FS#1220 - Wireless on WRT3200ACM kills all networking

Supply the following if possible:
Linksys WRT3200ACM

driver name: mwlwifi
chip type: 88W8964
hw version: 7
driver version:
firmware version: 0×09030201 power table loaded from dts: no
firmware region code: 0×0 mac address: 60:38:e0:be:cc:e1
2g: enable
5g: disable
antenna: 4 4
irq number: 106
ap macid support: 0000ffff
sta macid support: 00010000
macid used: 00000001
radio: enable
iobase0: e1200000
iobase1: e1480000
tx limit: 1024
rx limit: 16384

Reboot (17.01.4, r3560-79f57e422d)

Steps to reproduce:
Fresh OpenWRT Install
Remove the old mwlwifi driver, Install the updated (as it is broken in the base install)
Enable the 5GHZ band signals
SSH into router and run readlog -f
Run many speed tests from multiple devices (seems to trigger it almost instantly)


Right before it crashes and I lose all connectivity I get the message:
Mon Dec 11 08:39:31 2017 kernel: [10357.894826] mwifiex_sdio mmc0:0001:1: Tx: Bridge packet limit reached. Drop packet!
Mon Dec 11 08:39:51 2017 daemon.notice hostapd: nl80211: nl80211_recv_beacons→nl_recvmsgs failed: -5
Mon Dec 11 08:39:51 2017 kernel: [10377.918852] mwifiex_sdio mmc0:0001:1: cmd_wait_q terminated: -110

I tried increasing the txpacket limit from 1000 to 20000 but that only delayed the crash until later.

anomeome commented on 11.12.2017 20:27

This appears to be at cross purposes, you update and provide version information for mwlwifi, but error is from the driver for the third radio (sdio)?

kiwipuppeh commented on 11.12.2017 23:50

The error is what last gets sent across the log before all networking dies. Including LAN/WAN/WLAN.

As you can see, I updated and they said that the kernel error message was not due to the driver.

anomeome commented on 12.12.2017 00:10

Yes, as you appear to be conflating mwlwifi and mwiflex.

To point: kmod-mwlwifi != kmod-mwiflex-sdio (which is where you appear to hit issue)

See the readme about disabling third radio (phy2), to see if that might resolve.

kiwipuppeh commented on 12.12.2017 14:40

So far so stable, I'm unsure at this point who I would need to contact to get support for the third radio. If this doesn't fall under you guys, feel free to close this ticket.


Available keyboard shortcuts


Task Details

Task Editing