ath5k connection loss (failed to wakeup the MAC Chip)

ath5k connection loss (failed to wakeup the MAC Chip)

[Adrian von Bidder]

[-- Attachment #1: Type: text/plain, Size: 19042 bytes --]

Heyho!

(This is using kernel 2.6.31-rc3 as packaged by Debian)

While taking a full backup of my laptop, I noticed that after a few 100M the 
ath5k can't connect to WLAN anymore.

syslog shows:
+++
Jul 28 00:12:59 laeggerli kernel: [187967.601820] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:13:04 laeggerli wpa_supplicant[2574]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jul 28 00:13:04 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> disconnected
Jul 28 00:13:04 laeggerli kernel: [187973.344128] wlan0: no probe response from AP 00:21:29:7c:d6:7e - disassociating
Jul 28 00:13:05 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Jul 28 00:13:06 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:13:06 laeggerli wpa_supplicant[2574]: Trying to associate with 00:21:29:7c:d6:7e (SSID='JUNGBORN' freq=2437 MHz)
Jul 28 00:13:06 laeggerli wpa_supplicant[2574]: Association request to the driver failed
Jul 28 00:13:06 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> associating
Jul 28 00:13:06 laeggerli kernel: [187974.834410] wlan0: authenticate with AP 00:21:29:7c:d6:7e
Jul 28 00:13:06 laeggerli kernel: [187974.835893] wlan0: authenticated
Jul 28 00:13:06 laeggerli kernel: [187974.835902] wlan0: associate with AP 00:21:29:7c:d6:7e
Jul 28 00:13:06 laeggerli kernel: [187974.838825] wlan0: RX ReassocResp from 00:21:29:7c:d6:7e (capab=0x411 status=13 aid=0)
Jul 28 00:13:06 laeggerli kernel: [187974.838839] wlan0: AP denied association (code=13)
Jul 28 00:13:06 laeggerli kernel: [187975.032147] wlan0: associate with AP 00:21:29:7c:d6:7e
Jul 28 00:13:06 laeggerli kernel: [187975.232140] wlan0: associate with AP 00:21:29:7c:d6:7e
Jul 28 00:13:06 laeggerli kernel: [187975.234415] wlan0: RX AssocResp from 00:21:29:7c:d6:7e (capab=0x411 status=0 aid=2)
Jul 28 00:13:06 laeggerli kernel: [187975.234427] wlan0: associated
Jul 28 00:13:06 laeggerli wpa_supplicant[2574]: Associated with 00:21:29:7c:d6:7e
Jul 28 00:13:06 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  associating -> associated
Jul 28 00:13:06 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  associated -> 4-way handshake
Jul 28 00:13:06 laeggerli wpa_supplicant[2574]: WPA: Key negotiation completed with 00:21:29:7c:d6:7e [PTK=CCMP GTK=CCMP]
Jul 28 00:13:06 laeggerli wpa_supplicant[2574]: CTRL-EVENT-CONNECTED - Connection to 00:21:29:7c:d6:7e completed (reauth) [id=0 id_str=]
Jul 28 00:13:06 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  4-way handshake -> group handshake
Jul 28 00:13:06 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Jul 28 00:13:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:15:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:16:57 laeggerli kernel: [188206.300081] CE: hpet increasing min_delta_ns to 22500 nsec
Jul 28 00:17:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:19:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:21:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:23:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:25:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:27:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:29:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:31:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:33:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:35:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:36:33 laeggerli wpa_supplicant[2574]: WPA: Group rekeying completed with 00:21:29:7c:d6:7e [GTK=CCMP]
Jul 28 00:36:33 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> group handshake
Jul 28 00:36:33 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Jul 28 00:37:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:39:50 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:40:39 laeggerli wpa_supplicant[2574]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
Jul 28 00:40:39 laeggerli kernel: [189628.185908] wlan0: no probe response from AP 00:21:29:7c:d6:7e - disassociating
Jul 28 00:40:39 laeggerli kernel: [189628.312377] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:40:39 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> disconnected
Jul 28 00:40:39 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Jul 28 00:40:40 laeggerli kernel: [189628.381965] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:40 laeggerli kernel: [189628.381984] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:40 laeggerli kernel: [189628.419755] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:40 laeggerli kernel: [189628.419771] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:40 laeggerli kernel: [189628.457511] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:40 laeggerli kernel: [189628.457526] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:40 laeggerli kernel: [189628.495260] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:40 laeggerli kernel: [189628.495276] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:40 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:40:45 laeggerli kernel: [189633.901859] __ratelimit: 20 callbacks suppressed
Jul 28 00:40:45 laeggerli kernel: [189633.901872] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:45 laeggerli kernel: [189633.901886] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:45 laeggerli kernel: [189633.939635] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:45 laeggerli kernel: [189633.939651] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:45 laeggerli kernel: [189633.977350] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:45 laeggerli kernel: [189633.977365] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:45 laeggerli kernel: [189634.015105] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:45 laeggerli kernel: [189634.015120] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:45 laeggerli kernel: [189634.052883] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:45 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:40:50 laeggerli kernel: [189639.310908] __ratelimit: 18 callbacks suppressed
Jul 28 00:40:50 laeggerli kernel: [189639.310923] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:40:51 laeggerli kernel: [189639.423590] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:51 laeggerli kernel: [189639.423608] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:51 laeggerli kernel: [189639.461345] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:51 laeggerli kernel: [189639.461361] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:51 laeggerli kernel: [189639.499131] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:51 laeggerli kernel: [189639.499147] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:51 laeggerli kernel: [189639.536910] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:51 laeggerli kernel: [189639.536926] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:51 laeggerli kernel: [189639.574650] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:51 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:40:55 laeggerli NetworkManager: <info>  (wlan0): device state change: 8 -> 3
Jul 28 00:40:55 laeggerli NetworkManager: <info>  (wlan0): deactivating device (reason: 11).
Jul 28 00:40:55 laeggerli NetworkManager: <info>  wlan0: canceled DHCP transaction, dhcp client pid 22348
Jul 28 00:40:55 laeggerli NetworkManager: <info>  (wlan0): removing resolv.conf from /sbin/resolvconf
Jul 28 00:40:55 laeggerli NetworkManager: <WARN>  check_one_route(): (wlan0) error -34 returned from rtnl_route_del(): Sucess#012
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Activation (wlan0) starting connection 'JUNGBORN'
Jul 28 00:40:55 laeggerli NetworkManager: <info>  (wlan0): device state change: 3 -> 4
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 28 00:40:55 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Jul 28 00:40:55 laeggerli NetworkManager: <info>  (wlan0): device state change: 4 -> 5
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Activation (wlan0/wireless): connection 'JUNGBORN' has security, and secrets exist.  No 
new
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Config: added 'ssid' value 'JUNGBORN'
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Config: added 'scan_ssid' value '1'
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Config: added 'key_mgmt' value 'WPA-PSK'
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Config: added 'auth_alg' value 'OPEN'
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Config: added 'psk' value '<omitted>'
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Jul 28 00:40:55 laeggerli NetworkManager: <info>  Config: set interface ap_scan to 1
Jul 28 00:40:56 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Jul 28 00:40:56 laeggerli kernel: [189644.942989] __ratelimit: 19 callbacks suppressed
Jul 28 00:40:56 laeggerli kernel: [189644.943006] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:56 laeggerli kernel: [189644.943025] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:56 laeggerli kernel: [189644.980644] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:56 laeggerli kernel: [189644.980657] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:56 laeggerli kernel: [189645.018382] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:56 laeggerli kernel: [189645.018400] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:56 laeggerli kernel: [189645.056153] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:56 laeggerli kernel: [189645.056169] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:56 laeggerli kernel: [189645.093905] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:40:56 laeggerli kernel: [189645.093920] ath5k phy0: can't reset hardware (-5)
Jul 28 00:40:57 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:41:01 laeggerli kernel: [189650.312282] __ratelimit: 18 callbacks suppressed
Jul 28 00:41:01 laeggerli kernel: [189650.312297] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:41:02 laeggerli kernel: [189650.465854] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:02 laeggerli kernel: [189650.465873] ath5k phy0: can't reset hardware (-5)
Jul 28 00:41:02 laeggerli kernel: [189650.503638] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:02 laeggerli kernel: [189650.503654] ath5k phy0: can't reset hardware (-5)
Jul 28 00:41:02 laeggerli kernel: [189650.541381] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:02 laeggerli kernel: [189650.541397] ath5k phy0: can't reset hardware (-5)
Jul 28 00:41:02 laeggerli kernel: [189650.579152] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:02 laeggerli kernel: [189650.579168] ath5k phy0: can't reset hardware (-5)
Jul 28 00:41:02 laeggerli kernel: [189650.616908] ath5k phy0: failed to wakeup the MAC Chip
...
Jul 28 00:41:19 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:41:21 laeggerli NetworkManager: <info>  Activation (wlan0/wireless): association took too long.
Jul 28 00:41:21 laeggerli NetworkManager: <info>  (wlan0): device state change: 5 -> 6
Jul 28 00:41:21 laeggerli NetworkManager: <info>  Activation (wlan0/wireless): asking for new secrets
Jul 28 00:41:21 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  scanning -> disconnected
Jul 28 00:41:23 laeggerli kernel: [189672.311165] __ratelimit: 18 callbacks suppressed
Jul 28 00:41:23 laeggerli kernel: [189672.311180] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:41:34 laeggerli kernel: [189683.312283] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:41:36 laeggerli NetworkManager: <info>  wlan0: link timed out.
Jul 28 00:41:45 laeggerli kernel: [189694.310974] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:41:49 laeggerli NetworkManager: <info>  (wlan0): supplicant connection state:  disconnected -> scanning
Jul 28 00:41:49 laeggerli kernel: [189697.437887] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:49 laeggerli kernel: [189697.437906] ath5k phy0: can't reset hardware (-5)
Jul 28 00:41:49 laeggerli kernel: [189697.475626] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:49 laeggerli kernel: [189697.475640] ath5k phy0: can't reset hardware (-5)
Jul 28 00:41:49 laeggerli kernel: [189697.513393] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:49 laeggerli kernel: [189697.513410] ath5k phy0: can't reset hardware (-5)
Jul 28 00:41:49 laeggerli kernel: [189697.551173] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:49 laeggerli kernel: [189697.551190] ath5k phy0: can't reset hardware (-5)
Jul 28 00:41:49 laeggerli kernel: [189697.588922] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:41:49 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:41:56 laeggerli kernel: [189705.310991] __ratelimit: 19 callbacks suppressed
Jul 28 00:41:56 laeggerli kernel: [189705.311005] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:42:07 laeggerli kernel: [189716.310940] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:42:18 laeggerli kernel: [189727.311011] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:42:29 laeggerli kernel: [189738.312159] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:42:40 laeggerli kernel: [189749.310972] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:42:51 laeggerli kernel: [189760.310827] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:43:02 laeggerli kernel: [189771.310876] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:43:13 laeggerli kernel: [189782.310957] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:43:24 laeggerli kernel: [189793.310941] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:43:49 laeggerli kernel: [189817.437845] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:43:49 laeggerli kernel: [189817.437864] ath5k phy0: can't reset hardware (-5)
Jul 28 00:43:49 laeggerli kernel: [189817.475614] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:43:49 laeggerli kernel: [189817.475627] ath5k phy0: can't reset hardware (-5)
Jul 28 00:43:49 laeggerli kernel: [189817.513366] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:43:49 laeggerli kernel: [189817.513383] ath5k phy0: can't reset hardware (-5)
Jul 28 00:43:49 laeggerli kernel: [189817.551138] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:43:49 laeggerli kernel: [189817.551153] ath5k phy0: can't reset hardware (-5)
Jul 28 00:43:49 laeggerli kernel: [189817.588901] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:43:49 laeggerli wpa_supplicant[2574]: CTRL-EVENT-SCAN-RESULTS
Jul 28 00:43:57 laeggerli kernel: [189826.310939] __ratelimit: 19 callbacks suppressed
Jul 28 00:43:57 laeggerli kernel: [189826.310954] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:44:08 laeggerli kernel: [189837.310993] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:44:19 laeggerli kernel: [189848.310941] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:44:30 laeggerli kernel: [189859.312331] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:44:41 laeggerli kernel: [189870.310908] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:44:52 laeggerli kernel: [189881.310876] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:45:03 laeggerli kernel: [189892.310988] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:45:14 laeggerli kernel: [189903.311005] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:45:25 laeggerli kernel: [189914.310988] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:45:36 laeggerli kernel: [189925.312394] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:45:47 laeggerli kernel: [189936.310909] ath5k phy0: noise floor calibration timeout (2437MHz)
Jul 28 00:45:49 laeggerli kernel: [189937.437866] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:45:49 laeggerli kernel: [189937.437885] ath5k phy0: can't reset hardware (-5)
Jul 28 00:45:49 laeggerli kernel: [189937.475614] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:45:49 laeggerli kernel: [189937.475628] ath5k phy0: can't reset hardware (-5)
Jul 28 00:45:49 laeggerli kernel: [189937.513360] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:45:49 laeggerli kernel: [189937.513377] ath5k phy0: can't reset hardware (-5)
Jul 28 00:45:49 laeggerli kernel: [189937.551138] ath5k phy0: failed to wakeup the MAC Chip
Jul 28 00:45:49 laeggerli kernel: [189937.551154] ath5k phy0: can't reset hardware (-5)
Jul 28 00:45:49 laeggerli kernel: [189937.588900] ath5k phy0: failed to wakeup the MAC Chip
etc. etc.
+++

This only happens with bulk data transfers, and probably only when sending.  
Downloading large dataset over WLAN is fine (I haven't tested it as much as 
sending, though: downloads are mostly small, while the bulk sending happens 
regularly during backup.)

It is not related to how long the WLAN is up: I can work for days or weeks 
(happened with earlier kernels as well) with this laptop, over 
suspend/resume, and WLAN works fine.  It's only when I run backup that it 
happens (always - but I since backups usually are incremental, they're often 
small enough.  But once I do a full backup WLAN goes down.  So use cable for 
those...)

Is this known?  Can I get you more information?

Hardware is Acer AOA 150.

thanks
-- vbi

-- 
featured link: Debian Bookmark Collection - http://bookmarks.debian.net/



[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 388 bytes --]

Re: ath5k connection loss (failed to wakeup the MAC Chip)

[Maxim Levitsky]

On Tue, 2009-07-28 at 08:38 +0200, Adrian von Bidder wrote:
> Heyho!
> 
> (This is using kernel 2.6.31-rc3 as packaged by Debian)
> 
> While taking a full backup of my laptop, I noticed that after a few 100M the 
> ath5k can't connect to WLAN anymore.

Yep, same here, same hardware.
I must say that moving large files typically results in prolonged
periods in which no communication is gone,  maybe even something like
that.

Best regards,
	Maxim Levitsky

Re: ath5k connection loss (failed to wakeup the MAC Chip)

[Nick Kossifidis]

2009/7/28 Adrian von Bidder <avbidder@fortytwo.ch>:
> Heyho!
>
> (This is using kernel 2.6.31-rc3 as packaged by Debian)
>
> While taking a full backup of my laptop, I noticed that after a few 100M the
> ath5k can't connect to WLAN anymore.
>

[...]

> This only happens with bulk data transfers, and probably only when sending.
> Downloading large dataset over WLAN is fine (I haven't tested it as much as
> sending, though: downloads are mostly small, while the bulk sending happens
> regularly during backup.)
>
> It is not related to how long the WLAN is up: I can work for days or weeks
> (happened with earlier kernels as well) with this laptop, over
> suspend/resume, and WLAN works fine.  It's only when I run backup that it
> happens (always - but I since backups usually are incremental, they're often
> small enough.  But once I do a full backup WLAN goes down.  So use cable for
> those...)
>
> Is this known?  Can I get you more information?
>
> Hardware is Acer AOA 150.
>
> thanks

Working on it, can you please post the part when ath5k loads ?


-- 
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick

Re: ath5k connection loss (failed to wakeup the MAC Chip)

[Adrian von Bidder]

[-- Attachment #1: Type: text/plain, Size: 3005 bytes --]

Hi,

On Wednesday 29 July 2009 01.53:18 Nick Kossifidis wrote:
> 2009/7/28 Adrian von Bidder <avbidder@fortytwo.ch>:
> > Heyho!
> >
> > (This is using kernel 2.6.31-rc3 as packaged by Debian)
> >
> > While taking a full backup of my laptop, I noticed that after a few
> > 100M the ath5k can't connect to WLAN anymore.
>
> Working on it, can you please post the part when ath5k loads ?

$ dmesg | grep -5 ath5
[   10.837434] usbcore: registered new interface driver uvcvideo
[   10.837444] USB Video Class driver (v0.1.0)                  
[   11.058396] Synaptics Touchpad, model: 1, fw: 7.2, id: 0x1c0b1, caps: 0xd04771/0xa40000                                                                      
[   11.100259] ACPI: WMI: Mapper loaded                                         
[   11.116172] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input3                                                                 
[   11.152799] ath5k 0000:03:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[   11.152843] ath5k 0000:03:00.0: setting latency timer to 64
[   11.152938] ath5k 0000:03:00.0: registered as 'phy0'
[   11.160210] acer-wmi: Acer Laptop ACPI-WMI Extras   
[   11.160218] acer-wmi: Blacklisted hardware detected - not loading
[   11.227537] ath: EEPROM regdomain: 0x65                          
[   11.227546] ath: EEPROM indicates we should expect a direct regpair map
[   11.227557] ath: Country alpha2 being used: 00                         
--
[   13.449969] ACPI: Video Device [OVGA] (multi-head: yes  rom: yes  post: no)
[   13.500020] Clocksource tsc unstable (delta = -353758420 ns)               
[   13.602489] ACPI: AC Adapter [ACAD] (on-line)                              
[   13.602714] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input7                                                                      
[   13.872882] phy0: Selected rate control algorithm 'minstrel'                 
[   13.875055] Registered led device: ath5k-phy0::rx
[   13.875106] Registered led device: ath5k-phy0::tx
[   13.875116] ath5k phy0: Atheros AR2425 chip found (MAC: 0xe2, PHY: 0x70)
[   14.047189] HDA Intel 0000:00:1b.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16                                                                               
[   14.047271] HDA Intel 0000:00:1b.0: setting latency timer to 64              
[   14.160144] ACPI: Lid Switch [LID0]                                          
[   14.160386] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input8                                                                    
[   14.160502] ACPI: Sleep Button [SLPB]                                        

(btw, in my case the laptop probably went through suspend to ram/resume 
before I started the backup.  Don't know if that has any influence.)

cheers
-- vbi

cheers
-- vbi

-- 
featured product: ClamAV Antivirus - http://www.clamav.net/


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 388 bytes --]

Re: ath5k connection loss (failed to wakeup the MAC Chip)

[Ben Greear]

I'm not sure if it helps, but if I:

load ath5k and let some stations associate (I'm testing virtual
STA logic)

.. wait a bit ...

rmmod ath5k; modprobe ath5k

then it fails to wakeup the MAC chip every time.

But, if I then wait a few seconds, and repeat the rmmod/modprobe commands, then it wakes
up and works fine.

I'm running a hacked kernel (and ath5k/wifi stack), so could be something
I'm doing wrong, but just maybe it will give you a reproducible test
case...

Thanks,
Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

Re: ath5k connection loss (failed to wakeup the MAC Chip)

[Nick Kossifidis]

2009/7/29 Ben Greear <greearb@candelatech.com>:
> I'm not sure if it helps, but if I:
>
> load ath5k and let some stations associate (I'm testing virtual
> STA logic)
>
> .. wait a bit ...
>
> rmmod ath5k; modprobe ath5k
>
> then it fails to wakeup the MAC chip every time.
>
> But, if I then wait a few seconds, and repeat the rmmod/modprobe commands,
> then it wakes
> up and works fine.
>
> I'm running a hacked kernel (and ath5k/wifi stack), so could be something
> I'm doing wrong, but just maybe it will give you a reproducible test
> case...
>
> Thanks,
> Ben
>

Patch on the way ;-)

-- 
GPG ID: 0xD21DB2DB
As you read this post global entropy rises. Have Fun ;-)
Nick