Hi, > > This is all very strange behavior, I don't know what can cause the > > ACPI to disable an interrupt for the device, but what is interesting to > > see is that the BSSID in the register seems to have been cleared.... > I remember reading somewhere that ACPI can do that, if it detects > spurious interrupts coming from the device. Not sure if that's the only > situation where ACPI does this. Could you try editing rt2500pci.c and in rt2500pci_interrupt() change: if (rt2x00_get_field32(reg, CSR7_TBCN_EXPIRE)) rt2x00lib_beacondone(rt2x00dev); to //if (rt2x00_get_field32(reg, CSR7_TBCN_EXPIRE)) // rt2x00lib_beacondone(rt2x00dev); > > Could you create a debugfs dump of the time just before it breaks? > > Because it is very odd to see the BSSID to be suddenly cleared, currently > > is seems to occur with some people in managed mode as well and so > > far I haven't been able to trace it. > > Although now that it occurs in master mode as well it becomes > > more worrying since mac80211 doesn't control the BSSID in that case > > (rt2x00 just grabs the MAC address). So if this seems reproducable there > > might be some sort of hardware register reset occuring that messes > > things up badly.. :S > ok, here are some regdumps: > > 1) regdump_beforeifup: a regdump taken before the interface is brought > up (module is loaded of course) > 2) regdump_beforehostapd: a regdump taken immediately after the > interface is brought up, but before hostapd is running. > 3) regdump_beforeauth: a regdump taken after hostapd is started, and > running, but before a client has started an authentication. > 4) regdump_afterauthhang: a regdump, after hostapd has locked up, due to > an authentication attempt. Ivo -- 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
