Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Robert  Smith <robert.smith@dataflex.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] PCI FATAL issue
Date: Fri, 6 Jun 2014 14:38:51 +0100	[thread overview]
Message-ID: <001801cf818c$a77b6480$f6722d80$@dataflex.com> (raw)

Hi,

 

We are using a DNXA116 based on the HB116 with the Atheros AR9382 chip. We
are developing on a OpenWRT (Barrier Breaker) platform using kernel version
3.10.28  and compat-wireless-2013-11-05 using the ath9k driver for this PCIe
device. 

 

Everytime we start the device (when it is trying to bring it into service as
an AP) we get a 'received PCI FATAL interrupt' (corresponding to
AR_INTR_SYNC_HOST1_FATAL) then 'FATAL: skipping interrupts' (corresponding
to ATH9K_INT_FATAL) and hence the device doesn't startup.

We've tried with multiple PCIe cards and multiple base cards to try and rule
out a dodgy card somewhere and get this with all.

Does anyone know why this happens or why we may be seeing this ?  Or has
anyone got any suggestions about how to find out more about this problem
we're seeing ?

 

Thanks in advance

Rob Smith




Dataflex Limited - 8 Frederick Sanger Road - Surrey Research Park - Guildford - Surrey - GU2 7YD +44 1483685200


Dataflex Limited - 8 Frederick Sanger Road - Surrey Research Park - Guildford - Surrey - GU2 7YD +44 1483685200
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20140606/6de039e2/attachment.htm 

                 reply	other threads:[~2014-06-06 13:38 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='001801cf818c$a77b6480$f6722d80$@dataflex.com' \
    --to=robert.smith@dataflex.com \
    --cc=ath9k-devel@lists.ath9k.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