Hi Mohammed,
so, I provoked the crash again on a newer build with debugging enabled
(LEDE r2321, Linux 4.4.32, ath10k firmware 10.2.4.70.54).
The relevant dmesg output is pasted below (with mac addresses
pseudo-anonymized). I hope this includes the information you were
looking for. If not, please
Hi Mohammed,
sorry for the late reply, but I was on a business trip last week.
The log I had attached is all I got from this crash. I have no experience
with kernel debugging, but I assume some info might be missing because the
kernel was not compiled with debug information. So, I will have to pr
Hi Timo,
sorry had I missed the exact kernel crash call trace ?
I could see only the warnings, can you please post the call
trace of the kernel crash please ?
regards,
shafi
On Sun, Nov 20, 2016 at 02:35:27AM +0100, Timo Sigurdsson wrote:
> Hi Adrian,
>
> sure - here's the bug report on kernel.
Hi Adrian,
sure - here's the bug report on kernel.org:
https://bugzilla.kernel.org/show_bug.cgi?id=188201
Regards,
Timo
Adrian Chadd schrieb am 18.11.2016 22:22:
> hiya!
>
> Can you file a kernel.org bug mentioning this?
>
> thanks!
>
>
> -a
>
>
> On 18 November 2016 at 01:30, Timo Sigu
hiya!
Can you file a kernel.org bug mentioning this?
thanks!
-a
On 18 November 2016 at 01:30, Timo Sigurdsson
wrote:
> Hi again,
>
> in the meantime, I have some more information to add to the issue mentioned in
> my email quoted further down below.
>
> Ben Greear approached me off-list and
Hi again,
in the meantime, I have some more information to add to the issue mentioned in
my email quoted further down below.
Ben Greear approached me off-list and suggested to try the Candela Tech ath10k
driver and firmware and see if the issue occurs with that as well. So, for the
last 3 weeks I
Unfortunately, there are no crashlogs. If there's anything else I can
do to help debug this, please let me know!
On 31 October 2016 at 09:11, Jo-Philipp Wich wrote:
> Hi Phil,
>
> if you enter failsafe after boot-loop, is there a
> /sys/kernel/debug/crashlog available and if-yes, can you post it
Hi,
this is reply to Jo's message [1] which was only sent to the mailing list, but
not to me directly. As I am not subscribed to the mailing list, please
excplicitly include me in future replies. Thank you.
Jo-Philipp Wich schrieb am 31.10.2016 01:37:
> Hi Timo,
>
> did you try with kmod-ath1
Just to report a possibly connected issue: snapshot LEDE builds for
the Archer C7 v1 (I tried Saturday and last Monday) go into bootloop
(though failsafe mode remains available, thankfully).
The C7 v1 5ghz / AC radio isn't supported by ath10k, according to the
OpenWrt wiki. Could ath10k also be ca
Hi Phil,
if you enter failsafe after boot-loop, is there a
/sys/kernel/debug/crashlog available and if-yes, can you post its
contents here?
~ Jo
signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.o
Hi Timo,
did you try with kmod-ath10k or kmod-ath10k-ct ?
Might be worth trying the -ct variant, to see if it has the same issue.
~ Jo
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev
Hi everybody,
I have a TP-Link Archer C7 v2 running a fairly recent build of LEDE (r1952,
Linux 4.4.26, compat-wireless-2016-10-08). It all works well except for the
fact that when I connect a Nexus 5X device to the 5GHz radio, the kernel or
ath10k driver will crash after a while. 5Ghz wifi will
12 matches
Mail list logo
