Ubuntu
linux package

ath9k - nm-applet don't connect to any network after 2 hours (+-)

Bug #439723 reported by Joan Teixidó
24
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

Ubuntu 9.04, kernel 2.6.28-15-generic
Asus laptop X56V (M51VR)

After one or two hours working, the nm-applet disconnects from wireless network and can't reconnect again. Only when i reboot, nm-applets connects.

I try to stop networking service, disable nm-applet, power off the wifi (it's a laptop)...

My syslog:

Oct 1 00:30:56 asus-portatil NetworkManager: <info> Activation (wlan0/wireless): connection '43+fza' has security, and secrets exist. No new secrets needed.
Oct 1 00:30:56 asus-portatil NetworkManager: <info> Config: added 'ssid' value '43+fza'
Oct 1 00:30:56 asus-portatil NetworkManager: <info> Config: added 'scan_ssid' value '1'
Oct 1 00:30:56 asus-portatil NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Oct 1 00:30:56 asus-portatil NetworkManager: <info> Config: added 'auth_alg' value 'SHARED'
Oct 1 00:30:56 asus-portatil NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Oct 1 00:30:56 asus-portatil NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Oct 1 00:30:56 asus-portatil NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Oct 1 00:30:56 asus-portatil NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Oct 1 00:30:56 asus-portatil NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 1 00:30:56 asus-portatil NetworkManager: <info> Config: set interface ap_scan to 1
Oct 1 00:30:56 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:30:56 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Oct 1 00:30:56 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:30:58 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Oct 1 00:30:58 asus-portatil kernel: [ 8325.105530] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 1
Oct 1 00:30:58 asus-portatil kernel: [ 8325.305062] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 2
Oct 1 00:30:58 asus-portatil kernel: [ 8325.505062] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 3
Oct 1 00:30:59 asus-portatil kernel: [ 8325.705078] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 timed out
Oct 1 00:31:08 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 1 00:31:08 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:31:10 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Oct 1 00:31:10 asus-portatil kernel: [ 8337.473795] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 1
Oct 1 00:31:11 asus-portatil NetworkManager: <info> wlan0: link timed out.
Oct 1 00:31:11 asus-portatil kernel: [ 8337.676105] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 2
Oct 1 00:31:11 asus-portatil kernel: [ 8337.872065] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 3
Oct 1 00:31:11 asus-portatil kernel: [ 8338.072064] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 timed out
Oct 1 00:31:20 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 1 00:31:20 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:31:23 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Oct 1 00:31:23 asus-portatil kernel: [ 8349.780567] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 1
Oct 1 00:31:23 asus-portatil kernel: [ 8349.982112] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 2
Oct 1 00:31:23 asus-portatil kernel: [ 8350.181451] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 3
Oct 1 00:31:23 asus-portatil kernel: [ 8350.381726] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 timed out
Oct 1 00:31:33 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 1 00:31:33 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:31:35 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Oct 1 00:31:35 asus-portatil kernel: [ 8362.213489] wlan0: authenticate with AP 00:03:c9:8d:5b:f5
Oct 1 00:31:35 asus-portatil kernel: [ 8362.412092] wlan0: authenticate with AP 00:03:c9:8d:5b:f5
Oct 1 00:31:35 asus-portatil NetworkManager: <info> wlan0: link timed out.
Oct 1 00:31:36 asus-portatil kernel: [ 8362.613096] wlan0: authenticate with AP 00:03:c9:8d:5b:f5
Oct 1 00:31:36 asus-portatil kernel: [ 8362.812090] wlan0: authentication with AP 00:03:c9:8d:5b:f5 timed out
Oct 1 00:31:45 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 1 00:31:45 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:31:48 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Oct 1 00:31:48 asus-portatil kernel: [ 8374.681112] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 1
Oct 1 00:31:48 asus-portatil kernel: [ 8374.881079] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 2
Oct 1 00:31:48 asus-portatil kernel: [ 8375.080103] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 3
Oct 1 00:31:48 asus-portatil kernel: [ 8375.280111] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 timed out
Oct 1 00:31:56 asus-portatil NetworkManager: <info> Activation (wlan0/wireless): association took too long.
Oct 1 00:31:56 asus-portatil NetworkManager: <info> (wlan0): device state change: 5 -> 6
Oct 1 00:31:56 asus-portatil NetworkManager: <info> Activation (wlan0/wireless): asking for new secrets
Oct 1 00:31:56 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 1 00:32:11 asus-portatil NetworkManager: <info> wlan0: link timed out.
Oct 1 00:33:06 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 1 00:33:23 asus-portatil NetworkManager: <info> (wlan0): device state change: 6 -> 4
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 1 00:33:23 asus-portatil NetworkManager: <info> (wlan0): device state change: 4 -> 5
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Activation (wlan0/wireless): connection '43+fza' has security, and secrets exist. No new secrets needed.
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Config: added 'ssid' value '43+fza'
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Config: added 'scan_ssid' value '1'
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Config: added 'auth_alg' value 'SHARED'
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Config: added 'wep_key0' value '<omitted>'
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Config: added 'wep_tx_keyidx' value '0'
Oct 1 00:33:23 asus-portatil NetworkManager: nm_setting_802_1x_get_pkcs11_engine_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Oct 1 00:33:23 asus-portatil NetworkManager: nm_setting_802_1x_get_pkcs11_module_path: assertion `NM_IS_SETTING_802_1X (setting)' failed
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 1 00:33:23 asus-portatil NetworkManager: <info> Config: set interface ap_scan to 1
Oct 1 00:33:23 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> disconnected
Oct 1 00:33:23 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:33:25 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Oct 1 00:33:25 asus-portatil kernel: [ 8472.217459] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 1
Oct 1 00:33:25 asus-portatil kernel: [ 8472.417060] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 2
Oct 1 00:33:26 asus-portatil kernel: [ 8472.617056] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 3
Oct 1 00:33:26 asus-portatil kernel: [ 8472.816061] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 timed out
Oct 1 00:33:35 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: associating -> disconnected
Oct 1 00:33:35 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: disconnected -> scanning
Oct 1 00:33:38 asus-portatil NetworkManager: <info> (wlan0): supplicant connection state: scanning -> associating
Oct 1 00:33:38 asus-portatil kernel: [ 8484.586944] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 1
Oct 1 00:33:38 asus-portatil kernel: [ 8484.784104] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 2
Oct 1 00:33:38 asus-portatil kernel: [ 8484.985097] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 try 3
Oct 1 00:33:38 asus-portatil kernel: [ 8485.184620] wlan0: direct probe to AP 00:03:c9:8d:5b:f5 timed out

and continues...

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
IfupdownConfig:
 auto lo
 iface lo inet loopback
NonfreeKernelModules: fglrx
Package: network-manager 0.7.1~rc4.1.cf199a964-0ubuntu2
ProcEnviron:
 PATH=(custom, user)
 LANG=ca_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
Uname: Linux 2.6.28-15-generic i686

Revision history for this message
Joan Teixidó (joanteixido) wrote :
Revision history for this message
Joan Teixidó (joanteixido) wrote :

In syslog.txt, the problems begins after a disconnectation at line Oct 1 00:28:52

Revision history for this message
Alexander Sack (asac) wrote :

howard, is this the ath9k bug you referred to?

summary: - nm-applet don't connect to any network after 2 hours (+-)
+ ath9k - nm-applet don't connect to any network after 2 hours (+-)
Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Howard Chu (hyc) wrote :

Actually I was referring to Bug #414560

However now that you mention it, I've seen the symptoms described here as well. My guess is these are caused by the same bug.

Revision history for this message
Howard Chu (hyc) wrote :
Download full text (5.7 KiB)

Note - I've killed NetworkManager and the issue still remains. This is an ath9k driver bug, not a NetworkManager bug.

Sep 30 23:15:11 violino kernel: [329813.143845] wlan0: no probe response from AP 00:12:17:26:56:10 - disassociating
Sep 30 23:15:17 violino kernel: [329818.803730] wlan0: authenticate with AP 00:12:17:26:56:10
Sep 30 23:15:17 violino kernel: [329818.806118] wlan0: authenticated
Sep 30 23:15:17 violino kernel: [329818.806145] wlan0: associate with AP 00:12:17:26:56:10
Sep 30 23:15:17 violino kernel: [329818.810114] wlan0: RX ReassocResp from 00:12:17:26:56:10 (capab=0x431 status=0 aid=2)
Sep 30 23:15:17 violino kernel: [329818.810250] wlan0: associated
Oct 1 02:17:26 violino kernel: [340747.876038] wlan0: no probe response from AP 00:12:17:26:56:10 - disassociating
Oct 1 02:17:32 violino kernel: [340753.543467] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
Oct 1 02:17:32 violino kernel: [340753.552914] wlan0: authenticate with AP 00:12:17:26:56:10
Oct 1 02:17:32 violino kernel: [340753.553687] wlan0: authenticated
Oct 1 02:17:32 violino kernel: [340753.553712] wlan0: associate with AP 00:12:17:26:56:10
Oct 1 02:17:32 violino kernel: [340753.556806] wlan0: RX ReassocResp from 00:12:17:26:56:10 (capab=0x431 status=0 aid=2)
Oct 1 02:17:32 violino kernel: [340753.556806] wlan0: associated
Oct 1 02:53:36 violino kernel: [342917.805911] wlan0: no probe response from AP 00:12:17:26:56:10 - disassociating
Oct 1 02:53:42 violino kernel: [342923.475754] wlan0: authenticate with AP 00:12:17:26:56:10
Oct 1 02:53:42 violino kernel: [342923.476639] wlan0: authenticated
Oct 1 02:53:42 violino kernel: [342923.476639] wlan0: associate with AP 00:12:17:26:56:10
Oct 1 02:53:42 violino kernel: [342923.479881] wlan0: RX ReassocResp from 00:12:17:26:56:10 (capab=0x431 status=0 aid=2)
Oct 1 02:53:42 violino kernel: [342923.479881] wlan0: associated
Oct 1 03:00:21 violino kernel: [343322.409166] wlan0: no probe response from AP 00:12:17:26:56:10 - disassociating
Oct 1 03:00:26 violino kernel: [343328.065713] wlan0: authenticate with AP 00:12:17:26:56:10
Oct 1 03:00:26 violino kernel: [343328.067280] wlan0: authenticated
Oct 1 03:00:26 violino kernel: [343328.067288] wlan0: associate with AP 00:12:17:26:56:10
Oct 1 03:00:26 violino kernel: [343328.069856] wlan0: RX ReassocResp from 00:12:17:26:56:10 (capab=0x431 status=0 aid=2)
Oct 1 03:00:26 violino kernel: [343328.069864] wlan0: associated
Oct 1 05:31:16 violino kernel: [352377.844929] wlan0: no probe response from AP 00:12:17:26:56:10 - disassociating
Oct 1 05:31:22 violino kernel: [352383.502306] wlan0: authenticate with AP 00:12:17:26:56:10
Oct 1 05:31:22 violino kernel: [352383.504054] wlan0: authenticated
Oct 1 05:31:22 violino kernel: [352383.504054] wlan0: associate with AP 00:12:17:26:56:10
Oct 1 05:31:22 violino kernel: [352383.505970] wlan0: RX ReassocResp from 00:12:17:26:56:10 (capab=0x431 status=0 aid=2)
Oct 1 05:31:22 violino kernel: [352383.506007] wlan0: associated
Oct 1 05:38:01 violino kernel: [352782.821565] wlan0: no probe response from AP 00:12:17:26:56:10 - disassociating
Oct 1 05:38:07 violino kernel: [352788.478100] wlan0...

Read more...

Revision history for this message
Joan Teixidó (joanteixido) wrote :

I read the Bug #414560 and from my little experience think that is the same issue. I read in the #414560 bug description:

"Performance drops significantly when this starts going on. At times it becomes impossible to look up hosts, etc. Other times, it will run fine for hours on en"

i've the same problem. The bit rate downs from 11Mb/s to 1Mb/s and after a unknow... and then begins the disassociations.

Can i help trying something?

Joan

Alexander Sack (asac)
affects: network-manager (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Hi Joan,

I'm a bit hesitant to mark this bug as a duplicate of bug 414560 mainly because reporters in bug 414560 seem to indicate that the 2.6.28 jaunty kernel is stable for them whereas you reported this issue against the 2.6.28 jaunty kernel. Have you since been able to test the newer 2.6.31 based Karmic kernel? Does the issue remain? ISO CD images can be found at http://cdimage.ubuntu.com/releases/karmic . Please let us know. Thanks!

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Alexander Sack (asac) wrote :

Leann, afaik Howard Chu is running ath9k from latest karmic kernel.

Revision history for this message
Howard Chu (hyc) wrote :

That's right. I've also tried ath9k drivers from wireless-testing up to 2009-09-23. There hasn't been anything newer for ath9k that I'm aware of.

Possibly there are two bugs at work in this bug report. The NetworkManager background scanning issue also had an extremely bad effect on the ath9k stability, and that certainly was still occurring in early jaunty. I don't recall if you guys patched it or not; I patched my own build of NM to turn off background scanning.

The reason I still wound up turning off NetworkManager in my current setup is because, whenever the ath9k driver said "no probe response" it would tell NM that it was disconnecting. NM would then pass this on to Dbus and all of my other apps (like pidgin) would disconnect. But this app disconnect was unnecessary - the ath9k driver would successfully reassociate within a few seconds. I was tired of pidgin always logging out and logging in again, when it would otherwise just ride out the outage and continue as if nothing had happened once the driver reassociated. (There's a reason the TCP RFCs say hosts MUST NOT drop a connection in response to particular lower level error events. This completely invalidates TCP's timeout mechanisms, and that's just Wrong.) That's a separate issue, I just don't know if it's an NM bug (should NM wait before reporting the network is unavailable) or an app bug (should DBus/NM-aware apps treat the "network down" event as just advisory, and not act on it immediately). I guess I can file a new bug to discuss that.

Revision history for this message
Ralf-Peter (ralfpeter-rohbeck) wrote :

I have this issue with Karmic (2.6.31-16) on an Eee PC 1005HA.

There are two separate bugs:
1. ath9k stops working. What you typically see is that it can't reconnect after it lost connection (I can reproduce that 100% by running my microwave) but it can also happen as a result of the "DMA failed to stop in 10 ms" problem. What you see is
Jan 10 17:52:58 eeepc kernel: [20874.572107] wlan0: direct probe to AP xx:xx:xx:xx:xx:xx timed out
The AP is a NetGear WNDR3700 FWIW.

sudo rmmod ath9k;sudo modprobe ath9k
fixes this.

2. Also, nm-applet gives up and displays the WEP code entry box (erroneously but maybe the return code from the driver is wrong), but even if you enter the correct WEP code it won't reconnect. This is fixed most easily by killing and restarting nm-applet:
pkill nm-applet;nm-applet &

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.