Latest working kernel version: / Earliest failing kernel version: / Distribution: Arch Linux 2008 Hardware Environment: 00:00.0 Host bridge: ATI Technologies Inc Radeon Xpress 7930 Host Bridge 00:02.0 PCI bridge: ATI Technologies Inc RS7933 PCI Bridge 00:05.0 PCI bridge: ATI Technologies Inc Device 7935 00:06.0 PCI bridge: ATI Technologies Inc RS7936 PCI Bridge 00:07.0 PCI bridge: ATI Technologies Inc Device 7937 00:12.0 SATA controller: ATI Technologies Inc SB600 Non-Raid-5 SATA 00:13.0 USB Controller: ATI Technologies Inc SB600 USB (OHCI0) 00:13.1 USB Controller: ATI Technologies Inc SB600 USB (OHCI1) 00:13.2 USB Controller: ATI Technologies Inc SB600 USB (OHCI2) 00:13.3 USB Controller: ATI Technologies Inc SB600 USB (OHCI3) 00:13.4 USB Controller: ATI Technologies Inc SB600 USB (OHCI4) 00:13.5 USB Controller: ATI Technologies Inc SB600 USB Controller (EHCI) 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 14) 00:14.1 IDE interface: ATI Technologies Inc SB600 IDE 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: ATI Technologies Inc SB600 PCI to LPC Bridge 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge 01:00.0 VGA compatible controller: ATI Technologies Inc M64-S [Mobility Radeon X2300] 02:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01) 05:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8039 PCI-E Fast Ethernet Controller (rev 15) Software Environment: Problem Description: I have an problem with the ath5k modul which is supporting my Atheros 242x chip. I connect my laptop with my Access-Point ( WEP ) with dhcpcd. After some time the modul disconnect me with my access-point with these info out of dmesg : wlan0: No ProbeResp from current AP 00:1d:19:3e:e1:ba - assume out of range just a reboot helps. This is with any other Distribution the same problem Steps to reproduce: None.
I am seeing the same problem on CentOS 5.3 with kernel-2.6.18-128.1.6.el5. After the "assume out of range" message: - The card is dead, iwconfig reports "not associated" - Attempt to do something (e.g. turn the card off, rmmod, etc) results in the call freezing. - Only reboot (hard reboot because of the freeze) helps. The module reports the card as: ath5k phy0: Atheros AR5414 chip found (MAC: 0xa5, PHY: 0x61)
P.S. Forgot to mention - this is on a dual-core 64-bit Athlon
This is normal: if a probe response fails, then you will get disconnected -- this happens with all other wireless hardware. I'm curious why you need to reboot to fix it. Can't you just re-associate with the AP? NetworkManager or wpa_supplicant daemons will do this automatically.
(In reply to comment #1) > I am seeing the same problem on CentOS 5.3 with kernel-2.6.18-128.1.6.el5. > After the "assume out of range" message: > - The card is dead, iwconfig reports "not associated" > - Attempt to do something (e.g. turn the card off, rmmod, etc) results in > the > call freezing. Rmmod hangs, or the whole computer hangs? Can you reproduce this on a vanilla kernel? If the whole computer hangs, try to remove the module while you're on a text VT, and take a picture of the oops if there is one.
I am not sure how to get it to reassociate. In my case, there is no WEP or anything, no NetworkManager, no wpa_supplicant, just plain "ifup" script (that uses ifconfig/iwconfig/etc). If I try to bring the interface down so that I can bring it back up, the process freezes. After that even a simple "iwconfig" (without arguments) would freeze. P.S. Do not have time to mess with vanilla kernel, sorry. P.P.S. For now I removed the ath5k module and installed madwifi - seems to work OK.
(In reply to comment #5) > I am not sure how to get it to reassociate. In my case, there is no WEP or > anything, no NetworkManager, no wpa_supplicant, just plain "ifup" script > (that > uses ifconfig/iwconfig/etc). If I try to bring the interface down so that I > can > bring it back up, the process freezes. After that even a simple "iwconfig" > (without arguments) would freeze. Well, that definitely sounds like some kind of locking problem. However, since I have no idea what centos has in its kernel (2.6.18 is very old -- I assume it is heavily patched), I can't really say if it's a problem in the current kernel or not, except that I haven't seen that here. It is probably worth reporting that to CentOS so others can benefit if they made a back-porting mistake. > P.P.S. For now I removed the ath5k module and installed madwifi - seems to > work OK. Ok - I hope it works better for you in the future.
Disregarding the CentOS problem...FWIW, I think current RHEL kernels fix the issue reported -- http://people.redhat.com/dzickus/el5 Does the original reporter still see this problem with current (i.e. 2.6.30 or later) upstream kernels?
Closed due to lack of response...