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
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
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 ?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
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
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
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 ***
Toralf Förster wrote:
> 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):
> > > ...
> > > 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
> >
> > Is there any other info (like dmesg or boot log) that tells what
> > device/driver uses interrupt 47 ?
>
> I attached the dmesg output
> ahci 0000:00:1f.2: irq 44 for MSI/MSI-X
> e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
> iwlagn 0000:03:00.0: irq 46 for MSI/MSI-X
> HDA Intel 0000:00:1b.0: irq 47 for MSI/MSI-X
> i915 0000:00:02.0: irq 48 for MSI/MSI-X
These interrupt numbers do not match; I'd guess that you rebooted and
that the drivers were initialized in a different order.
Anyway, it looks as if the i915 driver is the culprit.
A quick look into the DRM code shows that it uses dev->devname as
interrupt name, but that field might get freed by drm_setversion().
(Or I might be wrong; I don't have this hardware.)
Regards,
Clemens