From: Conrad Kostecki <ck+ath10k@bl4ckb0x.de>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: ath10k@lists.infradead.org
Subject: Re: Re[2]: Linux freezes after a time while running
Date: Wed, 2 Nov 2016 10:00:19 +0100 (CET) [thread overview]
Message-ID: <1233772075.6396.1478077219620@office.mailbox.org> (raw)
In-Reply-To: <CA+BoTQkyd2f78Pk=_FrYyuQXedn8t6EEYq6BWHB8zthOF_AZ6w@mail.gmail.com>
Hi!
> Michal Kazior <michal.kazior@tieto.com> hat am 2. November 2016 um 04:31 geschrieben:
> I suspect the pcie link gets broken one direction because attempting a
> cold reset did crash the host even harder.
What I can see, the WiFi runs stable, if nobody connects to it. The failure starts, when somebody connects and does some throughput.
> Looks like the device went into a very confused state due to pcie link
> failure starting from:
Well, I did a test and removed the Mikrotik RB14e, as it has a PLX chip and provides an extra pcie switch. Instead, I took a simple passive miniPCIe->PCIe adapter and build only one card into it. The problem still exists. So, the RB14e is not the cause at least.
> [ 691.609836] pcieport 0000:00:02.0: AER: Multiple Uncorrected
> (Non-Fatal) error received: id=0800
I see, so the firmware crash it not the cause, but the error reported by AER. Thanks for clarify!
> I'm not really familiar with these. Perhaps there's a pcie bridge
> problem on your host platform or maybe an electrical issue (e.g.
> insufficient power supply to handle short bursts?).
Well, the mainboard is microATX. So its powered by a Seasonic 400W passive PSU, but the whole system takes about 40-50w. So the PSU itself should be enough? ;-) IIRC PCIe should provide up to 75W?
I am out of ideas.. I know, a year ago, that cards were perfectly working. Even a test replacement shows the same errors, so it's not a defective card.
Cheers
Conrad
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-11-02 9:00 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 [this message]
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=1233772075.6396.1478077219620@office.mailbox.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox