From: Gabriele Martino <g.martino@gmx.com>
To: ath10k@lists.infradead.org
Subject: Re: ath10k: freeze after disconnection on killer1525
Date: Mon, 11 May 2015 20:10:06 +0200 [thread overview]
Message-ID: <5550F07E.7010701@gmx.com> (raw)
In-Reply-To: <CA+BoTQk0Lca7mUfELjeHSbY_fiExTopga9J74khnOPkzEU01Xg@mail.gmail.com>
On 11/05/2015 15:30, Michal Kazior wrote:
> On 11 May 2015 at 14:50, Gabriele Martino <g.martino@gmx.com> wrote:
>> Hi,
>> I'm using a Killer 1525 with hw2.1 firmware, and sometimes it stop working.
>> I can get it working again disconnecting and reconnecting, but sometimes
>> on disconnection it freezes for a long time:
>>
>> [ 2740.035190] dmar: DRHD: handling fault status reg 2
>> [ 2740.035195] dmar: DMAR:[DMA Read] Request device [03:00.0] fault addr
>> ffbeb000
>> DMAR:[fault reason 06] PTE Read access is not
>> set
> This looks like DMA tx pool memory address. I suspect
> firmware/hardware tried to access memory which was already unmapped by
> ath10k.
>
> If you're feeling lucky you could disable IOMMU - this should prevent
> from crashing and disconnecting. However this is hardly a solution
> unless you're okay with the device reading random memory and doing
> *stuff* with it (plaintext password from RAM sent on the air, anyone?
> :-)
This seems even worse than the problem itself :-)
Other ideas? Should I provide other logs?
Regards,
Gabriele
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-05-11 18:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 12:50 ath10k: freeze after disconnection on killer1525 Gabriele Martino
2015-05-11 13:30 ` Michal Kazior
2015-05-11 18:10 ` Gabriele Martino [this message]
2015-05-11 21:17 ` Ben Greear
2015-05-12 4:52 ` Michal Kazior
2015-05-12 19:37 ` 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=5550F07E.7010701@gmx.com \
--to=g.martino@gmx.com \
--cc=ath10k@lists.infradead.org \
/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.