From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "Berg, Johannes" <johannes.berg@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [Ilw] 3.10git: iwlwifi 0000:03:00.0: Request scan called when driver not ready.
Date: Mon, 24 Jun 2013 22:13:21 +0200 [thread overview]
Message-ID: <201306242213.21567.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB3019F3492@HASMSX103.ger.corp.intel.com>
On Monday 24 of June 2013, Grumbach, Emmanuel wrote:
> > Hi.
> >
> > [46804.179700] dmar: DRHD: handling fault status reg 3
> > [46804.179707] dmar: DMAR:[DMA Read] Request device [03:00.0] fault addr
> > ffed4000
>
> Fun. So you have an old device with a machine that has IOMMU. Ok...
>
> > DMAR:[fault reason 06] PTE Read access is not set
> > [46804.220818] iwlwifi 0000:03:00.0: Hardware error detected.
> > Restarting. [46804.220877] iwlwifi 0000:03:00.0: RF is used by WiMAX
>
> Did you really use WiMAX here?
No, that kernel doesn't even have wimax support compiled in.
# CONFIG_WIMAX is not set
( disabled wimax sometime ago in my kernel builds... maybe this is
coincidence)
>
> > [46807.828033] iwlwifi 0000:03:00.0: fail to flush all tx fifo queues Q 0
> > [46807.828039] iwlwifi 0000:03:00.0: Current SW read_ptr 138 write_ptr
> > 139
>
> Here, the HW is dead.
>
> > [46807.828230] iwl data: 00000000: a2 a5 a5 a5 a2 a5 a5 a5 a2 a5 a5 a5 a2
> > a5 a5 a5 ................
--
Arkadiusz Miśkiewicz, arekm / maven.pl
prev parent reply other threads:[~2013-06-24 20:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-23 18:21 3.10git: iwlwifi 0000:03:00.0: Request scan called when driver not ready Arkadiusz Miskiewicz
2013-06-24 19:56 ` [Ilw] " Grumbach, Emmanuel
2013-06-24 20:13 ` Arkadiusz Miskiewicz [this message]
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=201306242213.21567.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).