• State TI Thinks Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 43 subscribers
  • Views 4386 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/WL1831MOD: Many instances of "wlcore: WARNING corrupted packet in RX: status: 0x1"

Jonah Petri
Intellectual 320 points
Part Number: WL1831MOD
Other Parts Discussed in Thread: AM3357

Tool/software: Linux

We are encountering many, many instances of the following kernel log line. 

2017-10-30 11:26:13.589 [288519.884275] wlcore: WARNING corrupted packet in RX: status: 0x3 len: 375
2017-10-30 11:26:13.455 [334447.241466] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 362
2017-10-30 11:26:13.379 [288557.482231] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 78
2017-10-30 11:26:13.229 [334856.475089] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 110
2017-10-30 11:26:13.159 [334484.578544] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 323
2017-10-30 11:26:12.999 [220153.902151] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 110
2017-10-30 11:26:12.999 [220153.901110] wlcore: WARNING corrupted packet in RX: status: 0x1 len: 110

Some units log this line 500,000+ times per day.

I'm not sure what this line means, nor how to react to it.  It does seem to correlate with particularly bad wifi performance on the WL1831MOD module, which is a critical customer issue for us.

Configuration:

WL1831MOD on AM3357

TI kernel 3.12.10

Kernel SHA: 7f280334068b7c875ade51f8f3921ab311f0c824

wlcore: driver version: R8.7_SP2-dirty
wlcore: PHY firmware version: Rev 8.2.0.0.240
wlcore: firmware booted (Rev 8.9.0.0.75)



  • 0
    TI__Expert 6335 points
    Jonah,

    We have assigned your post to the relevant engineer and will get back to you.
  • 0 in reply to dale
    TI__Mastermind 27080 points
    Are you using a TISDK release and rebuit the WL18xx drivers from 8.7R2, backported to K3.12?
    Along the same lines - Have, you made any changes to the system (ex: migration to 8.7R2), after which you got these error messages?
  • 0 in reply to Hari Nagalla
    Intellectual 320 points
    Hello!
    Thanks for the reply.
    To be precise, we are using the build-utilities from git://git.ti.com/wilink8-wlan/build-utilites.git, and executing the build_wl18xx.sh script with the driver tag "R8.7_SP2".
    We recently moved from R8.6 to R8.7_SP2. We were seeing many messages as above: "wlcore: WARNING corrupted packet in RX", which led me to upgrade the firmware. However, our experience has remained unchanged.
    Any help understanding where to look would be very much appreciated. We don't have clear steps to reproduce the issue, unfortunately, but the issue is quite pervasive.
    Jonah
  • 0 in reply to Jonah Petri
    TI__Mastermind 27080 points
    Did, you try with different Access Points? And, is this error message consistent across the APs?
    It seems, moving to newer firmware has improved for some configurations.. Please check here:

    e2e.ti.com/.../401452

    Thanks
  • 0 in reply to Hari Nagalla
    Intellectual 320 points

    Hello Hari,

    As I said above, we have not managed to reproduce the issue locally.  We are seeing many, many logs from units in the field.  I do not have information on what access points are being used.  I'm hoping you can tell me what this log means, so that I can understand the severity.

    Also, as you can see, we are already on the latest firmware, R8.7_SP2.

    Best,

    Jonah

  • 0 in reply to Jonah Petri
    TI__Mastermind 27080 points
    It appears, one instance when this can occur is when an encrypted action frame type SA-Query is received. We, will check with our System Experts and get back to you..

    Thanks
  • 0 in reply to Jonah Petri
    TI__Expert 5285 points
    Hello Jonah,

    As Hari explained this message comes when the unit receives an encrypted message. Tries to parse it and finds the data corrupted.

    This can come from many different reasons.
    In order for us to be able to help and pin point what is the exact cause and how come the customer sees so many corrupted packets we will need more information.

    We need the following:

    1. Some general information about the scenario - which AP is involved. How congested is the air, and as much information as possible on the scenario,
    2. Logs - sniffer logs (so we can understand what packets are being sent. FW logs and Driver logs.

    Thanks,
    Chen Loewy
  • 0 in reply to Chen Loewy
    Intellectual 320 points

    Hello,
    Thanks for your reply.
    1) This is happening over literally hundreds of customer devices, each on their own access point, and seems tied to our upgrade from 8.6 to 8.7 SP2 firmware. I will try to get you some examples of customer AP make/model/firmware.
    2) I will not run any packet sniffers on customer's networks, obviously. If I can find a company employee or testbed device exhibiting this behavior, I can probably run something there. Can you send me a link to directions for exactly what to do to gather sniffer logs? I assume you want more than just a tcpdump pcap file?
    3) What firmware and driver logging should be enabled, and how do I do it?
    Best,
    Jonah

  • 0 in reply to Jonah Petri
    Intellectual 320 points
    Apparently a significant portion of these issues are seen by customers with a "Action Tech PK5000 DSL modem/router". This is apparently the stock AP/router for several large ISPs.
  • 0 in reply to Jonah Petri
    TI__Mastermind 27080 points
    I see.. Can, you try to reproduce the issue on your setup with this router? I will also check, if this router was used in WILINK8 IOT tests..
    For taking firmware logs, please review this document : www.ti.com/.../swru435a.pdf
    For sniffer, you would need a WiFi sniffer like, omni peek or similar..

    Thanks
  • 0 in reply to Hari Nagalla
    Intellectual 320 points

    I will try to find one of these — we don't have one in-house.

    Looking at the logs for one such customer, this trouble started with the R8.7 SP2 firmware upgrade, so I think this is going to be a wl18xx firmware issue.  Their connection was stable and fast before the firmware, and now cannot maintain a connection more than 6 hours or so without requiring a reboot.

    I'll report back once I have the AP in house for testing, but please do continue to look from your end.

  • 0 in reply to Jonah Petri
    TI__Mastermind 27080 points
    We, have no reported issues with this AP. We, found one AP of this type in our lab and started iperf test.. so far no issues observed.. We, will continue the test..
    In the mean time, if you are able to reproduce at your end, please let us know..

    Thanks