From: Fabian Wittenberg <Fabian.Wittenberg@sophos.com>
To: Adrian Chadd <adrian@freebsd.org>
Cc: Michal Kazior <michal.kazior@tieto.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: ath10k + INTEL_IDLE aka. cstates == firmware crash
Date: Thu, 19 Mar 2015 16:57:10 +0100 [thread overview]
Message-ID: <550AF1D6.80907@sophos.com> (raw)
In-Reply-To: <CAJ-VmonNygdZHU9+aUMh47_hjsRtrEqhH5wvgEWoQepPQh9DhQ@mail.gmail.com>
Yes, I guessed something like that but this should be a firmwarebug :-\
I'm quiet surprized that nowbody else has this problem!?
There are so many configuration constellations that trigger this...
Fabian
Am 19.03.2015 um 16:44 schrieb Adrian Chadd:
> It's possible that you're entering a sleep state, the whole socket +
> dram controller is going to sleep, and the latency that the wakeup
> causes is confusing the firmware and/or DMA engine.
>
>
>
> -adrian
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-03-19 15:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 13:08 ath10k + INTEL_IDLE aka. cstates == firmware crash Fabian Wittenberg
2015-02-23 13:32 ` Michal Kazior
2015-02-23 13:44 ` Fabian Wittenberg
2015-02-23 14:20 ` Michal Kazior
2015-02-23 14:41 ` Fabian Wittenberg
2015-03-02 12:20 ` Michal Kazior
2015-03-19 9:20 ` Fabian Wittenberg
2015-03-19 15:44 ` Adrian Chadd
2015-03-19 15:57 ` Fabian Wittenberg [this message]
2015-03-19 16:05 ` Adrian Chadd
2015-03-19 16:18 ` Fabian Wittenberg
2015-03-19 16:23 ` Adrian Chadd
2015-03-20 10:46 ` Fabian Wittenberg
2015-02-23 16:58 ` Ben Greear
2015-03-08 13:45 ` Jeremias Blendin
2015-03-08 18:27 ` Ben Greear
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=550AF1D6.80907@sophos.com \
--to=fabian.wittenberg@sophos.com \
--cc=adrian@freebsd.org \
--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