On Fri, Mar 23, 2018 at 12:26 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Fri, 2018-03-23 at 11:02 -0400, Tyler Gray wrote: >> You mentioned the firmware can suppress beacons for powersaving. Is >> there any debug I could look at to see if that was happening? I >> posted some fw_rx_stats, would those counters be incremented before >> that filtering would happen? I just watched the counters during a >> good period and a bad period. In the "good" period I saw 15 CCK >> packets/second, which is what I'd expect for my AP beaconing plus some >> some probe responses and some beacons from the adjacent channel. >> During the bad period the firmware saw 2 CCK packets in 7 seconds, and >> none of the error counters for the bad period showed an additional 100 >> packets lost for any reason. The two periods had fairly similar >> plcp_err stats. > > I'd have to check. It'd be great to know, or any other kind of debugging you'd suggest to pin it down to the packet isn't received at all, it isn't making it out of firmware, or it isn't making it out of the driver. We did set the debug level to 0xffffffff and that seems to generate 3-4 syslog entries per packet received, and I again see no activity when the beacons aren't showing up, so I'm pretty sure we're getting lost before the driver level. > ISTR being told that 8260 devices would make much better sniffers - any > chances you have one of those to try? The 7265 seems to be really popular in that 12x16mm soldered down package, so we're kind of tied to it because it's in hardware we want to use and there's no easy way to replace it. > Perhaps you could file a bug on bugzilla.kernel.org so we can track this > better. Thanks, I'll submit something next week.
