From: Julien Cubizolles <j.cubizolles@free.fr>
To: linux-wireless@vger.kernel.org
Subject: Re: firmware in a bad state (module mwifiex)
Date: Wed, 05 Aug 2015 11:12:25 +0200 [thread overview]
Message-ID: <87oaim85fq.fsf@free.fr> (raw)
In-Reply-To: d74ef56802d24c8e90e1b82eb5003172@SC-EXCH04.marvell.com
Amitkumar Karwar <akarwar@marvell.com>
writes:
> This looks like a command timeout problem probably caused due to a bug in firmware.
> How frequently do you see this problem? Are there any specific steps to recreate it?
Surprisingly, it's reproducible:
loading https://github.com/simonwjackson/mcomix/ and clicking on issues
is enough :-)
Should I build the latest driver version from some git repo to further
investigate this problem ?
Regards,
Julien.
next prev parent reply other threads:[~2015-08-05 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-23 13:48 wifi freezing (module mwifiex) Julien Cubizolles
2015-07-27 7:13 ` Amitkumar Karwar
2015-07-27 14:23 ` Julien Cubizolles
2015-08-05 6:30 ` firmware in a bad state " Julien Cubizolles
2015-08-05 8:40 ` Amitkumar Karwar
2015-08-05 9:12 ` Julien Cubizolles [this message]
2015-08-05 9:54 ` Amitkumar Karwar
2015-08-06 6:30 ` Julien Cubizolles
2015-08-06 10:31 ` Amitkumar Karwar
2015-08-07 10:51 ` Amitkumar Karwar
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=87oaim85fq.fsf@free.fr \
--to=j.cubizolles@free.fr \
--cc=linux-wireless@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.