#1343: Atheros AR5212 has awful reception, trouble holding connections
-----------------------------------------+----------------------------------
Reporter: [EMAIL PROTECTED] | Owner:
Type: defect | Status: new
Priority: major | Milestone:
Component: madwifi: driver | Version: v0.9.3
Resolution: | Keywords: atheros, ath_pci,
sensitivity
Patch_attached: 0 |
-----------------------------------------+----------------------------------
Comment (by [EMAIL PROTECTED]):
A dump from the system messages, as recorded from removing the USB mouse
and moving laptop into other room, including the coming back, as of
19:52:28, the reconnecting of the mouse, sitting next to AP.
{{{
Jan 6 19:10:54 be05294 kernel: usb 1-1: USB disconnect, address 4
Jan 6 19:21:09 be05294 NetworkManager: <info> ath0: link timed out.
Jan 6 19:21:09 be05294 NetworkManager: <info> SWITCH: found better
connection 'ath0/linksys' than current connection 'ath0/linksys'.
same_ssid=1, have_link=0
Jan 6 19:21:09 be05294 NetworkManager: <info> Will activate connection
'ath0/linksys'.
Jan 6 19:21:09 be05294 NetworkManager: <info> Device ath0 activation
scheduled...
Jan 6 19:21:09 be05294 NetworkManager: <info> Deactivating device ath0.
Jan 6 19:21:09 be05294 dhclient: wifi0: unknown hardware address type 801
Jan 6 19:21:09 be05294 dhclient: wifi0: unknown hardware address type 801
Jan 6 19:21:09 be05294 dhclient: DHCPRELEASE on ath0 to 10.110.0.2 port
67
Jan 6 19:21:09 be05294 dhcdbd: dhclient 4698 down (9) but si_code == 0
and releasing==0 !
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation (ath0)
started...
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) scheduled...
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) started...
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) scheduled...
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) complete.
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) starting...
Jan 6 19:21:10 be05294 NetworkManager: <info> IBM Wireless - workaround
setting ESSID to linksys
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation
(ath0/wireless): access point 'linksys' is encrypted, but NO valid key
exists. New key needed.
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation (ath0) New
wireless user key requested for network 'linksys'.
Jan 6 19:21:10 be05294 NetworkManager: <info> DHCP daemon state is now
14 (normal exit) for interface ath0
Jan 6 19:21:10 be05294 NetworkManager: <info> DHCP daemon state is now
11 (unknown) for interface ath0
Jan 6 19:21:10 be05294 NetworkManager: <info> DHCP daemon state is now
14 (normal exit) for interface ath0
Jan 6 19:21:10 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) complete.
Jan 6 19:21:10 be05294 avahi-daemon[3361]: Withdrawing address record for
10.110.0.116 on ath0.
Jan 6 19:21:10 be05294 avahi-daemon[3361]: Leaving mDNS multicast group
on interface ath0.IPv4 with address 10.110.0.116.
Jan 6 19:21:10 be05294 avahi-daemon[3361]: iface.c:
interface_mdns_mcast_join() called but no local address available.
Jan 6 19:21:10 be05294 avahi-daemon[3361]: Interface ath0.IPv4 no longer
relevant for mDNS.
Jan 6 19:21:11 be05294 NetworkManager: <info> Activation (ath0) New
wireless user key for network 'linksys' received.
Jan 6 19:21:11 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) scheduled...
Jan 6 19:21:11 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) started...
Jan 6 19:21:11 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) scheduled...
Jan 6 19:21:11 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) complete.
Jan 6 19:21:11 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) starting...
Jan 6 19:21:11 be05294 NetworkManager: <info> IBM Wireless - workaround
setting ESSID to linksys
Jan 6 19:21:11 be05294 NetworkManager: <info> Activation
(ath0/wireless): access point 'linksys' is encrypted, and a key exists.
No new key needed.
Jan 6 19:21:12 be05294 NetworkManager: <info> IBM Wireless - FOUND
DRIVER madwifi
Jan 6 19:21:12 be05294 NetworkManager: <info> Setting wpa_supplicant
driver to madwifi
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'INTERFACE_ADD ath0 madwifi /var/run/wpa_supplicant '
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:21:12 be05294 NetworkManager: <info> IBM Wireless - Setting
AP_SCAN to 1 as this is the default
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'AP_SCAN 1'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'ADD_NETWORK'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was '0'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 ssid 6c696e6b737973'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:21:12 be05294 NetworkManager: <info> IBM Wireless - Setting
SCAN_SSID overwritten by custom settings to 1
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 scan_ssid 1'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 proto WPA2'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 key_mgmt WPA-PSK'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 psk <key>'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: sending command
'ENABLE_NETWORK 0'
Jan 6 19:21:12 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:21:12 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) complete.
Jan 6 19:21:12 be05294 NetworkManager: <info> Activation (ath0/wireless)
Stage 2 of 5 (Device Configure) successful. Connected to access point
'linksys'.
Jan 6 19:21:12 be05294 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) scheduled.
Jan 6 19:21:12 be05294 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) started...
Jan 6 19:21:13 be05294 NetworkManager: <info> Activation (ath0)
Beginning DHCP transaction.
Jan 6 19:21:13 be05294 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) complete.
Jan 6 19:21:13 be05294 NetworkManager: <info> DHCP daemon state is now
12 (successfully started) for interface ath0
Jan 6 19:21:13 be05294 dhclient: wifi0: unknown hardware address type 801
Jan 6 19:21:13 be05294 NetworkManager: <info> DHCP daemon state is now 1
(starting) for interface ath0
Jan 6 19:21:13 be05294 dhclient: wifi0: unknown hardware address type 801
Jan 6 19:21:13 be05294 dhclient: DHCPDISCOVER on ath0 to 255.255.255.255
port 67 interval 8
Jan 6 19:21:21 be05294 dhclient: DHCPDISCOVER on ath0 to 255.255.255.255
port 67 interval 18
Jan 6 19:21:39 be05294 dhclient: DHCPDISCOVER on ath0 to 255.255.255.255
port 67 interval 18
Jan 6 19:21:41 be05294 NetworkManager: <info> Old device 'ath0'
activating, won't change.
Jan 6 19:21:45 be05294 NetworkManager: <info> ath0: link timed out.
Jan 6 19:21:45 be05294 NetworkManager: <info> Old device 'ath0'
activating, won't change.
Jan 6 19:21:57 be05294 dhclient: DHCPDISCOVER on ath0 to 255.255.255.255
port 67 interval 13
Jan 6 19:22:06 be05294 NetworkManager: <info> ath0: link timed out.
Jan 6 19:22:10 be05294 dhclient: DHCPDISCOVER on ath0 to 255.255.255.255
port 67 interval 4
Jan 6 19:22:14 be05294 dhclient: No DHCPOFFERS received.
Jan 6 19:22:14 be05294 dhcdbd: Unrequested down ?:3
Jan 6 19:22:14 be05294 NetworkManager: <info> DHCP daemon state is now
14 (normal exit) for interface ath0
Jan 6 19:22:46 be05294 NetworkManager: <info> ath0: link timed out.
Jan 6 19:22:52 be05294 NetworkManager: <info> Device 'ath0' DHCP
transaction took too long (>99s), stopping it.
Jan 6 19:22:52 be05294 NetworkManager: <info> Activation (ath0) Stage 4
of 5 (IP Configure Timeout) scheduled...
Jan 6 19:22:52 be05294 NetworkManager: <info> Activation (ath0) Stage 4
of 5 (IP Configure Timeout) started...
Jan 6 19:22:52 be05294 NetworkManager: <info> Activation (ath0) failure
scheduled...
Jan 6 19:22:52 be05294 NetworkManager: <info> Activation (ath0) Stage 4
of 5 (IP Configure Timeout) complete.
Jan 6 19:22:52 be05294 NetworkManager: <info> Activation (ath0) failed
for access point (linksys)
Jan 6 19:22:52 be05294 NetworkManager: <info> Activation (ath0) failed.
Jan 6 19:22:52 be05294 NetworkManager: <info> Deactivating device ath0.
Jan 6 19:26:29 be05294 ntpd[4748]: sendto(79.99.122.30) (fd=18): Invalid
argument
Jan 6 19:28:17 be05294 ntpd[4748]: sendto(80.200.240.52) (fd=18): Invalid
argument
Jan 6 19:28:35 be05294 ntpd[4748]: sendto(78.40.96.167) (fd=18): Invalid
argument
Jan 6 19:43:33 be05294 ntpd[4748]: sendto(79.99.122.30) (fd=18): Invalid
argument
Jan 6 19:45:22 be05294 ntpd[4748]: sendto(80.200.240.52) (fd=18): Invalid
argument
Jan 6 19:45:38 be05294 ntpd[4748]: sendto(78.40.96.167) (fd=18): Invalid
argument
Jan 6 19:52:28 be05294 kernel: usb 1-1: new low speed USB device using
uhci_hcd and address 5
Jan 6 19:52:29 be05294 kernel: usb 1-1: configuration #1 chosen from 1
choice
Jan 6 19:52:29 be05294 kernel: input: Logitech Optical USB Mouse as
/class/input/input5
Jan 6 19:52:29 be05294 kernel: input: USB HID v1.10 Mouse [Logitech
Optical USB Mouse] on usb-0000:00:1d.0-1
Jan 6 19:52:50 be05294 NetworkManager: <info> User Switch:
/org/freedesktop/NetworkManager/Devices/ath0 / linksys
Jan 6 19:52:50 be05294 NetworkManager: <info> Deactivating device ath0.
Jan 6 19:52:51 be05294 NetworkManager: <info> Device ath0 activation
scheduled...
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0)
started...
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) scheduled...
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) started...
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) scheduled...
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) complete.
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) starting...
Jan 6 19:52:51 be05294 NetworkManager: <info> IBM Wireless - workaround
setting ESSID to linksys
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation
(ath0/wireless): access point 'linksys' is encrypted, but NO valid key
exists. New key needed.
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) New
wireless user key requested for network 'linksys'.
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) complete.
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) New
wireless user key for network 'linksys' received.
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) scheduled...
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) started...
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) scheduled...
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 1
of 5 (Device Prepare) complete.
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) starting...
Jan 6 19:52:51 be05294 NetworkManager: <info> IBM Wireless - workaround
setting ESSID to linksys
Jan 6 19:52:51 be05294 NetworkManager: <info> Activation
(ath0/wireless): access point 'linksys' is encrypted, and a key exists.
No new key needed.
Jan 6 19:52:52 be05294 NetworkManager: <info> IBM Wireless - FOUND
DRIVER madwifi
Jan 6 19:52:52 be05294 NetworkManager: <info> Setting wpa_supplicant
driver to madwifi
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'INTERFACE_ADD ath0 madwifi /var/run/wpa_supplicant '
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:52:52 be05294 NetworkManager: <info> IBM Wireless - Setting
AP_SCAN to 1 as this is the default
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'AP_SCAN 1'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'ADD_NETWORK'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was '0'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 ssid 6c696e6b737973'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:52:52 be05294 NetworkManager: <info> IBM Wireless - Setting
SCAN_SSID overwritten by custom settings to 1
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 scan_ssid 1'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 proto WPA2'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 key_mgmt WPA-PSK'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'SET_NETWORK 0 psk <key>'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: sending command
'ENABLE_NETWORK 0'
Jan 6 19:52:52 be05294 NetworkManager: <info> SUP: response was 'OK'
Jan 6 19:52:52 be05294 NetworkManager: <info> Activation (ath0) Stage 2
of 5 (Device Configure) complete.
Jan 6 19:52:52 be05294 NetworkManager: <info> Activation (ath0/wireless)
Stage 2 of 5 (Device Configure) successful. Connected to access point
'linksys'.
Jan 6 19:52:52 be05294 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) scheduled.
Jan 6 19:52:52 be05294 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) started...
Jan 6 19:52:54 be05294 NetworkManager: <info> Activation (ath0)
Beginning DHCP transaction.
Jan 6 19:52:54 be05294 NetworkManager: <info> Activation (ath0) Stage 3
of 5 (IP Configure Start) complete.
Jan 6 19:52:54 be05294 NetworkManager: <info> DHCP daemon state is now
12 (successfully started) for interface ath0
Jan 6 19:52:54 be05294 dhclient: wifi0: unknown hardware address type 801
Jan 6 19:52:54 be05294 NetworkManager: <info> DHCP daemon state is now 1
(starting) for interface ath0
Jan 6 19:52:54 be05294 dhclient: wifi0: unknown hardware address type 801
Jan 6 19:52:54 be05294 dhclient: DHCPDISCOVER on ath0 to 255.255.255.255
port 67 interval 3
Jan 6 19:52:54 be05294 dhclient: DHCPOFFER from 10.110.0.2
Jan 6 19:52:54 be05294 dhclient: DHCPREQUEST on ath0 to 255.255.255.255
port 67
Jan 6 19:52:54 be05294 dhclient: DHCPACK from 10.110.0.2
Jan 6 19:52:54 be05294 NetworkManager: <info> DHCP daemon state is now 2
(bound) for interface ath0
Jan 6 19:52:54 be05294 NetworkManager: <info> Activation (ath0) Stage 4
of 5 (IP Configure Get) scheduled...
Jan 6 19:52:54 be05294 NetworkManager: <info> Activation (ath0) Stage 4
of 5 (IP Configure Get) started...
Jan 6 19:52:54 be05294 dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.host_name
Jan 6 19:52:54 be05294 dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_domain
Jan 6 19:52:54 be05294 dhcdbd: message_handler: message handler not found
under /com/redhat/dhcp/ath0 for sub-path ath0.dbus.get.nis_servers
Jan 6 19:52:54 be05294 NetworkManager: <info> Retrieved the following
IP4 configuration from the DHCP daemon:
Jan 6 19:52:54 be05294 NetworkManager: <info> address 10.110.0.116
Jan 6 19:52:54 be05294 NetworkManager: <info> netmask 255.255.255.0
Jan 6 19:52:54 be05294 NetworkManager: <info> broadcast 10.110.0.255
Jan 6 19:52:54 be05294 NetworkManager: <info> gateway 10.110.0.2
Jan 6 19:52:54 be05294 NetworkManager: <info> nameserver 10.110.0.2
Jan 6 19:52:54 be05294 NetworkManager: <info> domain name 'ibm.com'
Jan 6 19:52:54 be05294 NetworkManager: <info> Activation (ath0) Stage 5
of 5 (IP Configure Commit) scheduled...
Jan 6 19:52:54 be05294 NetworkManager: <info> Activation (ath0) Stage 4
of 5 (IP Configure Get) complete.
Jan 6 19:52:54 be05294 NetworkManager: <info> Activation (ath0) Stage 5
of 5 (IP Configure Commit) started...
Jan 6 19:52:54 be05294 avahi-daemon[3361]: New relevant interface
ath0.IPv4 for mDNS.
Jan 6 19:52:54 be05294 avahi-daemon[3361]: Joining mDNS multicast group
on interface ath0.IPv4 with address 10.110.0.116.
Jan 6 19:52:54 be05294 dhclient: bound to 10.110.0.116 -- renewal in
41223 seconds.
Jan 6 19:52:54 be05294 avahi-daemon[3361]: Registering new address record
for 10.110.0.116 on ath0.
Jan 6 19:52:54 be05294 kernel: FIREWALL: IN=ath0 OUT= MAC=
SRC=10.110.0.116 DST=224.0.0.251 LEN=385 TOS=0x00 PREC=0x00 TTL=255 ID=0
DF PROTO=UDP SPT=5353 DPT=5353 LEN=365
Jan 6 19:52:54 be05294 kernel: FIREWALL: IN=ath0 OUT= MAC=
SRC=10.110.0.116 DST=224.0.0.251 LEN=210 TOS=0x00 PREC=0x00 TTL=255 ID=0
DF PROTO=UDP SPT=5353 DPT=5353 LEN=190
Jan 6 19:52:55 be05294 kernel: FIREWALL: IN=ath0 OUT= MAC=
SRC=10.110.0.116 DST=224.0.0.251 LEN=385 TOS=0x00 PREC=0x00 TTL=255 ID=0
DF PROTO=UDP SPT=5353 DPT=5353 LEN=365
Jan 6 19:52:55 be05294 kernel: FIREWALL: IN=ath0 OUT= MAC=
SRC=10.110.0.116 DST=224.0.0.251 LEN=385 TOS=0x00 PREC=0x00 TTL=255 ID=0
DF PROTO=UDP SPT=5353 DPT=5353 LEN=365
Jan 6 19:52:55 be05294 kernel: FIREWALL: IN=ath0 OUT= MAC=
SRC=10.110.0.116 DST=224.0.0.251 LEN=263 TOS=0x00 PREC=0x00 TTL=255 ID=0
DF PROTO=UDP SPT=5353 DPT=5353 LEN=243
Jan 6 19:52:55 be05294 NetworkManager: <info> Activation (ath0)
successful, device activated.
Jan 6 19:52:55 be05294 NetworkManager: <info> Activation (ath0) Finish
handler scheduled.
Jan 6 19:52:55 be05294 NetworkManager: <info> Activation (ath0) Stage 5
of 5 (IP Configure Commit) complete.
Jan 6 19:52:56 be05294 NetworkManager: <info> Setting reconnection
timeout to 60000 msec
}}}
--
Ticket URL: <http://madwifi.org/ticket/1343#comment:37>
madwifi.org <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Madwifi-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/madwifi-tickets
