From: Maximilian Luz <luzmaximilian@gmail.com>
To: dave@bewaar.me
Cc: amitkarwar@gmail.com, davem@davemloft.net,
ganapathi017@gmail.com, huxinming820@gmail.com,
johannes.berg@intel.com, kuba@kernel.org, kvalo@codeaurora.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, sharvari.harisangam@nxp.com
Subject: Re: [BUG] recursive lock in mwifiex_uninit_sw
Date: Fri, 14 May 2021 15:57:37 +0200 [thread overview]
Message-ID: <bf0c987a-8830-0f44-cf82-bd378e87e000@gmail.com> (raw)
In-Reply-To: <ab4d00ce52f32bd8e45ad0448a44737e@bewaar.me>
On 5/14/21 14:45 AM, dave@bewaar.me wrote:
> A firmware crash of the Marvell 88W8897, which are spurious on Microsoft
> Surface devices, will unload/reset the device. However this can also
> fail
> in more recent kernels, which can cause more problems since the driver
> does not unload. This causes programs trying to reach the network or
> networking devices to hang which in turn causes a reboot/poweroff to
> hang.
>
> This can happen on the following fedora rawhide kernels:
> - 5.12.0-0.rc8.20210423git7af08140979a.193.fc35.x86_64 [1]
> - 5.13.0-0.rc1.20210512git88b06399c9c7.15.fc35.x86_64 [2]
>
> The latter seems to be more consistent in triggering this behaviour
> (and crashing the firmware). If someone can give me some pointers
> I would gladly help and debug this.
I believe the same issue (with slightly different symptoms) is also
reported in
https://lore.kernel.org/linux-wireless/98392296-40ee-6300-369c-32e16cff3725@gmail.com/
See also
https://lore.kernel.org/linux-wireless/522833b9-08c1-f470-a328-0e7419e86617@gmail.com/
for more details.
Regards,
Max
prev parent reply other threads:[~2021-05-14 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 12:45 [BUG] recursive lock in mwifiex_uninit_sw dave
2021-05-14 13:57 ` Maximilian Luz [this message]
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=bf0c987a-8830-0f44-cf82-bd378e87e000@gmail.com \
--to=luzmaximilian@gmail.com \
--cc=amitkarwar@gmail.com \
--cc=dave@bewaar.me \
--cc=davem@davemloft.net \
--cc=ganapathi017@gmail.com \
--cc=huxinming820@gmail.com \
--cc=johannes.berg@intel.com \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sharvari.harisangam@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox