All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mihai Moldovan <ionic@ionic.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] received PCI FATAL interrupt
Date: Tue, 07 Apr 2009 21:44:31 +0200	[thread overview]
Message-ID: <49DBAD1F.1030709@ionic.de> (raw)
In-Reply-To: <1239131099.8746.439.camel@arrakis>

* On 07.04.2009 21:04, Jason Tackaberry wrote:
> Hi,
>
> On Tue, 2009-04-07 at 20:53 +0200, Mihai Moldovan wrote:
>   
>> today I have updated to Kernel 2.6.29.1 using compat-wireless
>> (yesterday's snapshot) and got those messages in my kernel log ring buffer:
>>
>> [   72.952758] ath9k: received PCI FATAL interrupt
>>     
>
> What is the contents of /proc/interrupts
Hi Jason,

actually looks fine. Relevant lines:

 19:      76501      63856      52512      64969   IO-APIC-fasteoi
uhci_hcd:usb7, ath
 21:     128257     122019     114385     128061   IO-APIC-fasteoi
uhci_hcd:usb4, ath

ath and USB should not interfere, but well...

Anyways, full content:

           CPU0       CPU1       CPU2       CPU3
  0:         46          2          2          6   IO-APIC-edge      timer
  1:          2          0          0          0   IO-APIC-edge      i8042
  4:          0          0          1          0   IO-APIC-edge
  8:       1695       1538       1484       1464   IO-APIC-edge      rtc0
  9:          0          0          0          0   IO-APIC-fasteoi   acpi
 12:          1          0          3          0   IO-APIC-edge      i8042
 16:          0          0          0          0   IO-APIC-fasteoi
uhci_hcd:usb3
 17:          0          0          0          1   IO-APIC-fasteoi
 18:          0          0          0          0   IO-APIC-fasteoi
ehci_hcd:usb1, uhci_hcd:usb5, uhci_hcd:usb8
 19:      76501      63856      52512      64969   IO-APIC-fasteoi
uhci_hcd:usb7, ath
 21:     128257     122019     114385     128061   IO-APIC-fasteoi
uhci_hcd:usb4, ath
 23:         46         36         37         36   IO-APIC-fasteoi
ehci_hcd:usb2, uhci_hcd:usb6
 24:      53885          0          0          0  HPET_MSI-edge      hpet2
 25:          0      40218          0          0  HPET_MSI-edge      hpet3
 26:          0          0      88740          0  HPET_MSI-edge      hpet4
 27:          0          0          0      82489  HPET_MSI-edge      hpet5
 32:       3515       3470       3165       2764   PCI-MSI-edge      ahci
 33:      44801      40299      38433      41709   PCI-MSI-edge      eth1
 34:      41813      45560      40506      37979   PCI-MSI-edge      eth0
NMI:          0          0          0          0   Non-maskable interrupts
LOC:         95         79         52         25   Local timer interrupts
RES:       5880       7402       5444       6837   Rescheduling interrupts
CAL:         49         73         72         58   Function call interrupts
TLB:        319        568        308        573   TLB shootdowns
TRM:          0          0          0          0   Thermal event interrupts
THR:          0          0          0          0   Threshold APIC interrupts
SPU:          0          0          0          0   Spurious interrupts
ERR:          0
MIS:          0

Best regards,


Mihai


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 898 bytes
Desc: OpenPGP digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20090407/ac733e81/attachment.pgp 

  reply	other threads:[~2009-04-07 19:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-07 18:53 [ath9k-devel] received PCI FATAL interrupt Mihai Moldovan
2009-04-07 19:04 ` Jason Tackaberry
2009-04-07 19:44   ` Mihai Moldovan [this message]
2009-05-15  0:57     ` Mihai Moldovan
2009-05-15  1:47       ` Luis R. Rodriguez

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=49DBAD1F.1030709@ionic.de \
    --to=ionic@ionic.de \
    --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 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.