2008/9/23 Steven Noonan <steven@xxxxxxxxxxxxxx>: > Okay. I'm in Seattle now. > > Yes, it solved the issue, but surely an #if 0 isn't a proper solution. For 2.6.27 it will be unless people are willing to accept a patch to enable ANI support for 2.6.27. > What's the actual bug here? I'm afraid the meaning of what's going on > here isn't exactly intuitive. Check linux-wireless for my patch on MIB event comments. But I'll summarize here for you. We get MIB interrupts to update statistics on a number of PHY related elements. We then use this information to process ANI -- some automatic noise immunity work. If you don't process the information for ANI it seems you get the hardware treating this as untreated and hence you get an interrupt storm. So since 2.6.27 doesn't have ANI implemented the MIB interrupts are not useful except to collect internal statistics. Since you are so eager to test this with a "proper" solution I will send you a patch to test ANI for 2.6.27. We'll leave it up to the maintainers and distributions to decide whether or not to pick this up. But for that let's leave that for another thread. Luis -- 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
