netdev - mwifiex_sdio and mwifiex failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAA=hcWSRO7Khj8XZbq6fzA6sEN0urR4SeJZh2YcrGe6g8d9ZdA@mail.gmail.com>
Date:   Sat, 13 Nov 2021 15:29:13 +1100
From:   Jupiter <jupiter.hce@...il.com>
To:     linux-wireless <linux-wireless@...r.kernel.org>
Cc:     netdev@...r.kernel.org, Nishant Sarmukadam <nishants@...vell.com>
Subject: mwifiex_sdio and mwifiex failure

Hi,

I am work on a Linux embedded IoT device including both 4G LTE and
WiFi modems, I use linux-firmware-sd8801 and Marvell driver
mwifiex_sdio.ko and mwifiex.ko drivers, it works well for a couple of
days, then the WiFi failed which could be caused by low WiFi signal
strength level, but that should not cause the mwifiex_sdio errors.
While the connman was able to switch from WiFi connection to 4G LTE
connection automatically, following error messages popped up in
console and kernel logs every second to consume lots of resources
despite the 4G LTE being connected and worked perfectly.
...............
[924785.415505] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
[924807.818102] mwifiex_sdio mmc0:0001:1: Ignore scan. Card removed or
firmware in bad state
[924808.406775] mwifiex_sdio mmc0:0001:1: PREP_CMD: card is removed
...........

I am not quite sure if the error message indicated the mwifiex_sdio or
kernel crash or not, but given the 4G LTE was connected fine, the
device was still in good operation, I don't think it is a kernel crash
sign.

My questions are:

(a) Is there any way to recover the mwifiex_sdio or reset
mwifiex_sdio? I tried modprobe -r mwifiex_sdio, modprobe mwifiex_sdio
and modprobe mwifiex, but that crashed my debug console despite the
device was still in good operation. I could only make it recover by
rebooting the device which was not a good solution as it was operated
24 / 7.

(b) If there is no way to recover or reset mwifiex_sdio, are there any
methods to suppress mwifiex_sdio endless error messages to both debug
console and to kernel logs?

Thank you.

Kind regards,

- jh