2008/9/15 Steven Noonan <steven@xxxxxxxxxxxxxx>: > > More recently, I had another incident where it disassociated and > refused to reassociate. I got about 100 of these in my dmesg (fixed by > unloading and reloading ath9k): > > [...] > [ 1279.031033] ath_set_channel: unable to reset channel 149 (5745Mhz) > flags 0x30142 hal status 4294967277 > [ 1279.031203] ath9k_config: Unable to set channel > [ 1279.323427] ath_set_channel: unable to reset channel 153 (5765Mhz) > flags 0x50142 hal status 4294967277 > [ 1279.323577] ath9k_config: Unable to set channel > [ 1279.624562] ath_set_channel: unable to reset channel 157 (5785Mhz) > flags 0x30142 hal status 4294967277 > [ 1279.624687] ath9k_config: Unable to set channel > [ 1279.916441] ath_set_channel: unable to reset channel 161 (5805Mhz) > flags 0x50142 hal status 4294967277 > [ 1279.916586] ath9k_config: Unable to set channel > [ 1280.207274] ath_set_channel: unable to reset channel 165 (5825Mhz) > flags 0x10142 hal status 4294967277 > [ 1280.207387] ath9k_config: Unable to set channel > [...] > I am experiencing this same issue from time to time, too. rmmod ath9k && modprobe ath9k fixes it. My card is AR5418 on a MacBook Pro. Regards, Davide Pesavento -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
