Linux wireless drivers development
 help / color / mirror / Atom feed
From: "René Rebe" <rene@exactcode.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: Amitkumar Karwar <amitkarwar@gmail.com>,
	Nishant Sarmukadam <nishants@marvell.com>,
	Ganapathi Bhat <gbhat@marvell.com>, Xinming Hu <huxm@marvell.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: MWIFIEX still unstable after two years on MS Surface Pro 3
Date: Tue, 5 Dec 2017 13:31:09 +0100	[thread overview]
Message-ID: <a5d827e7-6846-a903-0b1f-55132ddf2631@exactcode.com> (raw)
In-Reply-To: <CAAfyv35EDMmyW_FTJJsNbOweivd=xwDgb=omRA4swQiu4ZXUqQ@mail.gmail.com>

Hi Marek,

thank you for your blazingly fast reply.

On 12/05/2017 12:41 PM, Belisko Marek wrote:
> Hi Rene,
> 
> On Tue, Dec 5, 2017 at 12:06 PM, René Rebe <rene@exactcode.com> wrote:
>> 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
> As workaround you can disable powersave for wifi (using iw command)
> and test it should resolve an issue (at least it fixes for me).

  13:28:18 up  1:52,

Thanks, so far so good. Are you on a Surface, too?
Does this also make mwifiex survive a suspend/resume cycle?
(will try later, when I got work done ;-)

Greetings,
	Rene
-- 
   René Rebe, ExactCODE GmbH, Lietzenburger Str. 42, DE-10117 Berlin
   https://exactcode.com | https://t2sde.org | https://rene.rebe.de

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 11:06 MWIFIEX still unstable after two years on MS Surface Pro 3 René Rebe
2017-12-05 11:41 ` Belisko Marek
2017-12-05 12:31   ` René Rebe [this message]
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=a5d827e7-6846-a903-0b1f-55132ddf2631@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=marek.belisko@gmail.com \
    --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