>> Does also your board support 802.11abg? I don't understand why the noise >> calibration process remains stuck @ 5.18GHz. >> 5.18 is the first channel on 5GHz band and 5GHz band is the band we start with, so it's the first channel the driver sets. > My initial thought was that one of the cpus was stuck, running the > calibration function again and again which would result what you > describe. Well that's of course extreme, but i can't explain why you can't unload the module or why you get higher cpu utilization. I mean it seems only the calibration function gets called (if reset function got called then we would have more than 6 nf timeout failures since reset also performs a nf calibration) and nothing else works. It could be an interrupt storm but i don't understand why this patch triggers it. -- GPG ID: 0xD21DB2DB As you read this post global entropy rises. Have Fun ;-) Nick -- 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
