From: Ellie Reeves <ellierevves@gmail.com>
To: Ganapathi Bhat <gbhat@marvell.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"amitkarwar@gmail.com" <amitkarwar@gmail.com>,
Nishant Sarmukadam <nishants@marvell.com>,
Xinming Hu <huxm@marvell.com>
Subject: Re: [EXT] Marvell Mwifiex wireless driver: mwifiex_pcie broken on Marvell ESPRESSOBin
Date: Wed, 22 Nov 2017 08:14:12 -0500 [thread overview]
Message-ID: <6e26f5b1-10a7-b7fc-1518-f0d0f66a50e9@gmail.com> (raw)
In-Reply-To: <4dbd89bbcb0a4706bf3fe7b79025d95c@SC-EXCH02.marvell.com>
Hello,
thanks for the quick answer. To answer Ganapathi's question, all I have
to do in order to trigger the issue is to:
1. Upgrade kernel as usual.
2. Reboot and see the wifi going insane.
If I want to get it working properly I have to:
1. Downgrade kernel to 4.12.12.
2. Make sure initramfs and the uImage for u-boot have been generated for
the 4.12.12 kernel again (my distrubution has a script that takes care
of this).
3. Perform a "shutdown now". A simple soft reboot, and even pressing the
reset button on the ESPRESSObin isn't enough to completely reset the
state, if you reboot this way you will get the "fw is already running !"
message and it will not work. You have to unplug and then replug the
board. After that kernel 4.12.12 will boot and wifi will work.
Here is the dmesg output:
https://paste.xogium.me/view/4dc3bebd
--
Ellie Reeves
next prev parent reply other threads:[~2017-11-22 13:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 15:15 Marvell Mwifiex wireless driver: mwifiex_pcie broken on Marvell ESPRESSOBin Ellie Reeves
2017-11-20 13:53 ` [EXT] " Ganapathi Bhat
2017-11-20 20:51 ` Ellie Reeves
2017-11-22 10:13 ` Ellie Reeves
2017-11-22 12:34 ` Ganapathi Bhat
2017-11-22 13:14 ` Ellie Reeves [this message]
2017-11-30 10:57 ` Ellie Reeves
2017-12-01 15:37 ` Ellie Reeves
2017-12-13 10:34 ` Ganapathi Bhat
2017-12-13 10:46 ` Ellie Reeves
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=6e26f5b1-10a7-b7fc-1518-f0d0f66a50e9@gmail.com \
--to=ellierevves@gmail.com \
--cc=amitkarwar@gmail.com \
--cc=gbhat@marvell.com \
--cc=huxm@marvell.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nishants@marvell.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;
as well as URLs for NNTP newsgroup(s).