Modify

Opened 3 years ago

Closed 2 years ago

#19636 closed defect (no_response)

WDS crashes on the 5ghz band on TP-Link Archer C7 (1750) v2

Reported by: anonymous Owned by: developers
Priority: normal Milestone: Barrier Breaker 14.07
Component: kernel Version: Barrier Breaker 14.07
Keywords: wds ath10k crash firmware 5ghz Cc:

Description

I tried setting up 2 TP-Link Archer C7 v2 routers to form a WDS bridge on the 5ghz band using the following guide:
https://app.box.com/s/6hx9qhi84hr9l3kqxc3m

When the WDS client tries to join the network, its firmware crashes and it goes into the join/crash loop. Following the exact same steps in that guide using the 2.4ghz radio works fine, WDS functions normally. Log file from the client below:

Mon May 4 02:03:18 2015 kern.info kernel: [ 682.180000] wlan0: authenticate with 30:b5:c2:ec:09:3c
Mon May 4 02:03:18 2015 kern.info kernel: [ 682.190000] wlan0: send auth to 30:b5:c2:ec:09:3c (try 1/3)
Mon May 4 02:03:18 2015 kern.info kernel: [ 682.200000] wlan0: authenticated
Mon May 4 02:03:18 2015 kern.info kernel: [ 682.210000] wlan0: associate with 30:b5:c2:ec:09:3c (try 1/3)
Mon May 4 02:03:18 2015 kern.info kernel: [ 682.210000] wlan0: RX AssocResp from 30:b5:c2:ec:09:3c (capab=0x1 status=0 aid=1)
Mon May 4 02:03:18 2015 kern.info kernel: [ 682.220000] wlan0: associated
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.220000] ath10k: firmware crashed!
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.230000] ath10k: hardware name qca988x hw2.0 version 0x4100016c
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.230000] ath10k: firmware version: 10.1.467.2-1
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.240000] ath10k: target register Dump Location: 0x00401930
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.250000] ath10k: target Register Dump
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.250000] ath10k: [00]: 0x4100016C 0x00000000 0x009A123A 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.260000] ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.260000] ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.270000] ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.280000] ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x009A123A
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.280000] ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.290000] ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.300000] ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.300000] ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.310000] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.320000] ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.320000] ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.330000] ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.340000] ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 kern.err kernel: [ 682.340000] ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:18 2015 daemon.notice netifd: Network device 'wlan0' link is up
Mon May 4 02:03:18 2015 kern.info kernel: [ 682.350000] br-lan: port 2(wlan0) entered forwarding state
Mon May 4 02:03:18 2015 kern.info kernel: [ 682.360000] br-lan: port 2(wlan0) entered forwarding state
Mon May 4 02:03:20 2015 kern.info kernel: [ 684.360000] br-lan: port 2(wlan0) entered forwarding state
Mon May 4 02:03:21 2015 kern.warn kernel: [ 685.350000] net_ratelimit: 7 callbacks suppressed
Mon May 4 02:03:21 2015 kern.warn kernel: [ 685.350000] ath10k: failed to put down monitor vdev 1: -11
Mon May 4 02:03:24 2015 kern.warn kernel: [ 688.360000] ath10k: failed to to request monitor vdev 1 stop: -11
Mon May 4 02:03:29 2015 kern.warn kernel: [ 693.360000] ath10k: failed to synchronise monitor vdev 1: -145
Mon May 4 02:03:29 2015 kern.warn kernel: [ 693.360000] ath10k: failed to stop monitor vdev: -145
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.370000] ath10k: failed to request wmi monitor vdev 1 removal: -11
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.370000] ath10k: failed to delete monitor vdev: -11
Mon May 4 02:03:32 2015 kern.info kernel: [ 696.900000] ieee80211 phy0: Hardware restart was requested
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.900000] ath10k: failed to delete peer 30:b5:c2:ec:09:3c for vdev 0: -143
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.910000] ath10k: failed to stop WMI vdev 0: -143
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.910000] ath10k: failed to recalculate rts/cts prot for vdev 0: -143
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.920000] ath10k: failed to set erp slot for vdev 0: -143
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.930000] ath10k: failed to set preamble for vdev 0: -143
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.930000] ath10k: failed to set wmm params: -143
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.940000] ath10k: failed to set wmm params: -143
Mon May 4 02:03:32 2015 kern.warn kernel: [ 696.940000] ath10k: failed to set wmm params: -143
Mon May 4 02:03:32 2015 daemon.notice netifd: Network device 'wlan0' link is down
Mon May 4 02:03:32 2015 kern.info kernel: [ 696.950000] br-lan: port 2(wlan0) entered disabled state
Mon May 4 02:03:33 2015 kern.err kernel: [ 697.210000] ath10k: failed to wait for target to init: -70
Mon May 4 02:03:34 2015 kern.info kernel: [ 698.450000] ath10k: device successfully recovered
Mon May 4 02:03:37 2015 kern.info kernel: [ 701.140000] wlan0: authenticate with 30:b5:c2:ec:09:3c
Mon May 4 02:03:37 2015 kern.info kernel: [ 701.150000] wlan0: send auth to 30:b5:c2:ec:09:3c (try 1/3)
Mon May 4 02:03:37 2015 kern.info kernel: [ 701.160000] wlan0: authenticated
Mon May 4 02:03:37 2015 kern.info kernel: [ 701.170000] wlan0: associate with 30:b5:c2:ec:09:3c (try 1/3)
Mon May 4 02:03:37 2015 kern.info kernel: [ 701.170000] wlan0: RX AssocResp from 30:b5:c2:ec:09:3c (capab=0x1 status=0 aid=1)
Mon May 4 02:03:37 2015 kern.info kernel: [ 701.180000] wlan0: associated
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.180000] ath10k: firmware crashed!
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.190000] ath10k: hardware name qca988x hw2.0 version 0x4100016c
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.190000] ath10k: firmware version: 10.1.467.2-1
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.200000] ath10k: target register Dump Location: 0x00401930
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.210000] ath10k: target Register Dump
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.210000] ath10k: [00]: 0x4100016C 0x00000000 0x009A123A 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.220000] ath10k: [04]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.220000] ath10k: [08]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.230000] ath10k: [12]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.240000] ath10k: [16]: 0x00000000 0x00000000 0x00000000 0x009A123A
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.240000] ath10k: [20]: 0x00000000 0x00401930 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.250000] ath10k: [24]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.260000] ath10k: [28]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.260000] ath10k: [32]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.270000] ath10k: [36]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.280000] ath10k: [40]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.280000] ath10k: [44]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.290000] ath10k: [48]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.300000] ath10k: [52]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 kern.err kernel: [ 701.300000] ath10k: [56]: 0x00000000 0x00000000 0x00000000 0x00000000
Mon May 4 02:03:37 2015 daemon.notice netifd: Network device 'wlan0' link is up
Mon May 4 02:03:37 2015 kern.info kernel: [ 701.310000] br-lan: port 2(wlan0) entered forwarding state
Mon May 4 02:03:37 2015 kern.info kernel: [ 701.320000] br-lan: port 2(wlan0) entered forwarding state
Mon May 4 02:03:39 2015 kern.info kernel: [ 703.320000] br-lan: port 2(wlan0) entered forwarding state
Mon May 4 02:03:40 2015 kern.warn kernel: [ 704.310000] net_ratelimit: 7 callbacks suppressed
Mon May 4 02:03:40 2015 kern.warn kernel: [ 704.310000] ath10k: failed to put down monitor vdev 1: -11
Mon May 4 02:03:43 2015 kern.warn kernel: [ 707.320000] ath10k: failed to to request monitor vdev 1 stop: -11

Attachments (0)

Change History (6)

comment:1 Changed 3 years ago by anonymous

Client WDS is the one that crashes. Router in AP WDS mode does not crash.

comment:2 Changed 3 years ago by nbd

did you test current trunk?

comment:3 Changed 3 years ago by anonymous

No, just BB. I'm going to install DD-WRT on them and see if it has the same issues. I can test ChaosCalmer later if needed.

comment:4 Changed 3 years ago by anonymous

I can confirm that WDS works fine with DD-WRT 05-09-2015 r26866 installed on both routers

comment:5 Changed 2 years ago by nbd

please try current trunk

comment:6 Changed 2 years ago by nbd

  • Resolution set to no_response
  • Status changed from new to closed

Add Comment

Modify Ticket

Action
as closed .
The resolution will be deleted. Next status will be 'reopened'.
Author


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

 
Note: See TracTickets for help on using tickets.