Hi, Am Montag 27 September 2010 schrieb Joshua Smith: > The change to the REGISTER_BUSY_COUNT did not eliminate the issue. > The device still sometimes exhibits this behavior. (It may be exhibiting > it less often, but the occurrences are so random, that it's hard for me to > know for sure.) Yeah, as I said, just a shot in the dark. > However, the other fix DID indeed eliminate the kernel crash when I tried > to restart hostapd, and it also fixed a crash that I experienced when I > tried to rmmod the rt2800pci module. So you should definitely mainline > that patch. Sure. > Now that I can retry hostapd and rmmod the modules, I have found that there > is apparently no software workaround for the case where the DMA busy > condition does not pass. Hmm, maybe there is but we have't found it yet ;) > I have tried restarting hostapd, and I have tried rmmod'ding all the > associated modules and modprobing them back in. Nothing clears the > condition except a reboot. Too bad. > Any other ideas of what I could do to reset the hardware? I'd love to find > a "soft" fix for this, rather than having to reboot to clear the condition. Nothing obviouis at least. So, no without further debugging I don't know what's going on in your case. Would be interesting if others experience the same problem. Helmut -- 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
