Created attachment 581471 [details] dmesg log Description of problem: The wireless connection is interrupted suddenly. Re-established with a NetworkManager.service restart. Version-Release number of selected component (if applicable): NetworkManager-0.9.4.0-7.git20120403.fc17.x86_64 iwl5000-firmware-8.83.5.1_1-2.fc17.noarch iwl6000-firmware-9.221.4.1-3.fc17.noarch iwl6000g2a-firmware-17.168.5.3-2.fc17.noarch iwl6000g2b-firmware-17.168.5.2-2.fc17.noarch iwl4965-firmware-228.61.2.24-4.fc17.noarch iwl5150-firmware-8.24.2.2-3.fc17.noarch iwl1000-firmware-39.31.5.1-2.fc17.noarch python-iwlib-1.2-1.fc17.x86_64 iwl100-firmware-39.31.5.1-3.fc17.noarch iwl3945-firmware-15.32.2.9-6.fc17.noarch iwl6050-firmware-41.28.5.1-4.fc17.noarch
Created attachment 581472 [details] modinfo about iwlwifi and cfg80211
*** Bug 817927 has been marked as a duplicate of this bug. ***
Can you grab /var/log/messages too from when you experience the issue?
Recently, it doesn't arise again. I hope that's a false problem. Regards.
It appears again. Attach /var/log/messags log. To connect via wifi i had to restart my router.
Created attachment 582426 [details] var/log/messages
This time i can be more accurate. - Wifi connection breaks down suddently (with ath module) - dmesg [22181.913908] hub 2-0:1.0: port 4 disabled by hub (EMI?), re-enabling... [22181.913914] usb 2-4: USB disconnect, device number 3 [22182.021027] wlan1: deauthenticating from a0:21:b7:65:69:62 by local choice (reason=3) [22182.035149] wlan1: moving STA a0:21:b7:65:69:62 to state 2 [22182.035157] wlan1: moving STA a0:21:b7:65:69:62 to state 1 [22182.035163] wlan1: moving STA a0:21:b7:65:69:62 to state 0 [22182.156672] ath: Unable to reset hardware; reset status -5 (freq 2437 MHz) [22182.156947] cfg80211: Calling CRDA to update world regulatory domain [22182.167103] ath: Failed to wakeup in 500us [22182.402711] cfg80211: World regulatory domain updated: [22182.402715] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [22182.402718] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [22182.402721] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [22182.402723] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [22182.402726] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [22182.402729] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [22182.409206] usb 2-4: ath9k_htc: USB layer deinitialized - /var/log/messages section May 6 17:56:44 local kernel: [22181.913908] hub 2-0:1.0: port 4 disabled by hub (EMI?), re-enabling... May 6 17:56:44 local kernel: [22181.913914] usb 2-4: USB disconnect, device number 3 May 6 17:56:45 local kernel: [22182.156672] ath: Unable to reset hardware; reset status -5 (freq 2437 MHz) May 6 17:56:45 local kernel: [22182.156947] cfg80211: Calling CRDA to update world regulatory domain May 6 17:56:45 local kernel: [22182.167103] ath: Failed to wakeup in 500us May 6 17:56:45 local avahi-daemon[519]: Interface wlan1.IPv4 no longer relevant for mDNS. May 6 17:56:45 local avahi-daemon[519]: Leaving mDNS multicast group on interface wlan1.IPv4 with address 192.168.0.3. May 6 17:56:45 local dhclient[2399]: receive_packet failed on wlan1: Network is down May 6 17:56:45 local avahi-daemon[519]: Withdrawing address record for fe80::f6ec:38ff:fe8d:6ba on wlan1. May 6 17:56:45 local avahi-daemon[519]: Withdrawing address record for 192.168.0.3 on wlan1. May 6 17:56:45 local avahi-daemon[519]: Withdrawing workstation service for wlan1. May 6 17:56:45 local kernel: [22182.402711] cfg80211: World regulatory domain updated: May 6 17:56:45 local kernel: [22182.402715] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) May 6 17:56:45 local kernel: [22182.402718] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) May 6 17:56:45 local kernel: [22182.402721] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) May 6 17:56:45 local kernel: [22182.402723] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) May 6 17:56:45 local kernel: [22182.402726] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) May 6 17:56:45 local kernel: [22182.402729] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) May 6 17:56:45 local NetworkManager[1702]: <info> radio killswitch /sys/devices/pci0000:00/0000:00:1d.7/usb2/2-4/2-4:1.0/ieee80211/phy1/rfkill2 disappeared May 6 17:56:45 local kernel: [22182.409206] usb 2-4: ath9k_htc: USB layer deinitialized May 6 17:56:45 local NetworkManager[1702]: <info> (wlan1): now unmanaged May 6 17:56:45 local NetworkManager[1702]: <info> (wlan1): device state change: activated -> unmanaged (reason 'removed') [100 10 36] May 6 17:56:45 local NetworkManager[1702]: <info> (wlan1): deactivating device (reason 'removed') [36] May 6 17:56:45 local NetworkManager[1702]: <info> (wlan1): canceled DHCP transaction, DHCP client pid 2399 May 6 17:56:45 local NetworkManager[1702]: <warn> (5) failed to find interface name for index May 6 17:56:45 local NetworkManager[1702]: nm_system_iface_flush_routes: assertion `iface != NULL' failed May 6 17:56:45 local NetworkManager[1702]: <warn> (5) failed to find interface name for index May 6 17:56:45 local NetworkManager[1702]: <info> (wlan1): cleaning up... May 6 17:56:45 local NetworkManager[1702]: <warn> (5) failed to find interface name for index May 6 17:56:45 local NetworkManager[1702]: (nm-system.c:685):nm_system_iface_get_flags: runtime check failed: (iface != NULL) May 6 17:56:45 local NetworkManager[1702]: <error> [1336319805.544585] [nm-system.c:687] nm_system_iface_get_flags(): (unknown): failed to get interface link object May 6 17:56:45 local dbus-daemon[531]: dbus[531]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) May 6 17:56:45 local dbus[531]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper) May 6 17:56:45 local dbus-daemon[531]: dbus[531]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' May 6 17:56:45 local dbus[531]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' May 6 17:57:44 local dbus-daemon[531]: dbus[531]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) May 6 17:57:44 local dbus[531]: [system] Activating service name='net.reactivated.Fprint' (using servicehelper) May 6 17:57:44 local dbus-daemon[531]: Launching FprintObject May 6 17:57:44 local dbus-daemon[531]: dbus[531]: [system] Successfully activated service 'net.reactivated.Fprint' May 6 17:57:44 local dbus[531]: [system] Successfully activated service 'net.reactivated.Fprint' May 6 17:57:44 local dbus-daemon[531]: ** Message: D-Bus service launched with name: net.reactivated.Fprint May 6 17:57:44 local dbus-daemon[531]: ** Message: entering main loop May 6 17:57:44 local dbus-daemon[531]: ** Message: user 'root' claiming the device: 0 May 6 17:57:44 local dbus-daemon[531]: ** Message: now monitoring fd 10 May 6 17:57:44 local dbus-daemon[531]: ** Message: device 0 claim status 0 May 6 17:57:44 local dbus-daemon[531]: ** Message: no longer monitoring fd 10 May 6 17:57:44 local dbus-daemon[531]: ** Message: released device 0 - NetworkManager.service restarted - Wifi connection re-enabled
(In reply to comment #7) > - Wifi connection breaks down suddently (with ath module) > - dmesg > [22181.913908] hub 2-0:1.0: port 4 disabled by hub (EMI?), re-enabling... > [22181.913914] usb 2-4: USB disconnect, device number 3 So that's your core problem; your laptop is randomly disabling your wifi card. Googling the error message suggests that this may be caused by static electricity (eg, http://softsolder.com/2009/01/28/usb-disconnects-nobody-moves-nobody-gets-hurt/), or by cheap USB cables (though it seems unlikely to be that if this is only affecting an internal USB device). Now, as the end of the message indicates, the kernel re-enables the device after this happens, and so NM *should* be picking it back up again after that happens. I'm not sure why it isn't; there are a few NM error messages in the logs there that might be relevant. But, even if we fix the NM bug, that's just going to mean that your wifi connection is interrupted but then comes right back. There's nothing that can be done (in software) about the disconnection itself, because that's happening at the hardware level.
Therefore an hardware problem in your opinion. However until some weeks ago, this issue didn't exist and also happened with no-USB hardware (e.g. PCI device 07:00.0 Network controller: Intel Corporation WiFi Link 5100). Very strange. Thank you.
(In reply to comment #9) > Therefore an hardware problem in your opinion. I'm just telling you what the logs say... > However until some weeks ago, this issue didn't exist did you drop your laptop or spill soda in its keyboard a few weeks ago? :-) > and also happened with > non-USB hardware (e.g. PCI device 07:00.0 Network controller: Intel Corporation > WiFi Link 5100). Attach logs from that case?
(In reply to comment #10) > (In reply to comment #9) > > Therefore an hardware problem in your opinion. > > I'm just telling you what the logs say... ... and i have just asked you if i understood fine. :) > > However until some weeks ago, this issue didn't exist > > did you drop your laptop or spill soda in its keyboard a few weeks ago? :-) I'm not so careless. > > > and also happened with > > non-USB hardware (e.g. PCI device 07:00.0 Network controller: Intel Corporation > > WiFi Link 5100). > > Attach logs from that case? Yes, https://bugzilla.redhat.com/attachment.cgi?id=581471. If it will appear again, i'll show you /var/log/messages newly. Regards. Antonio
Random tips: - disable power saving: # iwconfig wlan0 power off or # iw dev wlan0 set power_save off - try kernel-3.4.0-1.fc17 from updates testing