All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jérôme Pouiller" <jerome.pouiller@silabs.com>
To: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	"Paweł Lenkow" <pawel.lenkow@camlingroup.com>,
	"Lech Perczak" <lech.perczak@camlingroup.com>
Cc: "Kalle Valo" <kvalo@kernel.org>,
	"Krzysztof Drobiński" <krzysztof.drobinski@camlingroup.com>,
	"Kirill Yatsenko" <kirill.yatsenko@camlingroup.com>
Subject: Re: wfx: Memory corruption during high traffic with WFM200 on i.MX6Q platform
Date: Mon, 12 Sep 2022 18:15:53 +0200	[thread overview]
Message-ID: <3193501.44csPzL39Z@pc-42> (raw)
In-Reply-To: <16b90f1d-69b4-72ac-7018-66d524f514f9@camlingroup.com>

On Monday 12 September 2022 17:16:24 CEST Lech Perczak wrote:
> 
> Hello,
> 
> We're trying to get a WFM200S022XNN3 module working on a custom i.MX6Q board using SDIO interface, using upstream kernel. Our patches concern primarily the device tree for the board - and upstream firmware from linux-firmware repository.
> 
> During that, we stumbled upon a memory corruption issue, which appears when big traffic is passing through the device. Our adapter is running in AP mode. This can be reproduced with 100% rate using iperf3, by starting an AP interface on the device, and an iperf3 server. Then, the client station runs iperf3 with "iperf3 -c <hostname> -t 3600" command - so the AP is sending data for up to one hour, however - the kernel on our device crashes after around a few minutes of traffic, sometimes less than a minute.
> 
> The behaviour is the same on kernel v5.19.7, v5.19.2, and even with v6.0-rc5. Tests on v6.0-rc5 have shown most detailed stacktrace so far:
> 

Hello Lech,

It seems that something somewhere (Ms Exchange, I am looking at you) has
removed all the newlines of your mail :-/. Can you try to fix the problem?
I think that sending mails using base64 encoding would solve the issue.


[...]

-- 
Jérôme Pouiller



  reply	other threads:[~2022-09-12 16:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-12 15:16 wfx: Memory corruption during high traffic with WFM200 on i.MX6Q platform Lech Perczak
2022-09-12 16:15 ` Jérôme Pouiller [this message]
2022-09-12 16:46   ` Lech Perczak
2022-09-15  9:56     ` Lech Perczak
2022-09-15 10:19       ` Jérôme Pouiller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3193501.44csPzL39Z@pc-42 \
    --to=jerome.pouiller@silabs.com \
    --cc=kirill.yatsenko@camlingroup.com \
    --cc=krzysztof.drobinski@camlingroup.com \
    --cc=kvalo@kernel.org \
    --cc=lech.perczak@camlingroup.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.lenkow@camlingroup.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.