> > wlan1: RX disassociation from 00:50:18:3b:2b:04 (reason=1) > > wlan1: disassociated > > wlan1: deauthenticate(reason=14) > > "Message integrity field (MIC) failure" -- doesn't look good. > > I've seen a few reports of data corruption with ath5k. Maybe it is > clobbering its own frames too? I get exactly this symptom as well, but with the 5424 and the changes queued for 2.6.26. I had just assumed it was because the 5424 calibration etc. isn't fully understood yet. This appears to be a 5212 though, so perhaps fixing it here would fix it for both. -Bob -- 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
