linux-kernel - Re: irq N: nobody cared (try booting with the "irqpoll" option)

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4D46BF6E.4090401@ladisch.de>
Date:	Mon, 31 Jan 2011 14:55:58 +0100
From:	Clemens Ladisch <clemens@...isch.de>
To:	"Artem S. Tashkinov" <t.artem@...os.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: irq N: nobody cared (try booting with the "irqpoll" option)

Artem S. Tashkinov wrote:
> I've never faced this problem before but after I've recently
> renewed my PC (a new MoBo and CPU) I'm now randomly getting
> this kernel message after booting the PC:
> 
> irq 18: nobody cared

One of the devices on interrupt line 18 has raised an interrupt, but
no driver has accepted it.

Have a look into /proc/interrupts to see which drivers are registered
for irq 18 (e100 in your case), then search in the output of "lspci -v"
for any _other_ devices that use irq 18.

It's also possible that one of the drivers is buggy and mistakenly said
"this interrupt is not from my device", or, in theory, that the BIOS is
buggy and has mislabeled some device's interrupt.

According to Google, there are other reports of this message with the
e100 driver.  Does your network work?  If not, does irqpoll help?

Regards,
Clemens
--
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/