2009-04-17 15:00:37

by Alessandro Bono

[permalink] [raw]
Subject: 2.6.29.1 sdhci: irq 19: nobody cared

Hi

This is a bug that occur from time to time on my (unsed) sdhci card
drive
this is with kernel 2.6.29.1 (not a regression, I had the same problem
with older kernel)

[ 2885.888003] irq 19: nobody cared (try booting with the "irqpoll"
option)
[ 2885.888014] Pid: 0, comm: swapper Not tainted 2.6.29.1 #1
[ 2885.888019] Call Trace:
[ 2885.888023] <IRQ> [<ffffffff802751cb>] __report_bad_irq+0x38/0x87
[ 2885.888045] [<ffffffff80275332>] note_interrupt+0x118/0x182
[ 2885.888053] [<ffffffff80275962>] handle_fasteoi_irq+0xa1/0xc5
[ 2885.888062] [<ffffffff8020de49>] do_IRQ+0x70/0xe7
[ 2885.888069] [<ffffffff8020bf53>] ret_from_intr+0x0/0xa
[ 2885.888073] <EOI> [<ffffffff8024f317>] ? notifier_call_chain
+0x33/0x5b
[ 2885.888136] [<ffffffffa002b7bb>] ? acpi_idle_enter_simple
+0x186/0x1f8 [processor]
[ 2885.888159] [<ffffffffa002b7b1>] ? acpi_idle_enter_simple
+0x17c/0x1f8 [processor]
[ 2885.888169] [<ffffffff80399fa6>] ? cpuidle_idle_call+0x8c/0xc6
[ 2885.888176] [<ffffffff8020a649>] ? cpu_idle+0x52/0x93
[ 2885.888184] [<ffffffff804133cd>] ? rest_init+0x61/0x63
[ 2885.888189] handlers:
[ 2885.888192] [<ffffffffa02b2b86>] (sdhci_irq+0x0/0x49a [sdhci])
[ 2885.888208] Disabling IRQ #19


as you can see there is a lot of interrupts on mmc0 but seems strange
because I don't use this drive at all


cat /proc/interrupts
CPU0 CPU1
0: 320163 361871 IO-APIC-edge timer
1: 997 1017 IO-APIC-edge i8042
7: 0 0 IO-APIC-edge parport0
9: 3427 205 IO-APIC-fasteoi acpi
12: 920 876 IO-APIC-edge i8042
14: 43038 224 IO-APIC-edge ata_piix
15: 0 0 IO-APIC-edge ata_piix
16: 34787 50 IO-APIC-fasteoi uhci_hcd:usb2, yenta
17: 742 735 IO-APIC-fasteoi uhci_hcd:usb4, yenta, HDA
Intel, HDA Intel
18: 2 2 IO-APIC-fasteoi ohci1394, ehci_hcd:usb1,
uhci_hcd:usb7
19: 5399854 147 IO-APIC-fasteoi
mmc0
20: 12 12 IO-APIC-fasteoi ehci_hcd:usb3,
uhci_hcd:usb5
22: 0 0 IO-APIC-fasteoi
uhci_hcd:usb6
28: 57246 12 PCI-MSI-edge
eth0
29: 26003 21615 PCI-MSI-edge
ahci
30: 922 722 PCI-MSI-edge
iwlagn
NMI: 0 0 Non-maskable
interrupts
LOC: 235843 241312 Local timer
interrupts
RES: 58369 76238 Rescheduling
interrupts
CAL: 67 65 Function call
interrupts
TLB: 3679 4198 TLB
shootdowns
TRM: 0 0 Thermal event
interrupts
THR: 0 0 Threshold APIC
interrupts
SPU: 0 0 Spurious
interrupts
ERR:
0
MIS: 0


from dmesg

[ 9.220049] ricoh-mmc: Ricoh MMC Controller disabling driver
[ 9.220054] ricoh-mmc: Copyright(c) Philip Langdale
[ 9.258786] sdhci: Secure Digital Host Controller Interface driver
[ 9.258788] sdhci: Copyright(c) Pierre Ossman
[ 9.329406] ricoh-mmc: Ricoh MMC controller found at 0000:02:06.4
[1180:0843] (rev 10)
[ 9.329424] ricoh-mmc: Controller is now disabled.
[ 9.329463] sdhci-pci 0000:02:06.3: SDHCI controller found
[1180:0822] (rev 20)
[ 9.329480] sdhci-pci 0000:02:06.3: PCI INT D -> GSI 19 (level, low)
-> IRQ 19
[ 9.331556] Registered led device: mmc0::
[ 9.332608] mmc0: SDHCI controller on PCI [0000:02:06.3] using PIO


dmesg attached

tell me if you need other info

thanks

--
Cordiali Saluti
Alessandro Bono


Attachments:
dmesg-2.6.29.1 (51.31 kB)

2009-06-03 20:09:19

by Pierre Ossman

[permalink] [raw]
Subject: Re: [Sdhci-devel] 2.6.29.1 sdhci: irq 19: nobody cared

On Fri, 17 Apr 2009 17:00:18 +0200
Alessandro Bono <[email protected]> wrote:

> Hi
>
> This is a bug that occur from time to time on my (unsed) sdhci card
> drive
> this is with kernel 2.6.29.1 (not a regression, I had the same problem
> with older kernel)
>
> [ 2885.888003] irq 19: nobody cared (try booting with the "irqpoll"
> option)

Unfortunately it's most likely something else, which happens to be
sharing the interrupt line with the SD controller. Please try to get in
touch with the Linux ACPI people. They are generally very good at
sorting out irq issues.

Rgds
--
-- Pierre Ossman

Linux kernel, MMC maintainer http://www.kernel.org
rdesktop, core developer http://www.rdesktop.org
TigerVNC, core developer http://www.tigervnc.org

WARNING: This correspondence is being monitored by the
Swedish government. Make sure your server uses encryption
for SMTP traffic and consider using PGP for end-to-end
encryption.


Attachments:
signature.asc (198.00 B)