Hm, ok. Well, file a PR and then try updating to -HEAD. Maybe my latest fix is good enough to fix it.
ADrian On 16 April 2013 13:19, <[email protected]> wrote: > Yea, stuck beacons are often seen in dmesg > ------Original Message------ > From: Adrian Chadd > Sender: [email protected] > To: Mike > Cc: [email protected] > Subject: Re: AR9380 in hostAP mode. The success story > Sent: Apr 16, 2013 23:13 > > Hiya, > > This is an interesting one: > > panic: lost 1 frames > > .. that's inside the HT A-MPDU receive reorder path. Which is odd, the > receive path shouldn't have that issue. > > Are you seeing stuck beacons or resets or something at the same time? > I wonder if this is occuring because there's a reset (from a stuck > beacon) occuring at the same time the RX path is running, and this is > causing the RX A-MPDU receive reorder path to get confused. > > The reset path _should_ be waiting for the RX path to complete before > it does a reset. Hm. > > > > Adrian > > > > On 15 April 2013 03:34, Mike <[email protected]> wrote: >> Finally I was able to get a core dump on a reboot-after-auth issue with ath. >> Here is core.txt: http://storage.v12.su/core.txt.2 >> >> -- >> With best regards from Russia, Mike >> _______________________________________________ >> [email protected] mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "[email protected]" > > > Sent from my BlackBerry® smartphone from MTS _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "[email protected]"
