On 22 July 2015 at 16:53, Martin Blumenstingl <[email protected]> wrote: > Hi Michal, > > On Wed, Jul 22, 2015 at 9:47 AM, Michal Kazior <[email protected]> > wrote: >> Note: It's better to post trace.dat. It contains more useful data - >> `trace-cmd report` doesn't decode, e.g. hexdumps unless you have extra >> plugins. > OK, noted. Do you still need trace.dat (I forgot to save that, but I > can obtain a new trace if required)?
No need for traces now, thanks ;-) We're back to guesswork. >> Anyway, I'm running out of ideas. You could make ath10k ignore SWBA >> events (i.e. not send beacon commands) and see what happens. > First of all: thanks for looking into this! > Can you be a bit more specific regarding ignoring SWBA events? Can I > simply make ath10k_wmi_event_host_swba a no-op? Yes, this should be enough. You'll want to add/keep a print to know how many SWBA event come in though. Perhaps not submitting beacons will prevent the crash or it'll postpone it until after more SWBA events are delivered than before. Michał _______________________________________________ ath10k mailing list [email protected] http://lists.infradead.org/mailman/listinfo/ath10k
