Peter Stuge wrote: > I am on linux.git commit d8efd82eece89f8a5790b0febf17522affe9e1f1 > which contains commit f212781, current wireless-next/master HEAD. .. > Do you suspect that my problem (as described briefly in the email > subject and with more detail after the part of my email which you > quoted) is related to the device driver rather than higher-up parts > of the stack? .. > > You can also try latest fw(v0.33): > > http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/attachments/20130111/f8ebe4d3/attachment.bin > > Thanks! Will try this and get back to you. With the above firmware the problem described briefly in Subject and in more detail in my original email occurs much more easily, even as I am actively generating traffic over the interface. It happened twice while I was composing this very short email. //Peter -- 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