David Madore wrote: > On Wed, Mar 21, 2012 at 11:02:42PM +0100, David Madore wrote: > > Or, to summarize all of this: the dongle works if and only if > > ath9k_htc is initializing it for the very first time since it was > > physically plugged in or powered on. No reset, USB reset or software > > reset of any kind seems to help. > > More accurately: the dongle fails to work if and only if, since it was > last plugged in, there has been a reboot (=anything short of a full > power cycle) after it has been initialized by ath9k_htc. > > Unloading and reloading the kernel modules does not cause a failure > (but neither does it solve the problem). Rebooting[#] the machine > causes the problem if and only if ath9k_htc has been loaded prior to > reboot (even if there have been other intermediate reboots). Powering > the machine down, or unplugging the dongle, are the only way I've > found of restoring a sane state: no lesser kind of USB reset has > worked. > > [#] I should try kexec, but I haven't been able to get it to work. > > I'm willing to run any other experience which might elucidate things, > of course. Can you compile the driver/kernel with debugging enabled [1] ? Then, load the driver with the module parameter 'debug=0x8701' and post the kernel log here (a full run - load, use, reboot, load). Thanks. [1] http://linuxwireless.org/en/users/Drivers/ath9k/debug Sujith -- 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