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[2]: Linux freezes after a time while running
Date: Mon, 31 Oct 2016 16:48:49 +0000	[thread overview]
Message-ID: <ema51f2924-a0bb-4f7a-8d84-3ee6fb82e317@valkyrie> (raw)
In-Reply-To: <CA+BoTQmbz1vHjn0Xbo2hKcb9v8MdN5uTEnVNOAK0Kfh_NwTp5w@mail.gmail.com>

Hello Michał,

Am 31.10.2016 11:12:03, "Michal Kazior" <michal.kazior@tieto.com> 
schrieb:

>  You could try loading ath10k_pci with reset_mode=1 parameter.
>
>Cold reset is known to cause some problems after firmware certain
>crashes and I've personally experienced system freezes on x86 (MIPS
>tends to spit "data bus error" and doesn't lock up).
thank you very much for your answer. I've now set reset_mode=1,
which seems to be now active, as I can see in dmesg:
[    8.471659] ath10k_pci 0000:08:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 1
[    8.587267] ath10k_pci 0000:09:00.0: pci irq msi oper_irq_mode 2 
irq_mode 0 reset_mode 1

After starting HostAPd, I powered up my Squeezebox Radio to connect via 
WiFi.
Just after a few minutes, it crashed, as expected, but it did not 
restart the whole server.
It this due reset_mode=1? I was now able to capture a lot of information 
from dmesg.
You can clearly see, that the firmware crashed. The HostAPd process is 
still running,
but the WiFi can be detected anymore.

As it's very much, I've put this on pastebin: 
http://pastebin.com/83WZktp6

You can see at mark 250, WiFi1 (2.4GHz) comes up and at mark 356 WIFI2 
(5GHz) comes up.
By mark 691, ath10k_pci crashed and WiFi stopped working. Normally, at 
this point the whole server would reboot.

I've also now tried the newest firmware 10.2.4.70.58 which no luck.

Any Ideas?

Cheers and Thanks
Conrad


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

  reply	other threads:[~2016-10-31 16:49 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   ` Conrad Kostecki [this message]
2016-11-02  3:31     ` Re[2]: " 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                   ` Re[6]: " Conrad Kostecki

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=ema51f2924-a0bb-4f7a-8d84-3ee6fb82e317@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.