mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Larry Finger <Larry.Finger@lwfinger.net>
Subject: How to diagnose unexpected IRQ Trap
Date: Tue, 24 Feb 2009 10:00:49 -0600	[thread overview]
Message-ID: <49A419B1.1040507@lwfinger.net> (raw)
In-Reply-To: <banggh.3o3ten@no-mx.forums.opensuse.org>

In helping troubleshoot a wireless problem with an RTL8187L (USB) device on the
openSUSE forums, the following excerpt from the dmesg output was reported:

=================================================
unexpected IRQ trap at vector a3
irq 163, desc: c053af00, depth: 1, count: 0, unhandled: 0
->handle_irq():  c0166904, handle_bad_irq+0x0/0x1e8
->chip(): c051ae9c, no_irq_chip+0x0/0x40
->action(): 00000000
IRQ_DISABLED set
unexpected IRQ trap at vector a3
irq 163, desc: c053af00, depth: 1, count: 0, unhandled: 0
->handle_irq():  c0166904, handle_bad_irq+0x0/0x1e8
->chip(): c051ae9c, no_irq_chip+0x0/0x40
->action(): 00000000
IRQ_DISABLED set
==================================================

After seeing this info, I asked for the results of 'cat /proc/interrupts' and
got the following:

===================================================

bang@resolver:~> cat /proc/interrupts
CPU0       CPU1
0:         92          0   IO-APIC-edge      timer
1:         14          0   IO-APIC-edge      i8042
4:          1          0   IO-APIC-edge
6:          5          0   IO-APIC-edge      floppy
7:          0          0   IO-APIC-edge      parport0
8:          0          0   IO-APIC-edge      rtc0
9:          0          0   IO-APIC-fasteoi   acpi
14:          0          0   IO-APIC-edge      pata_via
15:       8655          0   IO-APIC-edge      pata_via
17:      69762          0   IO-APIC-fasteoi   HDA Intel, eth1
18:          0          0   IO-APIC-fasteoi   saa7134[0]
20:       8439          0   IO-APIC-fasteoi   uhci_hcd:usb1
21:      27348          0   IO-APIC-fasteoi   sata_via, uhci_hcd:usb3,
ehci_hcd:usb5
22:          9          0   IO-APIC-fasteoi   uhci_hcd:usb2
23:          0          0   IO-APIC-fasteoi   uhci_hcd:usb4
28:     247256          0   IO-APIC-fasteoi   ahci
29:          0          0   IO-APIC-fasteoi   pata_jmicron
163:   22423122          0      none-<NULL>
222:          0          0   PCI-MSI-edge      aerdrv
223:          0          0   PCI-MSI-edge      aerdrv
NMI:          0          0   Non-maskable interrupts
LOC:     221651     239972   Local timer interrupts
RES:      21767      19731   Rescheduling interrupts
CAL:        380        273   function call interrupts
TLB:       1435       2561   TLB shootdowns
TRM:          0          0   Thermal event interrupts
SPU:          0          0   Spurious interrupts
ERR:          0
MIS:          0
===========================================================

The kernel in question is reported as 2.6.27.7-9-pae. I don't know what the
hardware is.

What information should I get to help resolve this problem?

Thanks,

Larry




           reply	other threads:[~2009-02-24 16:01 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <banggh.3o3ten@no-mx.forums.opensuse.org>]

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=49A419B1.1040507@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®