[Bug 822604] New: Wlan broken after hibernation
https://bugzilla.novell.com/show_bug.cgi?id=822604 https://bugzilla.novell.com/show_bug.cgi?id=822604#c0 Summary: Wlan broken after hibernation Classification: openSUSE Product: openSUSE 12.2 Version: Final Platform: x86-64 OS/Version: openSUSE 12.2 Status: NEW Severity: Normal Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: guillaume.gardet@opensuse.org QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20100101 Firefox/21.0 My wlan is working fine on boot, but if I hibernate and then power up, wlan is down. I need to use "systemctl restart network.service" to get it back working. This problem appeared 3 weeks ago or so. lspci give me this ref for my wifi card: 05:06.0 Ethernet controller: Atheros Communications Inc. AR5212/AR5213 Wireless Network Adapter (rev 01) Reproducible: Always Steps to Reproduce: 1. hibernate 2. powerup 3. network is down on wlan Actual Results: wlan is down Expected Results: wlan should be connected -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c
Ye Yuan
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c
David Liang
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c2
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c3
Guillaume GARDET
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c4
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c5
--- Comment #5 from Guillaume GARDET
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c6
Guillaume GARDET
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c7
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c8
Guillaume GARDET
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c9
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c10
Guillaume GARDET
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c11
Matt Chen
Yes I installed it but it had no effect. First boot is working fine, but after hibernation return, it does not work.
'hwinfo ath5k' returns: 'oops: don't know what to do with "ath5k"' Ouch....it was my fault. It was supposed to be "modinfo ath5k", sorry.
'hwinfo --wlan' returns:
29: PCI 506.0: 0282 WLAN controller [Created at pci.319] Unique ID: y9sn.irx8N41FxI2 Parent ID: qscc.ULOo3yhA66C SysFS ID: /devices/pci0000:00/0000:00:14.4/0000:05:06.0 SysFS BusID: 0000:05:06.0 Hardware Class: network Model: "Atheros AR5001X+ Wireless Network Adapter" Vendor: pci 0x168c "Atheros Communications Inc." Device: pci 0x0013 "Atheros AR5001X+ Wireless Network Adapter" SubVendor: pci 0x1385 "Netgear" SubDevice: pci 0x5e00 Revision: 0x01 Driver: "ath5k" Driver Modules: "ath5k" Device File: wlan0 Features: WLAN Memory Range: 0xff300000-0xff30ffff (rw,non-prefetchable) IRQ: 21 (no events) HW Address: 00:14:6c:8a:ca:d0 Link detected: yes WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457 2.462 WLAN encryption modes: WEP40 WEP104 TKIP CCMP WLAN authentication modes: open sharedkey wpa-psk wpa-eap Module Alias: "pci:v0000168Cd00000013sv00001385sd00005E00bc02sc00i00" Driver Info #0: Driver Status: ath5k is active Driver Activation Cmd: "modprobe ath5k" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge)
I also noticed that after hibernation return, I have the following line in dmesg: 'wlan0: deauthenticating from 16:ef:08:09:85:28 by local choice (reason=3)' yes, this is maybe your NetworkManager or wpa_supplicant tried to cut the connection due to some reasons. ( it needs to look deeper)
Wait! so this issue you reported is when you resume from hibernation, the connection is not _reconnect_ ? If so, it would be either NM or wpa_supplicant issue. Not driver issue. There is a easy way to confirm, when you resume from hibernation, try to run " iw wlan0 scan", see if there is anything showed.. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c12
Guillaume GARDET
Hi
(In reply to comment #10)
Yes I installed it but it had no effect. First boot is working fine, but after hibernation return, it does not work.
'hwinfo ath5k' returns: 'oops: don't know what to do with "ath5k"' Ouch....it was my fault. It was supposed to be "modinfo ath5k", sorry.
Here is the modinfo: filename: /lib/modules/3.4.47-2.38-desktop/weak-updates/updates/drivers/net/wireless/ath/ath5k/ath5k.ko license: Dual BSD/GPL description: Support for 5xxx series of Atheros 802.11 wireless LAN cards. author: Nick Kossifidis author: Jiri Slaby version: backported from Linux (v3.11-rc3-0-g5ae90d8) using backports v3.11-rc3-1-0-g4e81a94 srcversion: 2E1F86AAC2D0CC864C47416 alias: pci:v0000168Cd0000FF1Bsv*sd*bc*sc*i* alias: pci:v0000168Cd0000001Dsv*sd*bc*sc*i* alias: pci:v0000168Cd0000001Csv*sd*bc*sc*i* alias: pci:v0000168Cd0000001Bsv*sd*bc*sc*i* alias: pci:v0000168Cd0000001Asv*sd*bc*sc*i* alias: pci:v0000168Cd00000019sv*sd*bc*sc*i* alias: pci:v0000168Cd00000018sv*sd*bc*sc*i* alias: pci:v0000168Cd00000017sv*sd*bc*sc*i* alias: pci:v0000168Cd00000016sv*sd*bc*sc*i* alias: pci:v0000168Cd00000015sv*sd*bc*sc*i* alias: pci:v0000168Cd00000014sv*sd*bc*sc*i* alias: pci:v0000168Cd00001014sv*sd*bc*sc*i* alias: pci:v000010B7d00000013sv*sd*bc*sc*i* alias: pci:v0000A727d00000013sv*sd*bc*sc*i* alias: pci:v0000168Cd00000013sv*sd*bc*sc*i* alias: pci:v0000168Cd00000012sv*sd*bc*sc*i* alias: pci:v0000168Cd00000011sv*sd*bc*sc*i* alias: pci:v0000168Cd00000007sv*sd*bc*sc*i* alias: pci:v0000168Cd00000207sv*sd*bc*sc*i* depends: mac80211,compat,ath,cfg80211 vermagic: 3.4.6-2.10-desktop SMP preempt mod_unload modversions parm: nohwcrypt:Disable hardware encryption. (bool) parm: fastchanswitch:Enable fast channel switching for AR2413/AR5413 radios. (bool) parm: no_hw_rfkill_switch:Ignore the GPIO RFKill switch state (bool) (...)
I also noticed that after hibernation return, I have the following line in dmesg: 'wlan0: deauthenticating from 16:ef:08:09:85:28 by local choice (reason=3)'
yes, this is maybe your NetworkManager or wpa_supplicant tried to cut the connection due to some reasons. ( it needs to look deeper)
Wait! so this issue you reported is when you resume from hibernation, the connection is not _reconnect_ ? If so, it would be either NM or wpa_supplicant issue. Not driver issue.
There is a easy way to confirm, when you resume from hibernation, try to run " iw wlan0 scan", see if there is anything showed..
'iw wlan0 scan' returns: 'command failed: Network is down (-100)' After a 'ifconfig wlan0 up', the command list the wifi networks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c13
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c14
Guillaume GARDET
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c15
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c16
Guillaume GARDET
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c17
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c18
Guillaume GARDET
How do you apply Yast to set up your wifi work ?
Yast > Network Setting > Tradition Method with ifup ?
Yes, this is using this interface. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c19
--- Comment #19 from Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c20
Matt Chen
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c21
Guillaume GARDET
Hmm.....I don't see there is any way in Network Settings to scan and connect to AP items.
How do you connect to a AP ?
In Description Tab (2nd tab), click on the wlan0 interface to select it and then click on Modify button. (names are approximates since my interface is not in english but in french). In the new window, choose DHCP in 2nd tab (Address) and click on Next button. Here you can choose your wifi type (managed), scan networks and provide password. Then click on Next and Ok buttons to save your settings. And your done. You are connected to your wifi box without NM. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c
Jeffrey Cheung
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c22
Jeffrey Cheung
OK, it is apparently a NM issue. NM does not try to bring up the wlan0 interface after hibernation.
Please follow below steps:
1) add "-ddt" to /usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service, looks like:
Exec=/usr/sbin/wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -u -O /var/run/wpa_supplicant -ddddt -f /var/log/wpa_supplicant.log
2) reboot to duplicate this issue.
Would you please provide few files after hibernation ? 1) /var/log/messages 2) /var/log/wpa_supplicant.log 3) /var/log/NetworkManager.
Hi Guillaume, first, just wonder if you try newly released openSUSE 13.1 GA. seocnd, it is better to switch to NM ( you can set from YaST app ) and perform the testing as Matt pretty sure that the problem is related to NM. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c25
--- Comment #25 from Vladimir Botka
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c
Xiyuan Liu
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c27
Guillaume GARDET
https://bugzilla.novell.com/show_bug.cgi?id=822604
https://bugzilla.novell.com/show_bug.cgi?id=822604#c28
Jeffrey Cheung
participants (1)
-
bugzilla_noreply@novell.com