desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #124931
[Bug 373680] Re: network-manager fails periodically , on backgound networks scan?
lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as "Won't Fix".
** Changed in: network-manager (Ubuntu Lucid)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/373680
Title:
network-manager fails periodically , on backgound networks scan?
Status in NetworkManager:
Fix Released
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Lucid:
Won't Fix
Status in network-manager source package in Maverick:
Fix Released
Status in network-manager package in Fedora:
Invalid
Bug description:
Binary package hint: network-manager
1) The release
Ubuntu version: Ubuntu 9.04 Jaunty Release: 9.04 64 BITS
2) The version of the package you are using
Package affected : network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2
3) What you expected to happen
Estable connection.
If I kill NetworkManager and connect manually to the network using iwconfig , the problem dissapear.
4)What happened instead
Frecuently signal gets interrupted, but not complety disconnected.
I guess it is related with the background network scanning but not sure. I can notice while copying files on local network, watchins streaming movies or with the ping command.
Approximatly each 90-120 seconds , a 5-8 seconds lag is generated.
--> Hardware :
Dell Wireless card 1515
Atheros AR928X chipset
#lspci | grep Atheros
06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)
--> Drivers :
Im not sure. Clean Ubuntu 9.04 installation detected my card, but could not connect to networks until I installed linux-backports-modules-jaunty-generic .
#$ lsmod | grep ath9k
ath9k 311092 0
lbm_cw_mac80211 259000 1 ath9k
led_class 13064 1 ath9k
lbm_cw_cfg80211 85048 2 ath9k,lbm_cw_mac80211
More information:
---------------------------------------------------
->>If I kill NetworkManager and connect manually to the network using
iwconfig , THE PROBLEM DISAPPEAR.
#ping 192.168.0.1 ( my gateway )
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=1.75 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=1.82 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=1.46 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=1.60 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=6802 ms **Here it is the problem
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=5803 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=4803 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=3803 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=2803 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=1803 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=803 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=1.72 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=1.69 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=1.72 ms ** Everything keep normal, but afther 90-120 seconds, the 8 seconds lag happens again, and always like that.
#tail -n0 -f /var/log/syslog
NetworkManager: <debug> [1241785845.002524] periodic_update(): Roamed from BSSID 00:80:5A:4B:89:43 (rosquilla) to (none) ((none))
May 8 14:30:46 xps kernel: [ 2896.176696] wlan0: beacon loss from AP ffff88015e8cfac0 - sending probe request
May 8 14:30:51 xps NetworkManager: <debug> [1241785851.001653] periodic_update(): Roamed from BSSID (none) ((none)) to 00:80:5A:4B:89:43 (rosquilla)
May 8 14:32:45 xps NetworkManager: <debug> [1241785965.004390] periodic_update(): Roamed from BSSID 00:80:5A:4B:89:43 (rosquilla) to (none) ((none))
May 8 14:32:46 xps kernel: [ 3016.169028] wlan0: beacon loss from AP ffff88015e8cfac0 - sending probe request
May 8 14:32:51 xps NetworkManager: <debug> [1241785971.001949] periodic_update(): Roamed from BSSID (none) ((none)) to 00:80:5A:4B:89:43 (rosquilla)
* Note : The delay with the ping command and the syslog events happen at same time.
If i can add any adicional info please tell me what commands to writte
or a link with some help and i will post it.
(Is my first bug report, if im forgetting to add something or not reporting properly please tell me )
Thanks in advanced.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/373680/+subscriptions