On 16.07.2012 16:47, Mark Haney wrote: > This one might be a lot harder. I installed (fresh) F17 on my new > 6-core Phenom II system. I normally will keep that server on and > accessible via ssh from the internet so I can monitor logs on Squid, > do bandwidth tests on my customers servers, etc. > > I let the server sit running over Thursday, Friday and Saturday > morning last week, came in to do some work on it Sat evening and the > wireless NIC would NOT come up. It's set to connect automatically and > system connection in Network Manager. Even restarting the Network > service failed to bring it up. So, after some digging I noticed this > in dmesg: > > [25013.930030] phy0 -> rt2500pci_set_device_state: Error - Device > failed to enter state 1 (-16). > [25013.930036] phy0 -> rt2500pci_set_device_state: Error - Device > failed to enter state 1 (-16). > [25016.435030] ieee80211 phy0: wlan0: No probe response from AP > 0c:d5:02:7e:98:1f after 500ms, disconnecting. > [25016.441120] cfg80211: Calling CRDA to update world regulatory domain > [25016.447192] cfg80211: World regulatory domain updated: > [25016.447196] cfg80211: (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp) > [25016.447199] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), > (300 mBi, 2000 mBm) > > [25016.447230] cfg80211: Calling CRDA for country: US > [25016.450200] cfg80211: Regulatory domain changed to country: US > [25016.450203] cfg80211: (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp) > [25016.450205] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), > [25017.234399] wlan0: authenticate with 0c:d5:02:7e:98:1f > [25017.239521] wlan0: send auth to 0c:d5:02:7e:98:1f (try 1/3) > [25017.440026] wlan0: send auth to 0c:d5:02:7e:98:1f (try 2/3) > [25017.641026] wlan0: send auth to 0c:d5:02:7e:98:1f (try 3/3) > [25017.842021] wlan0: authentication with 0c:d5:02:7e:98:1f timed out > [25030.128035] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping > frame due to full tx queue 0. > [25035.811027] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping > frame due to full tx queue 0. > [25041.499026] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping > frame due to full tx queue 0. > [25047.184028] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping > frame due to full tx queue 0. > > I've never seen this error before on any of my systems. I run F17 on > my netbook and have let it sit for days running without this problem. > > Couple of things to note, I live way out in the boonies, so there is > no security on the wireless router I connect to. I've rebooted the > router just to make sure it wasn't the problem. The card came up > after a reboot, but this is bothersome if I can't rely on the link to > be up all the time. > > I'll be glad to offer any more information that may be necessary. > > Any ideas? > What about this: https://bugzilla.redhat.com/show_bug.cgi?id=753648 ? Mateusz Marzantowicz -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
