linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "voncken" <cedric.voncken@acksys.fr>
To: "'Michal Kazior'" <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>,
	"'linux-wireless'" <linux-wireless@vger.kernel.org>
Subject: RE: ath10k firmware crash
Date: Mon, 13 Oct 2014 11:20:07 +0200	[thread overview]
Message-ID: <024901cfe6c6$e1905780$a4b10680$@acksys.fr> (raw)
In-Reply-To: <CA+BoTQkXc-VL1ixRK5KWUiE0igCxXRQyyde86TAvuKVxZhEPdg@mail.gmail.com>



> -----Message d'origine-----
> De : Michal Kazior [mailto:michal.kazior@tieto.com]
> Envoyé : lundi 13 octobre 2014 09:54
> À : voncken
> Cc : ath10k@lists.infradead.org; linux-wireless
> Objet : Re: ath10k firmware crash
> 
> On 13 October 2014 09:35, voncken <cedric.voncken@acksys.fr> wrote:
> >         Thanks for your reply,
> >
> >>
> >> Can you then provide a crash register dump for 10.1, please? I can't
> >> help you much with the 636 dump.
> >>
> > Yes I can, but where I find it?
> 
> https://github.com/kvalo/ath10k-firmware/blob/master/10.1/firmware-
> 2.bin_10.1.467.2-1
> 
> 
> >> Are you perhaps trying to run STA with 4addr bridging? If so then
> >> make sure you use recent ath10k as this was known to be a problem.
> >>
> > Yes I'm testing with 4 addr bridging because I need to bridge this
> interface. I' ll try without this option.
> > I'm testing with commit number 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0
> from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware. It is the
> latest version in openwrt.
> >
> >> Can you also provide ath10k traces or debug logs, please?
> >>
> > I'll send a trace.
> 
I'm using the compat wireless from Openwrt.
	Compat wireless version 2014-05-22, but we updated the firmware with the latest version provided by openwrt (commit number 38eeda3ae6f90fde5546bdd48ee4ff3090f238c0 from kernel.org/pub/scm/linux/kernel/git/firmare/linux-firmware)

> Thanks.
> 
> By the way, what kernel/compat-wireless are you using? I'm suspecting your
> build might be missing the fix for STA bridging.
Thanks.

> 
> 
> Michał


  reply	other threads:[~2014-10-13  9:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-10 14:46 ath10k firmware crash Cedric VONCKEN
2014-10-13  5:46 ` Michal Kazior
2014-10-13  7:35   ` voncken
2014-10-13  7:54     ` Michal Kazior
2014-10-13  9:20       ` voncken [this message]
2014-10-13  9:25         ` Michal Kazior
2014-10-13 12:00           ` voncken
2014-10-13 14:06           ` voncken
2014-10-13  9:23   ` voncken
2014-10-13  9:30     ` Michal Kazior
2014-10-13 12:06       ` voncken
2014-10-15 12:13         ` Bartosz Markowski
2014-10-15 13:05           ` voncken

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='024901cfe6c6$e1905780$a4b10680$@acksys.fr' \
    --to=cedric.voncken@acksys.fr \
    --cc=ath10k@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).