Can't connect to Wifi after suspend in Asus N56VZ

[Paweł Szafer]

Hello,

After suspend it is impossible to connect WPA2-EAP wireless.

It is what log shows (I changed MAC address and wifi name):
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Activation (wlan0) starting connection 'SOMEWIFI'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Activation (wlan0/wireless): connection 'SOMEWIFI' has security, and secrets exist. No new secrets needed.
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'ssid' value 'SOMEWIFI'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'scan_ssid' value '1'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'bssid' value '00:00:00:00:00:01'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'key_mgmt' value 'WPA-EAP'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'password' value '<omitted>'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'eap' value 'TTLS'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'fragment_size' value '1300'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'phase2' value 'auth=MSCHAPV2'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'identity' value 'username'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'bgscan' value 'simple:30:-45:300'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: added 'proactive_key_caching' value '1'
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> Config: set interface ap_scan to 1
Apr 19 06:00:26 TBH117 NetworkManager[1186]: <info> (wlan0): supplicant interface state: inactive -> scanning
Apr 19 06:00:27 TBH117 wpa_supplicant[1237]: wlan0: SME: Trying to authenticate with 00:00:00:00:00:01 (SSID='SOMEWIFI' freq=2437 MHz)
Apr 19 06:00:27 TBH117 kernel: [25424.715841] wlan0: authenticate with 00:00:00:00:00:01
Apr 19 06:00:27 TBH117 NetworkManager[1186]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 19 06:00:27 TBH117 kernel: [25424.721666] wlan0: direct probe to 00:00:00:00:00:01 (try 1/3)
Apr 19 06:00:27 TBH117 kernel: [25424.922006] wlan0: direct probe to 00:00:00:00:00:01 (try 2/3)
Apr 19 06:00:27 TBH117 kernel: [25425.125894] wlan0: direct probe to 00:00:00:00:00:01 (try 3/3)
Apr 19 06:00:27 TBH117 kernel: [25425.329739] wlan0: authentication with 00:00:00:00:00:01 timed out
Apr 19 06:00:27 TBH117 NetworkManager[1186]: <info> (wlan0): supplicant interface state: authenticating -> disconnected
Apr 19 06:00:27 TBH117 NetworkManager[1186]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Apr 19 06:00:27 TBH117 wpa_supplicant[1237]: wlan0: SME: Trying to authenticate with 00:00:00:00:00:01 (SSID='SOMEWIFI' freq=2437 MHz)
Apr 19 06:00:27 TBH117 kernel: [25425.472763] wlan0: authenticate with 00:00:00:00:00:01
Apr 19 06:00:27 TBH117 kernel: [25425.476999] wlan0: direct probe to 00:00:00:00:00:01 (try 1/3)
Apr 19 06:00:27 TBH117 NetworkManager[1186]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 19 06:00:28 TBH117 kernel: [25425.677596] wlan0: direct probe to 00:00:00:00:00:01 (try 2/3)
Apr 19 06:00:28 TBH117 kernel: [25425.881448] wlan0: direct probe to 00:00:00:00:00:01 (try 3/3)
Apr 19 06:00:28 TBH117 kernel: [25426.085337] wlan0: authentication with 00:00:00:00:00:01 timed out
Apr 19 06:00:28 TBH117 NetworkManager[1186]: <info> (wlan0): supplicant interface state: authenticating -> disconnected

-----

On wireless AP there are not any requests for connection.

To repair this behaviour I need to:
sudo rmmod iwldvm && sudo rmmod iwlwifi && sudo modprobe iwldvm && sudo modprobe iwlwifi

Other info:
cat /proc/version_signature: Ubuntu 3.8.0-19.29-generic 3.8.8

As attachment output of sudo lspci -vnvn
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: pawel 28135 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=445d35a6-fd35-46f2-88ff-e391fb250de9
InstallationDate: Installed on 2013-03-08 (41 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130308)
MachineType: ASUSTeK COMPUTER INC. N56VZ
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcFB:
 0 inteldrmfb
 1 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-19-generic root=UUID=f63c7482-f3fb-4ab7-9983-de52cfa9ba91 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.105
Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo vboxusers
WifiSyslog:

dmi.bios.date: 12/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.216:bd12/06/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N56VZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1170553

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

apport information

[Paweł Szafer (pszafer)]

More info:

router/AP - Asus RT-N66U with Tomato software
Only this one laptop has issue with connection.

After restart it could not connect to WiFi too to and it says "SSID not found"

Maybe it is router issue?

Apr 19 08:15:16 TBH117 NetworkManager[1231]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Apr 19 08:15:16 TBH117 NetworkManager[1231]: <info> Config: set interface ap_scan to 1
Apr 19 08:15:17 TBH117 NetworkManager[1231]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Apr 19 08:15:17 TBH117 wpa_supplicant[1404]: wlan0: SME: Trying to authenticate with 50:46:5d:ce:17:e0 (SSID='tbhydro' freq=2437 MHz)
Apr 19 08:15:17 TBH117 kernel: [ 272.231799] wlan0: authenticate with 50:46:5d:ce:17:e0
Apr 19 08:15:17 TBH117 kernel: [ 272.235901] wlan0: send auth to 50:46:5d:ce:17:e0 (try 1/3)
Apr 19 08:15:17 TBH117 NetworkManager[1231]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Apr 19 08:15:17 TBH117 wpa_supplicant[1404]: wlan0: Trying to associate with 50:46:5d:ce:17:e0 (SSID='tbhydro' freq=2437 MHz)
Apr 19 08:15:17 TBH117 kernel: [ 272.238602] wlan0: authenticated
Apr 19 08:15:17 TBH117 kernel: [ 272.240371] wlan0: associate with 50:46:5d:ce:17:e0 (try 1/3)
Apr 19 08:15:17 TBH117 NetworkManager[1231]: <info> (wlan0): supplicant interface state: authenticating -> associating
Apr 19 08:15:17 TBH117 wpa_supplicant[1404]: wlan0: Associated with 50:46:5d:ce:17:e0
Apr 19 08:15:17 TBH117 kernel: [ 272.244814] wlan0: RX AssocResp from 50:46:5d:ce:17:e0 (capab=0x411 status=0 aid=1)
Apr 19 08:15:17 TBH117 kernel: [ 272.246978] wlan0: associated
Apr 19 08:15:17 TBH117 NetworkManager[1231]: <info> (wlan0): supplicant interface state: associating -> associated
Apr 19 08:15:18 TBH117 wpa_supplicant[1404]: wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
Apr 19 08:15:41 TBH117 NetworkManager[1231]: <warn> Activation (wlan0/wireless): association took too long.
Apr 19 08:15:41 TBH117 NetworkManager[1231]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Apr 19 08:15:41 TBH117 kernel: [ 295.863481] wlan0: deauthenticating from 50:46:5d:ce:17:e0 by local choice (reason=3)
Apr 19 08:15:41 TBH117 NetworkManager[1231]: <warn> Activation (wlan0/wireless): asking for new secrets
Apr 19 08:15:41 TBH117 wpa_supplicant[1404]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=3
Apr 19 08:15:41 TBH117 NetworkManager[1231]: <info> (wlan0): supplicant interface state: associated -> disconnected

It happens every time NM tries to connect,

after that I have to put in /etc/NetworkManager/system-connections/connectionname

add line:
password=password
#otherwise NM would prompt me for password by it won't connect

after adding line I need to restart NM:
sudo service network-manager restart

What do you think about that? Maybe I should report it as another bug of NM (it is stopping on other step of connecting)

[Joseph Salisbury (jsalisbury)]

Did this issue occur in a previous version of Ubuntu, or is this a new issue?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-rc7-raring/

[Paweł Szafer (pszafer)]

I cannot use previous version of Ubuntu because it can't handle N56VZ hardware very well.

I'll test upstream Kernel on Monday.

[Paweł Szafer (pszafer)]

from few days I haven't felt any problems with wifi. Maybe some updates of Ubuntu did the trick.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]