Re: mwifiex won't connect to WPA2 anymore

[Julien Cubizolles]

Dan Williams  writes:


> Ok, at this point the only thing I can think of is the MAC
> randomization that NM has.  Please see:
>
> https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
>
> and look at the section "Randomization during Wi-Fi scanning" where it
> says:
>
> 
> This default behavior can be disabled with a global configuration
> option in NetworkManager.conf:
>
> [device]
> wifi.scan-rand-mac-address=no
> 
>
> if you set that, and restart NetworkManager, does that magically make
> things work?

Yes! It's now working fine, thanks a lot. I have my wifi AP set to only
accept a whitelist of MAC addresses so it makes sense that I can't
connect if the MAC address is random. I'll disable the randomization for
now on.

Julien.

Re: mwifiex won't connect to WPA2 anymore

[Julien Cubizolles]

Dan Williams  writes:


> Just to test, could you add:
>
> auth_alg=OPEN
> key_mgmt=WPA-PSK
> scan_ssid=1
>
> to the block and retry with the supplicant?  I don't know why those
> would make a difference but they might.

They don't: wpa_supplicant still connects with these settings.

Re: mwifiex won't connect to WPA2 anymore

[Julien Cubizolles]

Dan Williams <d...@redhat.com> writes:

> On Wed, 2017-05-03 at 22:33 +0200, Julien Cubizolles wrote:

>> It turns out that the problem lies with NetworkManager, I managed to
>> get
>> the wifi working with wpa_supplicant.
>
> That's odd.  Any idea what that was?  MAC randomization?  

I don't know if MAC randomization is supposed to be happen but ifconfig
always display the same MAC address for the wifi interface. Also the
same wifi router allows connections without secrets with another ssid,
and I have no problem connecting in this case.

> NM just uses the supplicant underneath, so there's no particular
> reason NM wouldn't work but wpa_supplicant itself would.

I'm using the following /etc/wpa_supplicant.conf file:

--8<---cut here---start->8---
ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
network={
priority=2
ssid="beguiled"
psk="*"
}

--8<---cut here---end--->8---

For the same ssid: NetworkManager uses the following
/etc/NetworkManager/system-connections/beguiled

--8<---cut here---start->8---
[connection]
id=beguiled
uuid=4ecc0776-046d-4f05-a324-19f5a8fe6853
type=wifi
permissions=
secondaries=

[wifi]
ssid=beguiled

[wifi-security]
psk=**

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto
--8<---cut here---end--->8---

Here are the logs when NM fails:
--8<---cut here---start->8---

May  4 23:06:25 touco NetworkManager[833]:   [1493931985.8411] device 
(wlx6045bdf646b4): set-hw-addr: set MAC address to E2:D4:E4:49:77:59 (scanning)
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.8433] manager: 
NetworkManager state is now DISCONNECTED
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.8435] device 
(wlx6045bdf646b4): Activation: starting connection 'beguiled' 
(406e52d4-e98b-454b-8d32-ce69fee5e03f)
May  4 23:06:25 touco kernel: [   58.255775] IPv6: ADDRCONF(NETDEV_UP): 
wlx6045bdf646b4: link is not ready
May  4 23:06:25 touco whoopsie[818]: [23:06:25] Cannot reach: 
https://daisy.ubuntu.com
May  4 23:06:25 touco nm-dispatcher: req:2 'down' [wlx6045bdf646b4]: new 
request (2 scripts)
May  4 23:06:25 touco nm-dispatcher: req:2 'down' [wlx6045bdf646b4]: start 
running ordered scripts...
May  4 23:06:25 touco whoopsie[818]: [23:06:25] Cannot reach: 
https://daisy.ubuntu.com
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.8711] 
sup-iface[0x5634f93244e0,wlx6045bdf646b4]: connection disconnected (reason -3)
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.8712] device 
(wlx6045bdf646b4): supplicant interface state: completed -> disconnected
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.8745] device 
(wlx6045bdf646b4): state change: disconnected -> prepare (reason 'none') [30 40 
0]
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.8747] manager: 
NetworkManager state is now CONNECTING
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9016] device 
(wlx6045bdf646b4): set-hw-addr: set-cloned MAC address to 60:45:BD:F6:46:B4 
(permanent)
May  4 23:06:25 touco kernel: [   58.316182] IPv6: ADDRCONF(NETDEV_UP): 
wlx6045bdf646b4: link is not ready
May  4 23:06:25 touco gsd-sharing[2450]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit rygel.service not loaded.
May  4 23:06:25 touco gsd-sharing[2450]: Failed to StopUnit service: 
GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit vino-server.service not 
loaded.
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9314] device 
(wlx6045bdf646b4): state change: prepare -> config (reason 'none') [40 50 0]
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9322] device 
(wlx6045bdf646b4): Activation: (wifi) access point 'beguiled' has security, but 
secrets are required.
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9323] device 
(wlx6045bdf646b4): state change: config -> need-auth (reason 'none') [50 60 0]
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9394] device 
(wlx6045bdf646b4): state change: need-auth -> prepare (reason 'none') [60 40 0]
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9403] device 
(wlx6045bdf646b4): state change: prepare -> config (reason 'none') [40 50 0]
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9406] device 
(wlx6045bdf646b4): Activation: (wifi) connection 'beguiled' has security, and 
secrets exist.  No new secrets needed.
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9406] Config: 
added 'ssid' value 'beguiled'
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9407] Config: 
added 'scan_ssid' value '1'
May  4 23:06:25 touco NetworkManager[833]:   [1493931985.9407] Config: 
added 'key_mgmt' value 'WPA-PSK'
May  4 

Re: mwifiex won't connect to WPA2 anymore

[Julien Cubizolles]

Julien Cubizolles <j.cubizol...@free.fr> writes:

> I can't connect anymore to my home wifi since upgrading my machine from
> Ubuntu 16.10 to Ubuntu 17.04.

It turns out that the problem lies with NetworkManager, I managed to get
the wifi working with wpa_supplicant.

Julien.

mwifiex won't connect to WPA2 anymore

[Julien Cubizolles]

I can't connect anymore to my home wifi since upgrading my machine from
Ubuntu 16.10 to Ubuntu 17.04.

The problem exists with kernel 4.10.0-20-generic from Ubuntu, and
remains with kernel 4.11.0-rc6 that I built from
linux-wireless. However, I can connect to a wifi network without
authentication. In the following logs, beguiled is the SSID of the
WPA-protected I can't connect to and FreeWifi the unprotected one for
which the connection succeeds.

I also copied the firmware files from
git://git.marvell.com/mwifiex-firmware.git, without success.

Here are the relevant lines from syslog. Network manager complains about
a "WRONG_KEY" but obviously I have triple checked the key, simplified
it, and checked that I can succcessfully connect to the same network
from my Android phone.

Let me know if you need anything else to investigate.

Julien.

--8<---cut here---start->8---
Apr 29 17:51:26 touco kernel: [ 1947.432039] usb 3-3: info: trying to associate 
to 'beguiled' bssid f4:ca:e5:ef:be:18
Apr 29 17:51:26 touco wpa_supplicant[1222]: wlx6045bdf646b4: Associated with 
f4:ca:e5:ef:be:18
Apr 29 17:51:26 touco wpa_supplicant[1222]: WMM AC: Missing IEs
Apr 29 17:51:26 touco NetworkManager[986]:   [1493481086.5692] device 
(wlx6045bdf646b4): supplicant interface state: disconnected -> associating
Apr 29 17:51:26 touco NetworkManager[986]:   [1493481086.5694] device 
(wlx6045bdf646b4): supplicant interface state: associating -> 4-way handshake

Apr 29 17:51:30 touco systemd[1]: Reloading OpenBSD Secure Shell server.
Apr 29 17:51:30 touco systemd[1]: Stopping LSB: Start NTP daemon...
Apr 29 17:51:30 touco systemd[1]: Reloaded OpenBSD Secure Shell server.

Apr 29 17:51:30 touco systemd[1]: Reloading.

Apr 29 17:51:30 touco kernel: [ 1951.459673] usb 3-3: info: successfully 
disconnected from f4:ca:e5:ef:be:18: reason code 2
Apr 29 17:51:30 touco kernel: [ 1951.459862] usb 3-3: CMD_RESP: cmd 0x10f 
error, result=0x2
Apr 29 17:51:30 touco wpa_supplicant[1222]: wlx6045bdf646b4: 
CTRL-EVENT-DISCONNECTED bssid=f4:ca:e5:ef:be:18 reason=2
Apr 29 17:51:30 touco wpa_supplicant[1222]: wlx6045bdf646b4: WPA: 4-Way 
Handshake failed - pre-shared key may be incorrect
Apr 29 17:51:30 touco wpa_supplicant[1222]: wlx6045bdf646b4: 
CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="beguiled" auth_failures=1 duration=10 
reason=WRONG_KEY
Apr 29 17:51:30 touco NetworkManager[986]:   [1493481090.5439] 
sup-iface[0x5622b1f28570,wlx6045bdf646b4]: connection disconnected (reason 2)
Apr 29 17:51:30 touco wpa_supplicant[1222]: wlx6045bdf646b4: 
CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
Apr 29 17:51:30 touco NetworkManager[986]:   [1493481090.5511] device 
(wlx6045bdf646b4): supplicant interface state: 4-way handshake -> disconnected
Apr 29 17:51:30 touco NetworkManager[986]:   [1493481090.5523] device 
(wlx6045bdf646b4): Activation: (wifi) disconnected during association, asking 
for new key
Apr 29 17:51:30 touco NetworkManager[986]:   [1493481090.5524] device 
(wlx6045bdf646b4): state change: config -> need-auth (reason 
'supplicant-disconnect') [50 60 8]
Apr 29 17:51:30 touco NetworkManager[986]:   [1493481090.6487] device 
(wlx6045bdf646b4): supplicant interface state: disconnected -> scanning

Apr 29 17:51:33 touco NetworkManager[986]:   [1493481093.3528] device 
(wlx6045bdf646b4): supplicant interface state: scanning -> inactive

Apr 29 17:51:40 touco nm-dispatcher: req:2 'down' [wlx6045bdf646b4]: start 
running ordered scripts...

Apr 29 17:51:40 touco systemd[1]: Started LSB: Start NTP daemon.

Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5363] keyfile: 
update /etc/NetworkManager/system-connections/beguiled 
(4ecc0776-046d-4f05-a324-19f5a8fe6853,"beguiled")
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5443] device 
(wlx6045bdf646b4): state change: need-auth -> prepare (reason 'none') [60 40 0]
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5454] device 
(wlx6045bdf646b4): state change: prepare -> config (reason 'none') [40 50 0]
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5457] device 
(wlx6045bdf646b4): Activation: (wifi) connection 'beguiled' has security, and 
secrets exist.  No new secrets needed.
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5457] Config: 
added 'ssid' value 'beguiled'
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5458] Config: 
added 'scan_ssid' value '1'
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5458] Config: 
added 'key_mgmt' value 'WPA-PSK'
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5458] Config: 
added 'psk' value ''
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.5576] 
sup-iface[0x5622b1f28570,wlx6045bdf646b4]: config: set interface ap_scan to 1
Apr 29 17:51:52 touco NetworkManager[986]:   [1493481112.6146] device 
(wlx6045bdf646b4): supplicant interface state: inactive -> scanning
Apr 29 17:51:55 touco wpa_supplicant[1222]: wlx6045bdf646b4: Trying to 
associate with 

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Amitkumar Karwar  writes:


> Could you check if attached patch fixes your connection problem with WPA AP?

It seems ok so far. I have set my home router back from WPA2 to WPA and
I can successfully connect. I'll let you know if I experience some
problems with it.

Thanks for your 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: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Amitkumar Karwar  writes:


> Thanks for the logs. We found one bug in our code. We expect vendor
> specific IE at the beginning of IE buffer otherwise connection is
> rejected.
> We will prepare a fix and get back.

Thanks a lot for making my laptop usable again. I'll be happy to test
the fix when it's ready.
--
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: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Amitkumar Karwar  writes:

> Thanks for the logs. I compared your network manager log with the one
> on my setup. Both are same. Basically network manager log doesn't show
> security info (WPA/WPA2, encryption mode etc). So we can't rely on
> that.
> I checked your kernel log shared in previous email. It's
> incomplete. It didn't include information when connection was actually
> attempted. Probably you can run "dmesg -c >> dmesg.log" in loop with
> some delay to capture complete info. Otherwise sharing
> "/var/log/messages" is also an option.
> I have created a driver debug patch(attached). Could you please apply it and 
> share complete dmesg log?

I applied your patch. Here are the dmesg logs when logging to a WPA
network with authentification (dmesg-WPA.log, ssid southcentral) and a
network without authentification (dmesg-noWPA.log, ssid FreeWifi).

Let me know if you need anything else.

> Btw, do you see the problem if AP is configured in WPA2 security mode?

Good catch, I changed my access point to WPA2 and now I can connect to
it ! I attached the corresponding dmesg logs (dmesg-WPA2.log, ssid 
southcentral).

> Regards,
> Amitkumar


dmesg-WPA.log
Description: Binary data


dmesg-noWPA.log
Description: Binary data


dmesg-WPA2.log
Description: Binary data

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Dan Williams  writes:

> He actually meant the wpa_supplicant configuration file, not the
> supplicant's dbus config file.  But when driven by NetworkManager, there
> is no supplicant configuration file.

Sorry about that.

> Instead, you can find out what config NM is pushing to the supplicant by
> checking the NetworkManager logs, where NM will log lines like:

Here are the relevant entries from the syslog file:

I included the failed attempt to connect to the WPA protected network
named "southcentral" and the successful one to a non protected one named
"FreeWifi".

--8<---cut here---start->8---
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): 
Activation: starting connection 'southcentral' 
(4c475300-8ffd-4dda-8445-bbd3a9cdc538)
Oct 28 22:27:17 touco dbus[675]: [system] Activating via systemd: service 
name='org.freedesktop.nm_dispatcher' 
unit='dbus-org.freedesktop.nm-dispatcher.service'
Oct 28 22:27:17 touco NetworkManager[656]:   Connection disconnected 
(reason -3)
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): 
supplicant interface state: completed -> disconnected
Oct 28 22:27:17 touco systemd[1]: Starting Network Manager Script Dispatcher 
Service...
Oct 28 22:27:17 touco NetworkManager[656]:   Connection disconnected 
(reason 3)
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): device 
state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): device 
state change: prepare -> config (reason 'none') [40 50 0]
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): 
Activation: (wifi) access point 'southcentral' has security, but secrets are 
required.
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): device 
state change: config -> need-auth (reason 'none') [50 60 0]
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): device 
state change: need-auth -> prepare (reason 'none') [60 40 0]
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): device 
state change: prepare -> config (reason 'none') [40 50 0]
Oct 28 22:27:17 touco NetworkManager[656]:   (wlx6045bdf646b4): 
Activation: (wifi) connection 'southcentral' has security, and secrets exist.  
No new secrets needed.
Oct 28 22:27:17 touco NetworkManager[656]:   Config: added 'ssid' value 
'southcentral'
Oct 28 22:27:17 touco NetworkManager[656]:   Config: added 'scan_ssid' 
value '1'
Oct 28 22:27:17 touco NetworkManager[656]:   Config: added 'key_mgmt' 
value 'WPA-PSK'
Oct 28 22:27:17 touco NetworkManager[656]:   Config: added 'psk' value 
''
Oct 28 22:27:17 touco NetworkManager[656]:   Config: set interface 
ap_scan to 1
Oct 28 22:27:17 touco dbus[675]: [system] Successfully activated service 
'org.freedesktop.nm_dispatcher'
Oct 28 22:27:17 touco nm-dispatcher: Dispatching action 'down' for 
wlx6045bdf646b4
Oct 28 22:27:17 touco systemd[1]: Started Network Manager Script Dispatcher 
Service.
Oct 28 22:27:19 touco ntpd[5268]: Deleting interface #7 wlx6045bdf646b4, 
fe80::6245:bdff:fef6:46b4#123, interface stats: received=0, sent=0, dropped=0, 
active_time=732 secs
Oct 28 22:27:19 touco ntpd[5268]: Deleting interface #3 wlx6045bdf646b4, 
10.2.45.69#123, interface stats: received=0, sent=0, dropped=0, active_time=732 
secs
Oct 28 22:27:19 touco ntpd[5268]: peers refreshed
Oct 28 22:27:21 touco wpa_supplicant[800]: wlx6045bdf646b4: Trying to associate 
with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
Oct 28 22:27:21 touco wpa_supplicant[800]: wlx6045bdf646b4: 
CTRL-EVENT-ASSOC-REJECT status_code=1
Oct 28 22:27:21 touco kernel: [ 1755.971734] usb 1-3: info: trying to associate 
to 'southcentral' bssid f4:ca:e5:ef:be:18
Oct 28 22:27:21 touco kernel: [ 1755.971755] usb 1-3: info: 
mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d
WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
Oct 28 22:27:21 touco kernel: [ 1755.971760] usb 1-3: Incompatible network 
settings
Oct 28 22:27:21 touco kernel: [ 1755.971766] usb 1-3: info: association to 
bssid f4:ca:e5:ef:be:18 failed
Oct 28 22:27:21 touco NetworkManager[656]:   (wlx6045bdf646b4): 
supplicant interface state: disconnected -> scanning
Oct 28 22:27:22 touco wpa_supplicant[800]: wlx6045bdf646b4: 
CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
Oct 28 22:27:25 touco wpa_supplicant[800]: wlx6045bdf646b4: Trying to associate 
with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
Oct 28 22:27:25 touco wpa_supplicant[800]: wlx6045bdf646b4: 
CTRL-EVENT-ASSOC-REJECT status_code=1
Oct 28 22:27:25 touco kernel: [ 1760.400746] usb 1-3: info: trying to associate 
to 'southcentral' bssid f4:ca:e5:ef:be:18
Oct 28 22:27:25 touco kernel: [ 1760.400757] usb 1-3: info: 
mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d
WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
Oct 28 22:27:25 touco kernel: [ 1760.400759] usb 1-3: Incompatible network 
settings
Oct 

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Amitkumar Karwar  writes:

> Hi Julien,
>
>>Yes, I'm using NetworkManager, version 1.0.4-ubuntu5, and I'm guessing
>>it's using wpa_supplicant. I deleted the configuration for this network
>>and created it again. The network is configured for WPA in
>>NetworkManager but I still get the same error message.
>
> Looks like driver has received encryption mode as TKIP, but didn't
> receive WPA ie. Hence the configuration didn't match with AP. Could
> you share wpa_supplicant configuration file if possible? 

Here is /etc/dbus-1/system.d/wpa_supplicant.conf, is this the one you
need ?

--8<---cut here---start->8---
http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd;>

































--8<---cut here---end--->8---

> Also, check if "sme->ie" is received in mwifiex_cfg80211_assoc()
> routine.

Is that what the following debugging is for ? Or should I do something
else ?

> Enable driver debug for the test using "echo 0x >
> /sys/kernel/debug/mwifiex/mlan0/debug_mask" and share dmesg logs.

Please find them attached.

Regards,

Julien.



mwifiex-dmesg.txt.gz
Description: application/gzip

Re: mwifiex problem: incompatible network settings

[Julien Cubizolles]

Dan Williams <d...@redhat.com> writes:

> On Mon, 2015-10-26 at 16:51 +0100, Julien Cubizolles wrote:
>> I can't connect anymore to my home wifi since upgrading my machine from
>> Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
>> from kernel.org without any problem. After the upgrade, and with the
>> same kernel, I couldn't connect anymore. I built 4.3.0-rc7, and the
>> problem remains. However, I can connect to the wifi access point from my
>> Android phone.
>> 
>> Here are the relevant lines from syslog. Let me know if you need more
>> information.
>
> The AP uses WPA, but the driver has been told that WPA is disabled.  Are
> you using wpa_supplicant (or NetworkManager, or something else?) to
> control the WiFi, and if so what version is it?

Yes, I'm using NetworkManager, version 1.0.4-ubuntu5, and I'm guessing
it's using wpa_supplicant. I deleted the configuration for this network
and created it again. The network is configured for WPA in
NetworkManager but I still get the same error message.

Thanks for your help.

--
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

mwifiex problem: incompatible network settings

[Julien Cubizolles]

I can't connect anymore to my home wifi since upgrading my machine from
Ubuntu 15.04 to Ubuntuy 15.10. I was previously running kernel 4.3.0-rc2
from kernel.org without any problem. After the upgrade, and with the
same kernel, I couldn't connect anymore. I built 4.3.0-rc7, and the
problem remains. However, I can connect to the wifi access point from my
Android phone.

Here are the relevant lines from syslog. Let me know if you need more
information.

--8<---cut here---start->8---
Oct 26 16:11:38 touco wpa_supplicant[734]: wlx6045bdf646b4: Trying to associate 
with f4:ca:e5:ef:be:18 (SSID='southcentral' freq=2462 MHz)
Oct 26 16:11:38 touco wpa_supplicant[734]: wlx6045bdf646b4: 
CTRL-EVENT-ASSOC-REJECT status_code=1
Oct 26 16:11:38 touco kernel: [   66.745281] usb 1-3: info: trying to associate 
to 'southcentral' bssid f4:ca:e5:ef:be:18
Oct 26 16:11:38 touco kernel: [   66.745289] usb 1-3: info: 
mwifiex_is_network_compatible: failed: wpa_ie=0xdd wpa2_ie=0x0 WEP=d
WPA=d WPA2=d EncMode=0xfac02 privacy=0x1
Oct 26 16:11:38 touco kernel: [   66.745291] usb 1-3: Incompatible network 
settings
Oct 26 16:11:38 touco kernel: [   66.745294] usb 1-3: info: association to 
bssid f4:ca:e5:ef:be:18 failed
--8<---cut here---end--->8---


The machine is a Microsoft Surface Pro. I've been having a lot of
problems getting the wifi to work but never this particular one, and
they were all fixed in 4.3.0-rc2.

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)

[Julien Cubizolles]

Amitkumar Karwar akar...@marvell.com 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

firmware in a bad state (module mwifiex)

[Julien Cubizolles]

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.

 echo 0x  /sys/kernel/debug/mwifiex/mlan0/debug_mask

Thanks for your help.

Regards,

Julien.

6[0.00] Initializing cgroup subsys cpuset
6[0.00] Initializing cgroup subsys cpu
6[0.00] Initializing cgroup subsys cpuacct
5[0.00] Linux version 4.2.0-rc3 (root@touco) (gcc version 4.9.2 
(Ubuntu 4.9.2-10ubuntu13) ) #3 SMP Mon Jul 27 15:27:49 CEST 2015
6[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-rc3 
root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro quiet splash vt.handoff=7
6[0.00] KERNEL supported cpus:
6[0.00]   Intel GenuineIntel
6[0.00]   AMD AuthenticAMD
6[0.00]   Centaur CentaurHauls
6[0.00] x86/fpu: xstate_offset[2]: 0240, xstate_sizes[2]: 0100
6[0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
6[0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
6[0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
6[0.00] x86/fpu: Enabled xstate features 0x7, context size is 0x340 
bytes, using 'standard' format.
6[0.00] x86/fpu: Using 'eager' FPU context switches.
6[0.00] e820: BIOS-provided physical RAM map:
6[0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
6[0.00] BIOS-e820: [mem 0x0009e000-0x0009] 
reserved
6[0.00] BIOS-e820: [mem 0x0010-0x1fff] usable
6[0.00] BIOS-e820: [mem 0x2000-0x201f] 
reserved
6[0.00] BIOS-e820: [mem 0x2020-0x40003fff] usable
6[0.00] BIOS-e820: [mem 0x40004000-0x40004fff] 
reserved
6[0.00] BIOS-e820: [mem 0x40005000-0xd9202fff] usable
6[0.00] BIOS-e820: [mem 0xd9203000-0xd9671fff] 
reserved
6[0.00] BIOS-e820: [mem 0xd9672000-0xd9681fff] ACPI 
data
6[0.00] BIOS-e820: [mem 0xd9682000-0xda24] ACPI 
NVS
6[0.00] BIOS-e820: [mem 0xda25-0xda66cfff] 
reserved
6[0.00] BIOS-e820: [mem 0xda66d000-0xda6fefff] type 20
6[0.00] BIOS-e820: [mem 0xda6ff000-0xda6f] usable
6[0.00] BIOS-e820: [mem 0xda70-0xda742fff] ACPI 
NVS
6[0.00] BIOS-e820: [mem 0xda743000-0xdad54fff] usable
6[0.00] BIOS-e820: [mem 0xdad55000-0xdaff1fff] 
reserved
6[0.00] BIOS-e820: [mem 0xdaff2000-0xdaff] usable
6[0.00] BIOS-e820: [mem 0xdb80-0xdf9f] 
reserved
6[0.00] BIOS-e820: [mem 0xf800-0xfbff] 
reserved
6[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] 
reserved
6[0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] 
reserved
6[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] 
reserved
6[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] 
reserved
6[0.00] BIOS-e820: [mem 0xff00-0x] 
reserved
6[0.00] BIOS-e820: [mem 0x0001-0x00011f5f] usable
6[0.00] NX (Execute Disable) protection: active
6[0.00] efi: EFI v2.31 by American Megatrends
6[0.00] efi:  ESRT=0xda5f1618  ACPI=0xd9677000  ACPI 2.0=0xd9677000  
SMBIOS=0xda66b198 
6[0.00] esrt: Reserving ESRT space from 0xda5f1618 to 
0xda5f16c8.
6[0.00] SMBIOS 2.7 present.
7[0.00] DMI: Microsoft Corporation Surface with Windows 8 Pro/Surface 
with Windows 8 Pro, BIOS 1.00.0250 01/08/2013
7[0.00] e820: update [mem 0x-0x0fff] usable == reserved
7[0.00] e820: remove [mem 0x000a-0x000f] usable
6[0.00] e820: last_pfn = 0x11f600 max_arch_pfn = 0x4
7[0.00] MTRR default type: uncachable
7[0.00] MTRR fixed ranges enabled:
7[0.00]   0-9 write-back
7[0.00]   A-F uncachable
7[0.00] MTRR variable ranges enabled:
7[0.00]   0 base 0 mask F write-back
7[0.00]   1 base 1 mask FE000 write-back
7[0.00]   2 base 0E000 mask FE000 uncachable
7[0.00]   3 base 0DC00 mask FFC00 uncachable
7[0.00]   4 base 0DB80 mask FFF80 uncachable
7[0.00]   5 base 11F80 mask FFF80 uncachable
7[ 

Re: firmware in a bad state (module mwifiex)

[Julien Cubizolles]

Amitkumar Karwar akar...@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.

--
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: wifi freezing (module mwifiex)

[Julien Cubizolles]

Amitkumar Karwar akar...@marvell.com
writes:

 Hi Julien,

 Thanks for reporting the problem. We now have a separate mechanism for
 debug logs and don't support dynamic debugging anymore.
 Issue below command to enable logs and share them.

 echo 0x  /sys/kernel/debug/mwifiex/mlan0/debug_mask

Thanks, I'll give it a try next time I have a similar problem. But I
have very good (at least for me) news:

 Do you have following USB chipset specific fixes included?
 http://www.spinics.net/lists/linux-wireless/msg129129.html

This one was already included.

 http://www.spinics.net/lists/netdev/msg334367.html

This one wasn't. I applied the patch and so far (after several MB
downloaded) no freeze. Thanks a lot.

I'm surprised that this patch wasn't included in the 4.2.0-rc3. When is
it due ?


--
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

wifi freezing (module mwifiex)

[Julien Cubizolles]

I'm running vanilla kernel 4.2.0-rc3 on a Microsoft Surface Pro. The
wifi (module mwifiex) freezes the whole system after a few seconds of
use. The problem appeared around kernel 3.19.

I've tried to get some debug info with the dynamic debugging method,
using the following:

--8---cut here---start-8---
echo module mwifiex +p  /sys/kernel/debug/dynamic_debug/control
echo module mwifiex_sdio +p  /sys/kernel/debug/dynamic_debug/control
echo module mwifiex_pcie +p  /sys/kernel/debug/dynamic_debug/control
echo module mwifiex_usb +p  /sys/kernel/debug/dynamic_debug/control
--8---cut here---end---8---

and getting the messages with

--8---cut here---start-8---
while true; do dmesg -c  mwifiex_logs.txt; sleep 1; done 
--8---cut here---end---8---

until the system freezes.

Surprisingly, there are very few messages related to mwifiex (see the
following logs). Is there something wrong with the dynamic debugging ?
What other information could I provide ?

Julien.

--8---cut here---start-8---
[0.00] Initializing cgroup subsys cpuset
[0.00] Initializing cgroup subsys cpu
[0.00] Initializing cgroup subsys cpuacct
[0.00] Linux version 4.2.0-040200rc3-generic (kernel@tangerine) (gcc 
version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04) ) #201507192329 SMP Sun Jul 19 
22:32:13 UTC 2015
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.2.0-040200rc3-generic 
root=UUID=919f00b8-5010-46e1-b2f9-c129e17d5312 ro quiet splash vt.handoff=7
[0.00] KERNEL supported cpus:
[0.00]   Intel GenuineIntel
[0.00]   AMD AuthenticAMD
[0.00]   Centaur CentaurHauls
[0.00] x86/fpu: xstate_offset[2]: 0240, xstate_sizes[2]: 0100
[0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
[0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
[0.00] x86/fpu: Enabled xstate features 0x7, context size is 0x340 
bytes, using 'standard' format.
[0.00] x86/fpu: Using 'eager' FPU context switches.
[0.00] e820: BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
[0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
[0.00] BIOS-e820: [mem 0x0010-0x1fff] usable
[0.00] BIOS-e820: [mem 0x2000-0x201f] reserved
[0.00] BIOS-e820: [mem 0x2020-0x40003fff] usable
[0.00] BIOS-e820: [mem 0x40004000-0x40004fff] reserved
[0.00] BIOS-e820: [mem 0x40005000-0xd9202fff] usable
[0.00] BIOS-e820: [mem 0xd9203000-0xd9671fff] reserved
[0.00] BIOS-e820: [mem 0xd9672000-0xd9681fff] ACPI data
[0.00] BIOS-e820: [mem 0xd9682000-0xda24] ACPI NVS
[0.00] BIOS-e820: [mem 0xda25-0xda66cfff] reserved
[0.00] BIOS-e820: [mem 0xda66d000-0xda6fefff] type 20
[0.00] BIOS-e820: [mem 0xda6ff000-0xda6f] usable
[0.00] BIOS-e820: [mem 0xda70-0xda742fff] ACPI NVS
[0.00] BIOS-e820: [mem 0xda743000-0xdad54fff] usable
[0.00] BIOS-e820: [mem 0xdad55000-0xdaff1fff] reserved
[0.00] BIOS-e820: [mem 0xdaff2000-0xdaff] usable
[0.00] BIOS-e820: [mem 0xdb80-0xdf9f] reserved
[0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved
[0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved
[0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved
[0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved
[0.00] BIOS-e820: [mem 0xff00-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00011f5f] usable
[0.00] NX (Execute Disable) protection: active
[0.00] efi: EFI v2.31 by American Megatrends
[0.00] efi:  ESRT=0xda5f1618  ACPI=0xd9677000  ACPI 2.0=0xd9677000  
SMBIOS=0xda66b198 
[0.00] esrt: Reserving ESRT space from 0xda5f1618 to 
0xda5f16c8.
[0.00] SMBIOS 2.7 present.
[0.00] DMI: Microsoft Corporation Surface with Windows 8 Pro/Surface 
with Windows 8 Pro, BIOS 1.00.0250 01/08/2013
[0.00] e820: update [mem 0x-0x0fff] usable == reserved
[0.00] e820: remove [mem 0x000a-0x000f] usable
[0.00] e820: last_pfn = 0x11f600 max_arch_pfn = 0x4
[0.00] MTRR default type: uncachable
[0.00] MTRR