All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Conrad Kostecki" <ck+ath10k@bl4ckb0x.de>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re[6]: Linux freezes after a time while running
Date: Fri, 18 Nov 2016 20:55:52 +0000	[thread overview]
Message-ID: <emd4599041-0b55-4d81-bfb1-4dde79408e41@valkyrie> (raw)
In-Reply-To: <CA+BoTQ=TMHfHJOAuystH_K-Uu7nP-t9BZhL6MpjHstU1QBe52g@mail.gmail.com>

Hi Michal,

Am 18.11.2016 15:47:42, "Michal Kazior" <michal.kazior@tieto.com> 
schrieb:

>Hmm.. looks like there's a stall in target-host communication for ~5
>seconds (89 suppressed warnings match 2 vifs beaconing at ~100ms
>interval).
>
>Did you try running without multi-BSS, i.e. just one AP vif? That's
>probably not going to help but it's worth ruling that out.
>
>

I've now run a test and as you said, it did not helped.

Cheers
Conrad


_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

      parent reply	other threads:[~2016-11-18 21:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 19:05 Linux freezes after a time while running Conrad Kostecki
2016-10-31 10:12 ` Michal Kazior
2016-10-31 16:48   ` Re[2]: " Conrad Kostecki
2016-11-02  3:31     ` Michal Kazior
2016-11-02  9:00       ` Conrad Kostecki
2016-11-02 15:27         ` Michal Kazior
2016-11-02 16:15           ` Conrad Kostecki
2016-11-02 17:24             ` Re[4]: " Conrad Kostecki
2016-11-07 13:38           ` Re[2]: " Conrad Kostecki
2016-11-07 16:43             ` Michal Kazior
2016-11-16 22:21               ` Re[4]: " Conrad Kostecki
2016-11-18 14:47                 ` Michal Kazior
2016-11-18 17:21                   ` Ben Greear
2016-11-18 20:55                   ` Conrad Kostecki [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=emd4599041-0b55-4d81-bfb1-4dde79408e41@valkyrie \
    --to=ck+ath10k@bl4ckb0x.de \
    --cc=ath10k@lists.infradead.org \
    --cc=michal.kazior@tieto.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.