Red Hat Bugzilla – Bug 450401
hard freeze activating wlan rt2500 after kernel upgrade to 184.108.40.206-10.fc8
Last modified: 2008-08-26 11:37:38 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:220.127.116.11) Gecko/20080416 Fedora/18.104.22.168-1.fc8 Firefox/22.214.171.124
Description of problem:
Upgraded to new kernel (126.96.36.199-10) from 188.8.131.52-92 via PUP. Upon reboot, computer freezes when trying to activate wlan Linksys wireless 54gV4 PCI wlan card (RT2500 driver). Works fine under prior kernel. No messages in log, no kernel panic,just hard freeze when trying to activate card.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.boot kernel 184.108.40.206-10.fc8
2.try to activate wlan card eithe automatically in Network Manager, or manually
3.computer hard freezes
computer hard freezes, can only power down and reboot. works fine under prior kernel.
wlan card should have activated.
None. Nothing is written to log
This has been happening to me on older fc8 kernels too.
And it also happens on fc9 (220.127.116.11-30.fc9.i586).
My hardware is a PCMCIA rt2500 card (Edimax), which was usable with
the old ralink driver.
When I plug in the board, the driver is loaded and the system locks up
immediately or after a few seconds (memory corruption).
A stack trace of mine is available here:
Finger pointed to locking, interrupts, sleeping in the rt2500 driver.
I too get this with a Ralink RT2500 PCMCIA card with the latest Fedora 9 kernel
(to date). Can look up more info later if you wish. The previous Fedora 9
kernel works fine, but the latest one crashed a second after you plug the card in.
The kerneloops service has reported the incident. As I say, ask if you want
I have the same problem. In fact at boot up with the wlan card acitivated at
boot the system try to enable wlan0 for an infinte time. If i disable wlan0 at
boot and i try to activate wlan0 from grome i obtain a hard freeze.
Please try -39.fc9 or later:
Those contain this fix: "rt2x00: Use atomic interface iteration in irq
context". Do the later kernels resolve the issue for you?
I tried kernel-18.104.22.168-24.fc8 which is an updates-testing and contain this fix.
No more hard freeze but impossible to associate to the access point.
Yes, I can also verify that rt2500pci from kernel-22.214.171.124-24.fc8 does not
associate with the AP.
Created attachment 309399 [details]
excerpt of var/log/messages containing wlan activation attempts
Addendum to comment #7 (sorry for multiple posts). Tried kernel
126.96.36.199-55.fc9. Hard freeze now gone, but cannot associate with AP either.
Messages in above attachment. AP is WPA2-PSK. Original passphrase stored in
keychain, but after first attempt, NetworkManager prompts me to input, but
activation fails anyway, and I get prompted again (until I cancel).
Created attachment 309979 [details]
dmesg with kernel errors after inserting rt2500 card
I get kernel error messages but no hard freeze with the rt2500. With testing
kernel no errors but can't associate with AP. Another card with a differnt
chipset works fine.
*** Bug 452350 has been marked as a duplicate of this bug. ***
Association still times out with kernel-188.8.131.52-40.fc8
Kernel 184.108.40.206-27.fc8 fixed the hard freeze for me and works like expected, but
with kernel 220.127.116.11-40.fc8 I cannot associate using wpa_supplicant.
You might wisht to try -46.fc8:
Does that help with wpa_supplicant?
Created attachment 311195 [details]
log of failed association
still unable to associate with -46 kernel
For me too, still unable to associate with -46.fc8 kernel
Same story with both -47.fc8 and -48.fc8.
Same with kernel-18.104.22.168-54.fc8
This bug is opened since 5 weeks. It's quite a long time ...
Just tried 22.214.171.124-5.fc8 from Koji. Still doesn't work .. (i.e. authentication with AP times out).
Hmmm...well "AP times out" sounds different than "hard freeze". Perhaps the problem you are seeing now is the same as bug 451422?
John, problems of association and times out are part of this bug since a long time see for example comment 5.
Hi John, I suppose it might be same as bug 451422 but the end result is still the same. I've had to stick with a 2.6.24 series kernel for at least two months now ..
Please use bug 451422 for the association problems. I'm sorry I didn't notice the change back in June.
*** This bug has been marked as a duplicate of bug 451422 ***