linux-kernel - Re: irq 18: nobody cared after resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 28 Aug 2009 11:16:50 +0200
From:	Jiri Slaby <jirislaby@...il.com>
To:	Zdenek Kabelac <zdenek.kabelac@...il.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-mmc@...r.kernel.org
Subject: Re: irq 18: nobody cared after resume

On 08/28/2009 10:48 AM, Zdenek Kabelac wrote:
> /proc/interrrupts:
> 18:        384        395   IO-APIC-fasteoi   uhci_hcd:usb7, mmc0
...
> HDA Intel 0000:00:1b.0: PCI INT B -> GSI 17 (level, low) -> IRQ 17
> irq 18: nobody cared (try booting with the "irqpoll" option)
> Pid: 0, comm: swapper Not tainted 2.6.31-rc7-00059-ge716334 #19
> Call Trace:
>  <IRQ>  [<ffffffff810a500b>] __report_bad_irq+0x2b/0xa0
>  [<ffffffff810a520a>] note_interrupt+0x18a/0x1d0
>  [<ffffffff810a588d>] handle_fasteoi_irq+0xcd/0xf0
>  [<ffffffff8100ee99>] handle_irq+0x49/0xa0
>  [<ffffffff813e1343>] do_IRQ+0x73/0xf0
>  [<ffffffff8100cb93>] ret_from_intr+0x0/0xf
>  <EOI>  [<ffffffff8129057d>] ? acpi_idle_enter_c1+0xa1/0xc0
>  [<ffffffff8107d83d>] ? trace_hardirqs_on+0xd/0x10
>  [<ffffffff81290580>] ? acpi_idle_enter_c1+0xa4/0xc0
>  [<ffffffff8129057d>] ? acpi_idle_enter_c1+0xa1/0xc0
>  [<ffffffff81334a9b>] ? cpuidle_idle_call+0x9b/0xf0
>  [<ffffffff8100aa7b>] ? cpu_idle+0x6b/0xd0
>  [<ffffffff813c72ca>] ? rest_init+0x7a/0x80
>  [<ffffffff81601b02>] ? start_kernel+0x38f/0x39b
>  [<ffffffff81601128>] ? x86_64_start_reservations+0x125/0x129
>  [<ffffffff8160120d>] ? x86_64_start_kernel+0xe1/0xe8
> handlers:
> [<ffffffffa0006720>] (usb_hcd_irq+0x0/0xa0 [usbcore])

The interesting thing is that there is no mmc handler. So it seems like
mmc disabled the irq in kernel, but not in HW?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/