From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: non-printable characters in /proc/interrupts
Date: Fri, 10 Jun 2011 16:05:41 -0700 [thread overview]
Message-ID: <20110610160541.21688a35.randy.dunlap@oracle.com> (raw)
In-Reply-To: <201106110038.43139.toralf.foerster@gmx.de>
On Sat, 11 Jun 2011 00:38:42 +0200 Toralf Förster wrote:
[adding Thomas]
> Randy Dunlap wrote at 18:11:32
> > On Fri, 10 Jun 2011 10:40:19 +0200 Toralf Förster wrote:
> > > I've wondering about this entry at my ThinkPad T400 (kernel 2.6.39.1):
> > >
> > > n22 ~ # grep 47: /proc/interrupts
> > >
> > > 47: 44041 69740 PCI-MSI-edge l▒��@�E�
> > >
> > > I attached the output of
> > > $>grep 47: /proc/interrupts > /tmp/int47
> > > onto this email, the complete table looks like this :
> > >
> > > n22 ~ # cat /proc/interrupts
> > >
> > > CPU0 CPU1
> > >
> > > 0: 605293 71393 IO-APIC-edge timer
> > > 1: 13432 4 IO-APIC-edge i8042
> > > 8: 55 64 IO-APIC-edge rtc0
> > > 9: 6248 509 IO-APIC-fasteoi acpi
> > >
> > > 12: 1389 72 IO-APIC-edge i8042
> > > 16: 0 0 IO-APIC-fasteoi uhci_hcd:usb6
> > > 17: 0 0 IO-APIC-fasteoi uhci_hcd:usb7
> > > 18: 0 0 IO-APIC-fasteoi uhci_hcd:usb8
> > > 19: 0 0 IO-APIC-fasteoi ehci_hcd:usb2
> > > 20: 52881 0 IO-APIC-fasteoi uhci_hcd:usb3
> > > 21: 329 37 IO-APIC-fasteoi uhci_hcd:usb4
> > > 22: 0 0 IO-APIC-fasteoi uhci_hcd:usb5
> > > 23: 30046 8743 IO-APIC-fasteoi ehci_hcd:usb1
> > > 40: 0 0 PCI-MSI-edge PCIe PME
> > > 41: 0 0 PCI-MSI-edge PCIe PME
> > > 42: 0 0 PCI-MSI-edge PCIe PME
> > > 43: 0 0 PCI-MSI-edge PCIe PME
> > > 44: 484163 55698 PCI-MSI-edge ahci
> > > 45: 750 1809 PCI-MSI-edge eth0
> > > 46: 94 213 PCI-MSI-edge hda_intel
> > > 47: 44399 70713 PCI-MSI-edge l▒��@�E�
> > > 48: 71969 102457 PCI-MSI-edge iwlagn
> > >
> > > NMI: 0 0 Non-maskable interrupts
> > > LOC: 10167789 10321319 Local timer interrupts
> > > SPU: 0 0 Spurious interrupts
> > > PMI: 0 0 Performance monitoring interrupts
> > > IWI: 213 200 IRQ work interrupts
> > > RES: 289390 333102 Rescheduling interrupts
> > > CAL: 4677 4542 Function call interrupts
> > > TLB: 22261 16007 TLB shootdowns
> > > TRM: 0 0 Thermal event interrupts
> > > THR: 0 0 Threshold APIC interrupts
> > > MCE: 0 0 Machine check exceptions
> > > MCP: 41 41 Machine check polls
> > > ERR: 0
> > > MIS: 0
> >
> > Is there any other info (like dmesg or boot log) that tells what
> > device/driver uses interrupt 47 ?
>
> 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio
> Controller (rev 03)
> Subsystem: Lenovo Device 20f2
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0, Cache Line Size: 64 bytes
> Interrupt: pin B routed to IRQ 47
> Region 0: Memory at fc020000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: <access denied>
> Kernel driver in use: HDA Intel
> Kernel modules: snd-hda-intel
>
> I attached the dmesg output
>
> --
So for you lspci, IRQ 47 is HD Audio,
but in the dmesg.txt file, we can see:
iwlagn 0000:03:00.0: irq 46 for MSI/MSI-X // iwlagn uses irq 48 above
HDA Intel 0000:00:1b.0: irq 47 for MSI/MSI-X // HDA Intel uses irq 46 above
i915 0000:00:02.0: irq 48 for MSI/MSI-X // i915 uses what irq above? maybe 47?
Hopefully Thomas can see something here.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-06-10 23:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 8:40 Toralf Förster
2011-06-10 16:11 ` Randy Dunlap
2011-06-10 22:38 ` Toralf Förster
2011-06-10 23:05 ` Randy Dunlap [this message]
2011-06-17 13:35 ` Clemens Ladisch
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=20110610160541.21688a35.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=toralf.foerster@gmx.de \
/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®