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 for Android: free password hash cracker in your pocket

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

Message-ID: <4D46E45B.6060501@ladisch.de>
Date:	Mon, 31 Jan 2011 17:33:31 +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:
> ----- "Clemens Ladisch" <clemens@...isch.de> wrote:
> > Artem S. Tashkinov wrote:
> > > irq 18: nobody cared
> >
> > According to Google, there are other reports of this message with the
> > e100 driver.  Does your network work?  If not, does irqpoll help?
> 
> eth1/e100 is what I'm using to get into the Internet so it's working
> correctly.
> 
> According to lspci -v I have two devices using IRQ 18:
> 
> 00:1f.3 SMBus: Intel Corporation Cougar Point SMBus Controller (rev 04)
>         Kernel driver in use: i801_smbus
> 
> and
> 
> 08:00.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 10)
>         Kernel driver in use: e100
> 
> According to /proc/interrupts only e100 module claims this interrupt

It's possible that the BIOS used the SMBus controller with interrupts,
and that the i2c-i801 driver did not properly reset this device when
loading.

You could try to blacklist the i2c-i801 module (add the line
  blacklist i2c-i801
to any existing or a new file in /etc/modprobe.d/) and then rebooting.

> I will try to reboot with irqpoll a bit later however before I try it I'd
> be very grateful to know what exactly this option does/if it affects
> performance/stability/etc and why it's not used/enabled by default.

The irqpoll option is used for machines with broken interrupt routing;
when an interrupt arrives, the kernel tries the handler for all other
interrupt lines, too, and it does the same checks in every timer
interrupt (in case that some interrupt did not arrive at all).

This lowers performance, and is useful only if some device would _not_
work without it.  Your e100 works, so don't bother.

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/