* irq N: nobody cared (try booting with the "irqpoll" option)
[not found] <9147572.49771296475645053.JavaMail.root@mail-zbox20.bo3.lycos.com>
@ 2011-01-31 12:08 ` Artem S. Tashkinov
2011-01-31 13:55 ` Clemens Ladisch
0 siblings, 1 reply; 4+ messages in thread
From: Artem S. Tashkinov @ 2011-01-31 12:08 UTC (permalink / raw)
To: linux-kernel
Hi everyone!
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:
[ 4684.693288] irq 18: nobody cared (try booting with the "irqpoll" option)
[ 4684.693294] Pid: 0, comm: swapper Tainted: P 2.6.37-ic #1
[ 4684.693296] Call Trace:
[ 4684.693303] [<c129ebd9>] ? printk+0x18/0x1a
[ 4684.693309] [<c1066637>] __report_bad_irq.clone.2+0x27/0x90
[ 4684.693314] [<c10667ef>] note_interrupt+0x14f/0x190
[ 4684.693320] [<c101cc72>] ? ack_apic_level+0x62/0x1b0
[ 4684.693323] [<c1068354>] ? move_native_irq+0x14/0x50
[ 4684.693328] [<c10672fb>] handle_fasteoi_irq+0xab/0xd0
[ 4684.693332] [<c1067250>] ? handle_fasteoi_irq+0x0/0xd0
[ 4684.693334] <IRQ> [<c1004e24>] ? do_IRQ+0x44/0xc0
[ 4684.693340] [<c1003229>] ? common_interrupt+0x29/0x30
[ 4684.693344] [<c1003229>] ? common_interrupt+0x29/0x30
[ 4684.693348] [<c103007b>] ? scheduler_tick+0x18b/0x220
[ 4684.693353] [<c117553f>] ? intel_idle+0xaf/0x100
[ 4684.693357] [<c1221c6e>] ? cpuidle_idle_call+0x6e/0xf0
[ 4684.693360] [<c10016e6>] ? cpu_idle+0x46/0x80
[ 4684.693365] [<c129127b>] ? rest_init+0x7b/0x80
[ 4684.693369] [<c13986e1>] ? start_kernel+0x26e/0x274
[ 4684.693373] [<c13981b9>] ? unknown_bootoption+0x0/0x1a3
[ 4684.693377] [<c139808e>] ? i386_start_kernel+0x8e/0x90
[ 4684.693379] handlers:
[ 4684.693380] [<f89b4c20>] (e100_intr+0x0/0xd0 [e100])
[ 4684.693397] Disabling IRQ #18
The Internet and even kernel bugzilla are rife with reports like this
one and almost all of them are left unanswered or unresolved (for
instance see kernel bugzilla reports 15307 and 17672).
Can anyone shed light on this problem?
How one can debug/understand/eliminate it? Is it safe to use irqpoll
boot option?
Best wishes,
Artem
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: irq N: nobody cared (try booting with the "irqpoll" option)
2011-01-31 12:08 ` irq N: nobody cared (try booting with the "irqpoll" option) Artem S. Tashkinov
@ 2011-01-31 13:55 ` Clemens Ladisch
2011-01-31 15:16 ` Artem S. Tashkinov
0 siblings, 1 reply; 4+ messages in thread
From: Clemens Ladisch @ 2011-01-31 13:55 UTC (permalink / raw)
To: Artem S. Tashkinov; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: irq N: nobody cared (try booting with the "irqpoll" option)
2011-01-31 13:55 ` Clemens Ladisch
@ 2011-01-31 15:16 ` Artem S. Tashkinov
2011-01-31 16:33 ` Clemens Ladisch
0 siblings, 1 reply; 4+ messages in thread
From: Artem S. Tashkinov @ 2011-01-31 15:16 UTC (permalink / raw)
To: Clemens Ladisch; +Cc: linux-kernel
----- "Clemens Ladisch" <clemens@ladisch.de> wrote:
> 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?
>
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)
Subsystem: ASUSTeK Computer Inc. Device 844d
Flags: medium devsel, IRQ 18
Memory at fb624000 (64-bit, non-prefetchable) [size=256]
I/O ports at f000 [size=32]
Kernel driver in use: i801_smbus
Kernel modules: i2c-i801
and
08:00.0 Ethernet controller: Intel Corporation 82557/8/9/0/1 Ethernet Pro 100 (rev 10)
Subsystem: Intel Corporation Device 0070
Flags: bus master, medium devsel, latency 32, IRQ 18
Memory at fb231000 (32-bit, non-prefetchable) [size=4K]
I/O ports at c080 [size=64]
Memory at fb200000 (32-bit, non-prefetchable) [size=128K]
Expansion ROM at fb220000 [disabled] [size=64K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: e100
Kernel modules: e100
According to /proc/interrupts only e100 module claims this interrupt:
CPU0 CPU1 CPU2 CPU3
0: 110 0 0 0 IO-APIC-edge timer
1: 53483 0 12 0 IO-APIC-edge i8042
4: 2 0 0 0 IO-APIC-edge
8: 34 0 0 0 IO-APIC-edge rtc0
9: 0 0 0 0 IO-APIC-fasteoi acpi
18: 1200001 0 0 0 IO-APIC-fasteoi eth1
19: 1864975 0 0 0 IO-APIC-fasteoi ahci, EMU10K1
23: 452718 884 0 0 IO-APIC-fasteoi ehci_hcd:usb3, ehci_hcd:usb4
40: 0 0 0 0 PCI-MSI-edge PCIe PME
41: 0 0 0 0 PCI-MSI-edge PCIe PME
42: 0 0 0 0 PCI-MSI-edge PCIe PME
43: 0 0 0 0 PCI-MSI-edge PCIe PME
44: 0 0 0 0 PCI-MSI-edge PCIe PME
45: 0 0 0 0 PCI-MSI-edge PCIe PME
46: 0 0 0 0 PCI-MSI-edge PCIe PME
47: 317397 0 0 0 PCI-MSI-edge ahci
48: 0 0 0 0 PCI-MSI-edge ahci
49: 9453 0 0 0 PCI-MSI-edge eth0
50: 1 0 0 0 PCI-MSI-edge xhci_hcd
51: 0 0 0 0 PCI-MSI-edge xhci_hcd
52: 0 0 0 0 PCI-MSI-edge xhci_hcd
53: 0 0 0 0 PCI-MSI-edge xhci_hcd
54: 0 0 0 0 PCI-MSI-edge xhci_hcd
55: 1 0 0 0 PCI-MSI-edge xhci_hcd
56: 0 0 0 0 PCI-MSI-edge xhci_hcd
57: 0 0 0 0 PCI-MSI-edge xhci_hcd
58: 0 0 0 0 PCI-MSI-edge xhci_hcd
59: 0 0 0 0 PCI-MSI-edge xhci_hcd
60: 647 340 0 0 PCI-MSI-edge hda_intel
61: 18966 0 0 0 PCI-MSI-edge nvidia
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 10419216 12012477 13088898 10786868 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 Performance monitoring interrupts
IWI: 0 0 0 0 IRQ work interrupts
RES: 18626 25210 16331 15105 Rescheduling interrupts
CAL: 24856 22805 45874 51634 Function call interrupts
TLB: 42997 27281 20665 18604 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
MCE: 0 0 0 0 Machine check exceptions
MCP: 65 65 65 65 Machine check polls
ERR: 3
MIS: 0
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: irq N: nobody cared (try booting with the "irqpoll" option)
2011-01-31 15:16 ` Artem S. Tashkinov
@ 2011-01-31 16:33 ` Clemens Ladisch
0 siblings, 0 replies; 4+ messages in thread
From: Clemens Ladisch @ 2011-01-31 16:33 UTC (permalink / raw)
To: Artem S. Tashkinov; +Cc: linux-kernel
Artem S. Tashkinov wrote:
> ----- "Clemens Ladisch" <clemens@ladisch.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
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-01-31 16:33 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <9147572.49771296475645053.JavaMail.root@mail-zbox20.bo3.lycos.com>
2011-01-31 12:08 ` irq N: nobody cared (try booting with the "irqpoll" option) Artem S. Tashkinov
2011-01-31 13:55 ` Clemens Ladisch
2011-01-31 15:16 ` Artem S. Tashkinov
2011-01-31 16:33 ` Clemens Ladisch
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox