Comment 16 for bug 373680

Revision history for this message
Bremner (paullinden) wrote : Re: [Bug 373680] Re: network-manager fails periodically , on backgound networks scan?

Quoting bitinerant <email address hidden>:My problem is more connected to the
failure of network manager and possibly the graphics not supporting mozilla
artwork USA in the opening window,My home network is pinging efficiently in
terminal but I can not connect to the web.I have had error messages during the
download of karmic which may be the ultimate cause and I have downloaded it on
several occasions both directly through update manager and via another
comp via
cd.In any case I shall waite untill I receive the official CD and try that
live.
If that fails, I will stick with 9.04 which works fine.

> After installing linux-backports-modules-wireless-karmic-generic a few
> days ago I began experiencing periodic pauses lasting several seconds,
> making working in ssh very cumbersome. Doing a 'ping 192.168.1.1' at
> the same time as 'tail -f /var/log/syslog' makes the pauses obvious and
> displays 'wpa_supplicant[1330]: CTRL-EVENT-SCAN-RESULTS in syslog at the
> end of every pause. Atheros AR5418, kernel 2.6.31-16-generic. Is this
> the same bug?
>
> --
> network-manager fails periodically , on backgound networks scan?
> https://bugs.launchpad.net/bugs/373680
> You received this bug notification because you are subscribed to
> NetworkManager.
>
> Status in NetworkManager: Confirmed
> Status in ?network-manager? package in Ubuntu: New
> 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.
>
>
>