RE: firmware in a bad state (module mwifiex)
Hi Julien,
>
> > Thanks for reporting this. We will take a look at this right away.
> > We don't have significant changes after 4.2.0-rc3.
>
> Well there were the two patches you pointed at that fixed a very serious
> problem for me. Actually are these included in some branch of the main
> kernel git tree ? I couldn't find the commit for
> http://www.spinics.net/lists/netdev/msg334367.html at
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/
>
> > You can try to find older working commit.
>
> I'm afraid that will be difficult since this driver has been broken for
> me since the 3.19 series.
>
> Thanks again for your very precious help.
>
We ran overnight data path stress test, but could not hit any issue. Do you see
command timeout message every time when the problem is hit?
Could you provide some more logs? We had following fixes for timeout issue.
Listing here just in case if you missed them(less likely).
http://www.spinics.net/lists/linux-wireless/msg123959.html
http://www.spinics.net/lists/linux-wireless/msg124366.html
Setup info:
Kernel - 4.2.0-rc4
Chip - USB8797
Firmware - 14.68.29.p38
Regards,
Amitkumar
N�r��yb�X��ǧv�^�){.n�+{��*ޕ�,�{ay� ʇڙ�,j��f���h���z� �w���
���j:+v���w�j�mzZ+�ݢj"��!�i
RE: firmware in a bad state (module mwifiex)
Hi Julien, > From: Julien Cubizolles [mailto:j.cubizol...@free.fr] > Sent: Thursday, August 06, 2015 12:00 PM > To: Amitkumar Karwar > Cc: linux-wireless@vger.kernel.org > Subject: Re: firmware in a bad state (module mwifiex) > > Amitkumar Karwar writes: > > > > Thanks for reporting this. We will take a look at this right away. > > We don't have significant changes after 4.2.0-rc3. > > Well there were the two patches you pointed at that fixed a very serious > problem for me. Actually are these included in some branch of the main > kernel git tree ? I couldn't find the commit for > http://www.spinics.net/lists/netdev/msg334367.html at > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ > I just submitted this critical fix for stable release. Regards, Amit
Re: firmware in a bad state (module mwifiex)
Amitkumar Karwar writes: > Thanks for reporting this. We will take a look at this right away. > We don't have significant changes after 4.2.0-rc3. Well there were the two patches you pointed at that fixed a very serious problem for me. Actually are these included in some branch of the main kernel git tree ? I couldn't find the commit for http://www.spinics.net/lists/netdev/msg334367.html at https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/ > You can try to find older working commit. I'm afraid that will be difficult since this driver has been broken for me since the 3.19 series. Thanks again for your very precious help. Regards, Julien. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: firmware in a bad state (module mwifiex)
Hi Julien, > From: linux-wireless-ow...@vger.kernel.org [mailto:linux-wireless- > ow...@vger.kernel.org] On Behalf Of Julien Cubizolles > Sent: Wednesday, August 05, 2015 2:42 PM > To: linux-wireless@vger.kernel.org > Subject: Re: firmware in a bad state (module mwifiex) > > Amitkumar Karwar > 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 ? > Thanks for reporting this. We will take a look at this right away. We don't have significant changes after 4.2.0-rc3. You can try to find older working commit. Regards, Amitkumar
Re: firmware in a bad state (module mwifiex)
Amitkumar Karwar 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. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: firmware in a bad state (module mwifiex)
Hi Julien, > From: Julien Cubizolles [mailto:j.cubizol...@free.fr] > Sent: Wednesday, August 05, 2015 12:01 PM > To: Amitkumar Karwar > Cc: linux-wireless@vger.kernel.org > Subject: firmware in a bad state (module mwifiex) > > > I'm running kernel 4.2.0-rc3 with the following patches to the mwifiex > driver, thanks to your advice. > > > Do you have following USB chipset specific fixes included? > > http://www.spinics.net/lists/linux-wireless/msg129129.html > > http://www.spinics.net/lists/netdev/msg334367.html > > I've recently noticed that the connection is lost (and the driver too > only rebooting makes the card usable again) when I connect to certain > websites (github for instance) > I've set debugging up with the following command, and attached the > output from dmesg. 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? Regards, Amit -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
