On Sunday 08 March 2009, Anders Eriksson wrote: > So, > Now it has happened again. :-( > > I can conclude that a rmmod/modprobe cycle does not help. > Well I can see from those logs that it is only the transmit side that is failing, some traffic is being seen on the receive side. Does your hardware have an rfkill button and do you have rfkill support enabled? I'm wondering if rfkill could be activated by a glitch on the signal. Other than that this is going to be tricky to do anything with. The fact that rmmod doesn't help suggests that there is a reasonable possibility of this being a hardware issue that the software can't fix (assuming this is a rt2500 issue, not something deeper in the stack). You can't do any very intrusive monitoring as the system needs to be left too long before it fails, except possibly by rmmodding the original driver when it fails and insmodding a new one that contains lots of printk statements in the tx path to see which het triggered. If trying that approach don't forget to instrument rt2500pci_interrupt as well as rt2x00mac_tx Adam -- 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
