From: "voncken" <cedric.voncken@acksys.fr>
To: 'Michal Kazior' <michal.kazior@tieto.com>
Cc: 'linux-wireless' <linux-wireless@vger.kernel.org>,
ath10k@lists.infradead.org
Subject: RE: ath10k firmware crash
Date: Mon, 13 Oct 2014 09:35:05 +0200 [thread overview]
Message-ID: <023801cfe6b8$350c1930$9f244b90$@acksys.fr> (raw)
In-Reply-To: <CA+BoTQ=a8kY0CGGKHwRhk4cg=V0oimipuht6Pkc0K0x4WMMn-A@mail.gmail.com>
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?
> 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.
>
> > Is it possible to use at the same time on 2 different cards the AP
> mode and client mode?
>
> Yes, it is possible.
>
>
> Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-10-13 8:36 UTC|newest]
Thread overview: 15+ 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 [this message]
2014-10-13 7:54 ` Michal Kazior
2014-10-13 9:20 ` voncken
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
-- strict thread matches above, loose matches on Subject: below --
2025-01-02 20:19 Ath10k " Jamie
2025-01-09 13:08 ` Kalle Valo
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='023801cfe6b8$350c1930$9f244b90$@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