Description of problem: Ever since the kernel-2.6.24.3-13.fc8 kernel update I've been experiencing the following problem, I can connect to my WPA2 network but after a while connection is lost and cannot be reestablished without issuing rmmod rt61pci. The following is in dmesg: wlan0: disassociate(reason=3) wlan0: disassociate(reason=3) wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:1c:10:9a:4e:de wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:1c:10:9a:4e:de wlan0: RX authentication from 00:1c:10:9a:4e:de (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:1c:10:9a:4e:de wlan0: authentication frame received from 00:1c:10:9a:4e:de, but not in authenticate state - ignored wlan0: RX AssocResp from 00:1c:10:9a:4e:de (capab=0x411 status=0 aid=2) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready ACPI: Unable to turn cooling device [ffff81007fb329a0] 'on' wlan0: RX deauthentication from 00:1c:10:9a:4e:de (reason=15) wlan0: deauthenticated wlan0: authenticate with AP 00:1c:10:9a:4e:de wlan0: RX authentication from 00:1c:10:9a:4e:de (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:1c:10:9a:4e:de wlan0: RX ReassocResp from 00:1c:10:9a:4e:de (capab=0x411 status=0 aid=2) wlan0: associated wlan0: RX deauthentication from 00:1c:10:9a:4e:de (reason=15) wlan0: deauthenticated wlan0: authenticate with AP 00:1c:10:9a:4e:de wlan0: RX authentication from 00:1c:10:9a:4e:de (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:1c:10:9a:4e:de wlan0: RX ReassocResp from 00:1c:10:9a:4e:de (capab=0x411 status=0 aid=2) wlan0: associated wlan0: no IPv6 routers present wlan0: RX deauthentication from 00:1c:10:9a:4e:de (reason=15) wlan0: deauthenticated wlan0: authenticate with AP 00:1c:10:9a:4e:de wlan0: RX authentication from 00:1c:10:9a:4e:de (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:1c:10:9a:4e:de wlan0: RX ReassocResp from 00:1c:10:9a:4e:de (capab=0x411 status=0 aid=2) wlan0: associated wlan0: disassociate(reason=3) wlan0: disassociate(reason=3) wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:1c:10:9a:4e:de wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:1c:10:9a:4e:de wlan0: RX authentication from 00:1c:10:9a:4e:de (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:1c:10:9a:4e:de wlan0: authentication frame received from 00:1c:10:9a:4e:de, but not in authenticate state - ignored wlan0: RX AssocResp from 00:1c:10:9a:4e:de (capab=0x411 status=0 aid=2) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready ACPI: Unable to turn cooling device [ffff81007fb329a0] 'on' ACPI: PCI interrupt for device 0000:02:06.0 disabled ACPI: Unable to turn cooling device [ffff81007fb329a0] 'on' ACPI: PCI Interrupt 0000:02:06.0[A] -> Link [APC3] -> GSI 18 (level, low) -> IRQ 18 phy1: Selected rate control algorithm 'pid' ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:1c:10:9a:4e:de wlan0: RX authentication from 00:1c:10:9a:4e:de (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:1c:10:9a:4e:de wlan0: RX AssocResp from 00:1c:10:9a:4e:de (capab=0x411 status=0 aid=2) wlan0: associated ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: no IPv6 routers present Version-Release number of selected component (if applicable): kernel-2.6.24.3-22.fc8 (problem appears to have started in -13, -12 crashes when loading the rt61pci module so could be there as well but undetected) How reproducible: 100% Steps to Reproduce: 1. yum install --enablerepo=updates-testing kernel 2. reboot 3. connect to network using networkmanager Actual results: loss of conenction after a little while Expected results: Glorious network connection Additional info:
Please try these kernels: http://koji.fedoraproject.org/koji/buildinfo?buildID=42735 Do these work for you? If so, please not it here: https://admin.fedoraproject.org/updates/F8/pending/kernel-2.6.24.3-34.fc8 Thanks!
Works so far, I haven't triggered this yet on -34 but it's only been running for about 30 mins. I'll reopen if it does this again.