• State
  • Locked Locked
  • Replies 14 replies
  • Subscribers 43 subscribers
  • Views 2037 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/WL1837MOD: MESH - AP network issue by using the WL1837MOD module

siva ch61
Intellectual 640 points
Part Number: WL1837MOD
Other Parts Discussed in Thread: WL1837

Tool/software: Linux

Hi All,

I am trying to evaluate the wl1837 module by configuring MESH + AP mode.

When I do start functionality after some time Wi-Fi is not functional as expected.

SETUP Details:

1. Driver and firmware version:

-> Using wlbuild version as "WL18xx_R8,7_SP1"

-> wlcore: PHY firmware version: Rev 8.2.0.0.237
-> wlcore: firmware booted (Rev 8.9.0.0.70)

 

Observations:

1. In mesh network there are 8 mesh nodes(8 AM437x-SK development based custom platforms and stopped communicating each other.

2. Stations are not able to connect  APs which are initialized as virtual interface at all 8 AM437x-Sk development board based custom boards along with mesh functionality.

3. From the dmesg log identified the issue that dropping the received messages at driver level.

wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118
[ 388.663234] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118
[ 389.198636] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70
[ 389.323340] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 106
[ 389.468776] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70
[ 390.193721] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70
[ 474.199391] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118
[ 474.206364] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 106
[ 474.791044] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70
[ 474.797983] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65
[ 474.804676] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65
[ 474.811593] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65
[ 474.895991] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

4. From the driver I came to know reason for this drop packets could be of below reasons.

1. Received packet decryption failure (WL1271_RX_DESC_DECRYPT_FAIL)

2. memory-outage conditions

Looks in my case I am seeing the status as WL1271_RX_DESC_DECRYPT_FAIL.

5. I would like to know how can I resolve this issue.

Right now It was very critical issue for us to proceed further, Please suggest me how can i over right this issue.

Please provide me is there any patch which can help me to resolve this issue.

I appreciate your quick support on this issue.

Thanks & Regards

Ch. Siva

 

  • 0
    TI__Mastermind 29250 points
    Hi,

    Your query has been assigned to the relevant WL18xx expert. We will get back to you soon.

    Best regards,
    Vihang
  • 0 in reply to Vihang Parmar
    Intellectual 640 points

    Hi Vihang,

    Thanks for your support!!

    I would like to provide more debug information on this issue.

    I have tested the mesh network for long run around 12 hours and observed the below kernel trace of the Wi-Fi driver.

    Kindly please have a look and provide me the solution on this. It is very critical issue from our side and need to resolve it.

    ####################### Kernel trace #########################

    hub 1-0:1.0: 1 port detected

    [    7.313824] xhci-hcd xhci-hcd.2.auto: xHCI Host Controller

    [    7.319481] xhci-hcd xhci-hcd.2.auto: new USB bus registered, assigned bus number 2

    [    7.327295] usb usb2: We don't know the algorithms for LPM for this host, disabling LPM.

    [    7.335568] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003

    [    7.342389] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1

    [    7.349664] usb usb2: Product: xHCI Host Controller

    [    7.354576] usb usb2: Manufacturer: Linux 4.1.13-g8dc6617 xhci-hcd

    [    7.360781] usb usb2: SerialNumber: xhci-hcd.2.auto

    [    7.366979] hub 2-0:1.0: USB hub found

    [    7.370804] hub 2-0:1.0: 1 port detected

    [    7.552603] random: dd urandom read with 18 bits of entropy available

    [    8.233341] net eth0: initializing cpsw version 1.15 (0)

    [    8.314243] net eth0: phy found : id is : 0x221622

    [   21.725124] NET: Registered protocol family 10

    [   21.732206] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready

    [   24.951351] cfg80211: Regulatory domain changed to country: US

    [   24.984261] cfg80211:  DFS Master region: FCC

    [   24.988498] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)

    [   25.004716] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 3000 mBm), (N/A)

    [   25.034171] cfg80211:   (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (N/A)

    [   25.043741] cfg80211:   (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2300 mBm), (0 s)

    [   25.059636] cfg80211:   (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2300 mBm), (0 s)

    [   25.067895] cfg80211:   (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 3000 mBm), (N/A)

    [   25.076518] cfg80211:   (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)

    [   25.532871] wlcore: PHY firmware version: Rev 8.2.0.0.237

    [   25.686433] wlcore: firmware booted (Rev 8.9.0.0.70)

    [   25.705036] IPv6: ADDRCONF(NETDEV_UP): wlan1: link is not ready

    [   25.866683] IPv6: ADDRCONF(NETDEV_CHANGE): wlan1: link becomes ready

    [   32.349644] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready

    [   38.515839] random: nonblocking pool is initialized

    [   38.528726] IPv6: ADDRCONF(NETDEV_CHANGE): mesh0: link becomes ready

    [ 3640.645143] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [14444.634103] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [14444.817571] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [14444.842926] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 75

    [18045.946634] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [21647.388097] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [44927.343769] wlcore: ERROR SW watchdog interrupt received! starting recovery.

    [44927.350962] ------------[ cut here ]------------

    [44927.355743] WARNING: CPU: 0 PID: 285 at /home/user/wl18xx_R8.7_SP1_9-12-16/wilink8-wlan-build-utilites/src/compat_wireless/drivers/net/wireless/ti/wlcore/main.c:806 wl12xx_queue_recovery_work.part.10+0x68/0x74 [wlcore]()

    [44927.375418] Modules linked in: ipv6 xhci_plat_hcd wl18xx(O) wlcore(O) mac80211(O) dwc3 ti_am335x_adc kfifo_buf industrialio cfg80211(O) udc_core wlcore_sdio(O) compat(O) phy_omap_usb2 dwc3_omap extcon omap_rng rng_core ti_am335x_tscadc rtc_omap omap_wdt pm33xx

    [44927.398725] CPU: 0 PID: 285 Comm: irq/116-wl18xx Tainted: G           O    4.1.13-g8dc6617 #7

    [44927.407301] Hardware name: Generic AM43 (Flattened Device Tree)

    [44927.413242] Backtrace:

    [44927.415745] [<c0012c08>] (dump_backtrace) from [<c0012e28>] (show_stack+0x18/0x1c)

    [44927.423344]  r7:bf193f24 r6:00000009 r5:00000326 r4:00000000

    [44927.429088] [<c0012e10>] (show_stack) from [<c06816f8>] (dump_stack+0x20/0x28)

    [44927.436375] [<c06816d8>] (dump_stack) from [<c003a450>] (warn_slowpath_common+0x7c/0xb4)

    [44927.444523] [<c003a3d4>] (warn_slowpath_common) from [<c003a52c>] (warn_slowpath_null+0x24/0x2c)

    [44927.453342]  r8:c006e064 r7:db599548 r6:00000001 r5:db5993b8 r4:db599380

    [44927.460166] [<c003a508>] (warn_slowpath_null) from [<bf193f24>] (wl12xx_queue_recovery_work.part.10+0x68/0x74 [wlcore])

    [44927.471072] [<bf193ebc>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf1942ac>] (wlcore_irq+0x230/0x23c [wlcore])

    [44927.482176]  r5:db5993b8 r4:db599380

    [44927.485827] [<bf19407c>] (wlcore_irq [wlcore]) from [<c006e088>] (irq_thread_fn+0x24/0x48)

    [44927.494141]  r7:ddcfc780 r6:00000001 r5:ddcfc780 r4:db5278c0

    [44927.499850] [<c006e064>] (irq_thread_fn) from [<c006e328>] (irq_thread+0xf8/0x144)

    [44927.507461]  r7:ddcfc780 r6:00000001 r5:dcf38000 r4:db5278c0

    [44927.513177] [<c006e230>] (irq_thread) from [<c0054424>] (kthread+0xd0/0xf0)

    [44927.520180]  r9:00000000 r8:00000000 r7:c006e230 r6:db5278c0 r5:db527900 r4:00000000

    [44927.528008] [<c0054354>] (kthread) from [<c000f988>] (ret_from_fork+0x14/0x2c)

    [44927.535270]  r7:00000000 r6:00000000 r5:c0054354 r4:db527900

    [44927.540972] ---[ end trace be243333e5053337 ]---

    [44927.546531] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.70

    [44927.574100] wlcore: pc: 0x11e4f2, hint_sts: 0x00000000 count: 1

    [44927.587919] wlcore: down

    [44927.590532] wlcore: down

    [44927.635062] ieee80211 phy0: Hardware restart was requested

    [44928.004161] wlcore: PHY firmware version: Rev 8.2.0.0.237

    [44928.186976] wlcore: firmware booted (Rev 8.9.0.0.70)

    [44929.190757] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44929.452671] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 106

    [44929.659917] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.668531] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.682106] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.689096] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.696106] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.702754] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.709699] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.716377] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.723017] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.729695] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.736354] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.743004] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44929.750161] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44929.775463] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44929.808624] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44929.840237] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.848767] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.855507] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.862503] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.885730] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44929.894052] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.908901] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.915840] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.922724] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.929450] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.936111] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.942751] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.949886] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.956583] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.963267] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.970266] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.976957] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.983778] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.990462] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44929.997242] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.003918] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.013373] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.020388] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.027072] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.033713] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.040512] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.047317] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44930.054211] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44930.111432] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.118707] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.125424] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.132081] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.138751] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.145693] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.152340] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.159011] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.165666] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.172305] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.178956] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.185607] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.192246] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.198904] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.212134] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.219056] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.226419] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.234281] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.251240] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.258092] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.275724] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 106

    [44930.282572] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 106

    [44930.324060] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.330871] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.337626] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.344490] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.351135] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.357810] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.364466] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.415690] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.422485] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.429190] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.435848] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.442683] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.467024] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44930.474026] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44930.481026] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 98

    [44930.487969] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.494789] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 98

    [44930.501438] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.508290] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.514965] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.521986] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.528931] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.535611] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.560938] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.567839] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.574630] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.581274] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.588223] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.594921] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.601562] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.608220] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.614873] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.621513] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.628474] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.635156] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.641846] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.648515] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.655175] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.661815] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.668472] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.675529] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.682184] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.688868] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.695525] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.702168] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.709290] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.715987] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.722634] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.729297] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.735955] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.742595] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.749671] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.756358] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.763027] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.769692] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44930.776345] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.782993] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.789649] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.796534] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.803182] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.809855] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44930.857503] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.871472] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.896807] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.912360] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.924858] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.933474] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.940208] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.947128] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.954139] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.960792] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.967598] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.974415] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.981060] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.987726] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44930.994380] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.001138] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.038491] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.045401] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.052047] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.058726] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.126024] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.132852] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.139606] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.146471] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.153117] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.159805] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.166469] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.204441] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44931.257006] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.263876] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.270669] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.277544] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44931.284317] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 98

    [44931.291145] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 118

    [44931.297917] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 98

    [44931.313104] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.320033] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.326883] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.333533] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.340342] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.454204] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 70

    [44931.533289] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.540310] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 81

    [44931.977281] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44931.984162] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [44931.990821] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 65

    [48533.333231] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [48533.367060] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [48533.679022] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [48534.661879] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [50460.894055] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 132

    [50585.004484] wlcore: ERROR SW watchdog interrupt received! starting recovery.

    [50585.011597] ------------[ cut here ]------------

    [50585.016566] WARNING: CPU: 0 PID: 285 at /home/user/wl18xx_R8.7_SP1_9-12-16/wilink8-wlan-build-utilites/src/compat_wireless/drivers/net/wireless/ti/wlcore/main.c:806 wl12xx_queue_recovery_work.part.10+0x68/0x74 [wlcore]()

    [50585.036238] Modules linked in: ipv6 xhci_plat_hcd wl18xx(O) wlcore(O) mac80211(O) dwc3 ti_am335x_adc kfifo_buf industrialio cfg80211(O) udc_core wlcore_sdio(O) compat(O) phy_omap_usb2 dwc3_omap extcon omap_rng rng_core ti_am335x_tscadc rtc_omap omap_wdt pm33xx

    [50585.059545] CPU: 0 PID: 285 Comm: irq/116-wl18xx Tainted: G        W  O    4.1.13-g8dc6617 #7

    [50585.068135] Hardware name: Generic AM43 (Flattened Device Tree)

    [50585.074095] Backtrace:

    [50585.076583] [<c0012c08>] (dump_backtrace) from [<c0012e28>] (show_stack+0x18/0x1c)

    [50585.084199]  r7:bf193f24 r6:00000009 r5:00000326 r4:00000000

    [50585.089944] [<c0012e10>] (show_stack) from [<c06816f8>] (dump_stack+0x20/0x28)

    [50585.097231] [<c06816d8>] (dump_stack) from [<c003a450>] (warn_slowpath_common+0x7c/0xb4)

    [50585.105381] [<c003a3d4>] (warn_slowpath_common) from [<c003a52c>] (warn_slowpath_null+0x24/0x2c)

    [50585.114215]  r8:c006e064 r7:db599548 r6:00000001 r5:db5993b8 r4:db599380

    [50585.121031] [<c003a508>] (warn_slowpath_null) from [<bf193f24>] (wl12xx_queue_recovery_work.part.10+0x68/0x74 [wlcore])

    [50585.131950] [<bf193ebc>] (wl12xx_queue_recovery_work.part.10 [wlcore]) from [<bf1942ac>] (wlcore_irq+0x230/0x23c [wlcore])

    [50585.143056]  r5:db5993b8 r4:db599380

    [50585.146708] [<bf19407c>] (wlcore_irq [wlcore]) from [<c006e088>] (irq_thread_fn+0x24/0x48)

    [50585.155019]  r7:ddcfc780 r6:00000001 r5:ddcfc780 r4:db5278c0

    [50585.160730] [<c006e064>] (irq_thread_fn) from [<c006e328>] (irq_thread+0xf8/0x144)

    [50585.168342]  r7:ddcfc780 r6:00000001 r5:dcf38000 r4:db5278c0

    [50585.174072] [<c006e230>] (irq_thread) from [<c0054424>] (kthread+0xd0/0xf0)

    [50585.181059]  r9:00000000 r8:00000000 r7:c006e230 r6:db5278c0 r5:db527900 r4:00000000

    [50585.188886] [<c0054354>] (kthread) from [<c000f988>] (ret_from_fork+0x14/0x2c)

    [50585.196149]  r7:00000000 r6:00000000 r5:c0054354 r4:db527900

    [50585.201851] ---[ end trace be243333e5053338 ]---

    [50585.208195] wlcore: Hardware recovery in progress. FW ver: Rev 8.9.0.0.70

    [50585.254325] wlcore: pc: 0x11e4f2, hint_sts: 0x00000000 count: 2

    [50585.284053] wlcore: down

    [50585.286706] wlcore: down

    [50585.307367] ieee80211 phy0: Hardware restart was requested

    [50585.708983] wlcore: PHY firmware version: Rev 8.2.0.0.237

    [50585.925123] wlcore: firmware booted (Rev 8.9.0.0.70)

    ################################ End of trace #########################

    Thanks & Regards

    Ch. Siva

  • 0
    TI__Mastermind 20285 points
    Hi Siva,

    Can you describe the system you are testing a bit more?:
    1. have you used our build scripts for builing R8.7_SP1 with the am437x kernel, or are you building the drivers which are in-tree in your Linux kernel?
    2. When setting Mesh+AP did you make sure both are using the same channel?
    3. Are you starting to see the corrupted packets immediately after setting the mesh network, or is the system working ok for some time?

    BR,
    Eyal
  • 0 in reply to Eyal Reizer
    Intellectual 640 points

    Hi Eyal,

    Thanks your quick support!!

    Please find the details below

    1. Yes, I am using the wl_build (R8.7_SP1) to generate the drivers.

    2.  Yes, Configured in same channel.

    3.  We were observing the corrupted packets in mesh+AP after around 6 hours of working system.

    As described above issue "mobile station are not able to connect AP" in a log run, to debug/identify the root cause of the issue we enabled driver debug level as shown below and identified that driver was not responding the authentication response pkt for mobile authentication request pkt.

    I am attaching the same console dump for your quick reference. This log gives information from boot-up to issue(station unable to connect).

    kernel driver debug level:

    echo 0x1840 > /sys/module/wlcore/parameters/debug_level

    Please have a look and let me know the root cause of this issue.

    I appreciate your quick response on this.wl18xx_debug_log_AP_not_connected.txt

    Thanks & Regards

    Ch. Siva

  • 0 in reply to siva ch61
    TI__Mastermind 20285 points
    Hi Siva,

    I understand that when the issue starts happening (after 6 hours) after the firmware recovery is seen and the driver reloads, the issue is not solved and you keep seeing corrupted packet with additional recovery etc.
    Can you confirm?

    In case it is true, what does it take to recover? Do you have to reboot the board?

    BR,
    Eyal
  • 0 in reply to Eyal Reizer
    Intellectual 640 points
    Hi Eyal,

    Yes, you are right!!
    In current observation issue was starting after 6 hours and it's not recovering properly and hanging in a certain state.
    And I would like to understand what is the state of driver and firmware in this case. Could you please explain it.

    I am rebooting the board to bring device to normal state.
    Could you please suggest is there any other recovery mechanism which can follow by checking the driver state or firmware state.

    Thanks & Regards
    Ch. Siva
  • 0 in reply to siva ch61
    TI__Mastermind 20285 points
    Hi Siva,

    I have followed up with our system test team and they do have a record of seeing this issue once during extensive traffic tests over mesh.
    So it could be an issue inside the firmware code itself that would need to be debugged by us.
    Can you describe a scenario with which you can reproduce the issue? Are you able to reproduce it easily?
    We have only seen it a couple of times and were not able to reproduce it easily.

    Right now, I believe that when you see this issue, after the recovery occurs if you bring the interfaces down (mesh and ap) and restart them you should be able to recover without a need for reboot. Can you confirm?

    Best Regards,
    Eyal
  • 0 in reply to Eyal Reizer
    Intellectual 640 points

    Hi Eyal,

    Thanks for the update.

    Our side we were able to reproduce issue with in day. Please find steps below to reproduce this issue.

    SETUP DETAILS:

    1. Here I am using the 8 devices for forming the mesh network.  

    2. On each device create two virtual interfaces for AP and mesh functionality.

    3.  Assign the static IP for mesh network.

    4. Run the continuous ping application from each mesh node to complete mesh network nodes.

    5. Step-4 is applicable for each and every node in the mesh network.

    6.  Leave the setup in testing for more than 6 hours to see this issue.

    I hope this could help to reproduce issue at your side.

    How do I know this state from driver stats or firmware stats to unload and reload the driver modules?

    Thanks & Regards

    Ch. Siva

  • 0 in reply to siva ch61
    TI__Mastermind 20285 points
    Hi Siva,

    In order to try and isolate the issue, would it be possible for you to try and recreate this issue with only mesh nodes (No AP)?
    Or do you know already that it happens only when both interfaces (mesh+ap) are up?

    BR,
    Eyal
  • 0 in reply to Eyal Reizer
    Intellectual 640 points
    Hi Eyal,

    we are testing AP+mesh operation and facing this issue.
    Better you test the same scenario to replicate the issue in quick manner.
    We are struck at this point and requesting you to provide solution ASAP.

    Thanks & Regards
    Ch. Siva
  • 0 in reply to siva ch61
    Prodigy 80 points

    Hi Eyal,

    I am Sai, Siva's colleague.

    Is there any update on this issue?

    Regards,

    Sai

  • 0 in reply to siva ch61
    TI__Mastermind 20285 points
    Hi Siva,

    I understand that each am437x based board is both AP and Mesh, right?

    Normally, running mesh and AP interfaces on the same device, allows connecting legacy devices to the mesh network. Meaning, legacy devices, that supports station interface only, can connect to our AP interface, and through it be connected to the mesh network.
    In such case only one AP is needed.
    Can you describe the setup you are trying to create here, and why 8 AP devices are needed.

    BR,
    Eyal
  • 0 in reply to Eyal Reizer
    Prodigy 80 points

    Hi Eyal,

    Yes AM437x board is with both AP and Mesh. 

    We want to allow legacy device to be connected from all devices as all can be situated at different place.

    Regards,

    Sai

     

  • 0 in reply to Sainath Shinde
    TI__Expert 5285 points
    Hello Sai,

    We are currently investigating the issue and trying to recreate it.

    It would be a great help if we can also get some more inputs from you.
    Can you please run the same setup only with 4 devices connected and send us all relevant logs and status (if the issue occurs)

    Thanks,
    Chen Loewy