kern/136836: atheros card stops functioning after about 12 hours uptime

[Sam Leffler]

Wes Morgan wrote:
> The following reply was made to PR kern/136836; it has been noted by GNATS.
> 
> From: Wes Morgan <morganw at chemikals.org>
> To: bug-followup at freebsd.org
> Cc:  
> Subject: Re: kern/136836: atheros card stops functioning after about 12 hours
>  uptime
> Date: Fri, 17 Jul 2009 12:58:33 -0500 (CDT)
> 
>  These messages show up in syslog indicating that the card has stopped working:
>  
>  Jul 17 06:35:57 catalyst wpa_supplicant[491]: CTRL-EVENT-EAP-STARTED EAP authentication started
>  Jul 17 06:35:57 catalyst wpa_supplicant[491]: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
>  Jul 17 06:35:57 catalyst wpa_supplicant[491]: OpenSSL: tls_connection_handshake - Failed to read possible Application Data error:00000000:lib(0):func(0):reason(0)
>  Jul 17 06:35:58 catalyst wpa_supplicant[491]: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
>  Jul 17 06:35:58 catalyst wpa_supplicant[491]: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
>  Jul 17 06:35:59 catalyst wpa_supplicant[491]: WPA: Failed to set PTK to the driver.
>  Jul 17 06:35:59 catalyst wpa_supplicant[491]: WPA: Key negotiation completed with 00:40:10:10:00:03 [PTK=CCMP GTK=CCMP]
>  Jul 17 06:37:16 catalyst kernel: nfs server 192.168.0.1:/usr/home/media: not responding
>  Jul 17 06:39:44 catalyst wpa_supplicant[491]: CTRL-EVENT-SCAN-RESULTS 
>  Jul 17 06:41:14 catalyst wpa_supplicant[491]: CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
>  Jul 17 06:41:14 catalyst kernel: wlan0: link state changed to DOWN
>  Jul 17 06:41:15 catalyst kernel: wlan0: link state changed to UP
>  
>  
>  Jul 16 08:00:26 catalyst wpa_supplicant[31662]: CTRL-EVENT-EAP-STARTED EAP authentication started
>  Jul 16 08:00:26 catalyst wpa_supplicant[31662]: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
>  Jul 16 08:00:26 catalyst wpa_supplicant[31662]: OpenSSL: tls_connection_handshake - Failed to read possible Application Data error:00000000:lib(0):func(0):reason(0)
>  Jul 16 08:00:26 catalyst wpa_supplicant[31662]: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
>  Jul 16 08:00:26 catalyst wpa_supplicant[31662]: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
>  Jul 16 08:00:27 catalyst wpa_supplicant[31662]: WPA: Failed to set PTK to the driver.
>  Jul 16 08:00:27 catalyst wpa_supplicant[31662]: WPA: Key negotiation completed with 00:40:10:10:00:03 [PTK=CCMP GTK=CCMP]
>  Jul 16 08:01:45 catalyst kernel: nfs server 192.168.0.1:/usr/home/media: not responding
>  
>  Jul 15 06:25:31 catalyst wpa_supplicant[495]: CTRL-EVENT-EAP-STARTED EAP authentication started
>  Jul 15 06:25:31 catalyst wpa_supplicant[495]: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 13 (TLS) selected
>  Jul 15 06:25:31 catalyst wpa_supplicant[495]: OpenSSL: tls_connection_handshake - Failed to read possible Application Data error:00000000:lib(0):func(0):reason(0)
>  Jul 15 06:25:31 catalyst wpa_supplicant[495]: CTRL-EVENT-EAP-SUCCESS EAP authentication completed successfully
>  Jul 15 06:25:31 catalyst wpa_supplicant[495]: WPA: EAPOL-Key Replay Counter did not increase - dropping packet
>  Jul 15 06:25:32 catalyst wpa_supplicant[495]: WPA: Failed to set PTK to the driver.
>  Jul 15 06:25:32 catalyst wpa_supplicant[495]: WPA: Key negotiation completed with 00:40:10:10:00:03 [PTK=CCMP GTK=CCMP]
>  Jul 15 06:26:50 catalyst kernel: nfs server 192.168.0.1:/usr/home/media: not responding

This looks like another problem I'm working on.  If you do

wlandebug +crypto

to get debug msgs you should see a complaint about not being able to 
plumb the PTK and the key index is > 0.

	Sam