Linux wireless drivers development
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.com>
To: Amitkumar Karwar <amitkarwar@gmail.com>,
	Nishant Sarmukadam <nishants@marvell.com>,
	Ganapathi Bhat <gbhat@marvell.com>, Xinming Hu <huxm@marvell.com>
Cc: linux-wireless@vger.kernel.org
Subject: MWIFIEX still unstable after two years on MS Surface Pro 3
Date: Tue, 5 Dec 2017 12:06:38 +0100	[thread overview]
Message-ID: <d776bc3d-7712-8430-93e2-72e4b6bbf23c@exactcode.com> (raw)

Hi all,

I write to start a discussion about the state of the mwifiex driver.
For over two years many other and me wait that the driver finally 
becomes "stable". However, even with kernel 4.14.2 it still fails after 
some minutes, or latest after some hours. With various stray errors in 
the system log:

Dec  5 09:50:50 surface3 kernel: mwifiex_pcie 0000:01:00.0: info: 
MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p119)
Dec  5 09:50:50 surface3 kernel: mwifiex_pcie 0000:01:00.0: 
driver_version = mwifiex 1.0 (15.68.7.p119)

Dec  5 10:38:28 surface3 kernel: mwifiex_pcie 0000:01:00.0: info: trying 
to associate to 'XXX' bssid xx:xx:xx:xx:xx:xx
Dec  5 10:38:28 surface3 kernel: mwifiex_pcie 0000:01:00.0: info: 
associated to bssid xx:xx:xx:xx:xx:xx successfully
...
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: Firmware 
wakeup failed
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: PREP_CMD: FW 
in reset state
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: PREP_CMD: 
card is removed
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: deleting the 
crypto keys
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: PREP_CMD: 
card is removed
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: deleting the 
crypto keys
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: PREP_CMD: 
card is removed
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: deleting the 
crypto keys
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: PREP_CMD: 
card is removed
Dec  5 10:42:51 surface3 kernel: mwifiex_pcie 0000:01:00.0: deleting the 
crypto keys

Also, rmmod usually then hangs, and even if it eventually force unloads 
and such re-loading the module does not even get it back into some 
working state. Not even with echoing 1 into the pci reset file.

If this firmware and driver is already for years not working very 
stable, can this not at least recover more gracefully?

Any suggestions how to finally address and solve these issues are welcome.

If someone needs more logs and debug fluff let me know to generate it as 
necessary.

For what it is worth, at least the USB attached mwifi chip in the 
Surface 2 appears to work more reliable with the Linux driver.

Best regards,
	René Rebe

-- 
   René Rebe, ExactCODE GmbH, Lietzenburger Str. 42, DE-10117 Berlin
   http://exactcode.com | http://t2-project.org | http://rene.rebe.de

             reply	other threads:[~2017-12-05 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 11:06 René Rebe [this message]
2017-12-05 11:41 ` MWIFIEX still unstable after two years on MS Surface Pro 3 Belisko Marek
2017-12-05 12:31   ` René Rebe
2017-12-05 12:53     ` Belisko Marek

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=d776bc3d-7712-8430-93e2-72e4b6bbf23c@exactcode.com \
    --to=rene@exactcode.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