Jump to content

Disabling IRQ #19

meep

By meep
in General Support (V5 and Older)

Recommended Posts

meep Enthusiast

meep

Posted
Posted

Hi

 

I'm getting the following with great regularity in my UnRaid/Xen log files. Wondering if anyone has any insight? In the current case, this occurred 9 hours after system boot with no other activity taking place at all (most recent logged activity was a full spinout at 02:11.

 

 

Oct 30 10:23:25 UnRaid kernel: irq 19: nobody cared (try booting with the "irqpoll" option)
Oct 30 10:23:25 UnRaid kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.3-unRAID #3
Oct 30 10:23:25 UnRaid kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD5, BIOS FCb 05/31/2013
Oct 30 10:23:25 UnRaid kernel: 0000000000000000 ffff880848003df0 ffffffff815d9532 ffff880813f14800
Oct 30 10:23:25 UnRaid kernel: ffff880848003e18 ffffffff810779a2 ffff880813f14800 0000000000000000
Oct 30 10:23:25 UnRaid kernel: 0000000000000013 ffff880848003e50 ffffffff81077dab 0000000000000013
Oct 30 10:23:25 UnRaid kernel: Call Trace:
Oct 30 10:23:25 UnRaid kernel:   [] dump_stack+0x45/0x56
Oct 30 10:23:25 UnRaid kernel: [] __report_bad_irq+0x2a/0xbc
Oct 30 10:23:25 UnRaid kernel: [] note_interrupt+0x19c/0x221
Oct 30 10:23:25 UnRaid kernel: [] handle_irq_event_percpu+0xdd/0xec
Oct 30 10:23:25 UnRaid kernel: [] handle_irq_event+0x39/0x57
Oct 30 10:23:25 UnRaid kernel: [] handle_fasteoi_irq+0x80/0xe0
Oct 30 10:23:25 UnRaid kernel: [] generic_handle_irq+0x19/0x25
Oct 30 10:23:25 UnRaid kernel: [] evtchn_fifo_handle_events+0x12d/0x156
Oct 30 10:23:25 UnRaid kernel: [] __xen_evtchn_do_upcall+0x48/0x75
Oct 30 10:23:25 UnRaid kernel: [] xen_evtchn_do_upcall+0x2e/0x3f
Oct 30 10:23:25 UnRaid kernel: [] xen_do_hypervisor_callback+0x1e/0x30
Oct 30 10:23:25 UnRaid kernel:   [] ? xen_hypercall_sched_op+0xa/0x20
Oct 30 10:23:25 UnRaid kernel: [] ? xen_hypercall_sched_op+0xa/0x20
Oct 30 10:23:25 UnRaid kernel: [] ? xen_safe_halt+0x10/0x18
Oct 30 10:23:25 UnRaid kernel: [] ? default_idle+0x9/0xd
Oct 30 10:23:25 UnRaid kernel: [] ? arch_cpu_idle+0xa/0xc
Oct 30 10:23:25 UnRaid kernel: [] ? cpu_startup_entry+0x12c/0x232
Oct 30 10:23:25 UnRaid kernel: [] ? rest_init+0x72/0x74
Oct 30 10:23:25 UnRaid kernel: [] ? start_kernel+0x3d6/0x3e2
Oct 30 10:23:25 UnRaid kernel: [] ? set_init_arg+0x53/0x53
Oct 30 10:23:25 UnRaid kernel: [] ? x86_64_start_reservations+0x2a/0x2c
Oct 30 10:23:25 UnRaid kernel: [] ? xen_start_kernel+0x521/0x52b
Oct 30 10:23:25 UnRaid kernel: handlers:
Oct 30 10:23:25 UnRaid kernel: [] ahci_interrupt [libahci]
Oct 30 10:23:25 UnRaid kernel: Disabling IRQ #19

Link to comment
jonp Mentor

jonp

Posted
Posted

Hi

 

I'm getting the following with great regularity in my UnRaid/Xen log files. Wondering if anyone has any insight? In the current case, this occurred 9 hours after system boot with no other activity taking place at all (most recent logged activity was a full spinout at 02:11.

 

 

Oct 30 10:23:25 UnRaid kernel: irq 19: nobody cared (try booting with the "irqpoll" option)
Oct 30 10:23:25 UnRaid kernel: CPU: 0 PID: 0 Comm: swapper/0 Not tainted 3.16.3-unRAID #3
Oct 30 10:23:25 UnRaid kernel: Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./990FXA-UD5, BIOS FCb 05/31/2013
Oct 30 10:23:25 UnRaid kernel: 0000000000000000 ffff880848003df0 ffffffff815d9532 ffff880813f14800
Oct 30 10:23:25 UnRaid kernel: ffff880848003e18 ffffffff810779a2 ffff880813f14800 0000000000000000
Oct 30 10:23:25 UnRaid kernel: 0000000000000013 ffff880848003e50 ffffffff81077dab 0000000000000013
Oct 30 10:23:25 UnRaid kernel: Call Trace:
Oct 30 10:23:25 UnRaid kernel:   [] dump_stack+0x45/0x56
Oct 30 10:23:25 UnRaid kernel: [] __report_bad_irq+0x2a/0xbc
Oct 30 10:23:25 UnRaid kernel: [] note_interrupt+0x19c/0x221
Oct 30 10:23:25 UnRaid kernel: [] handle_irq_event_percpu+0xdd/0xec
Oct 30 10:23:25 UnRaid kernel: [] handle_irq_event+0x39/0x57
Oct 30 10:23:25 UnRaid kernel: [] handle_fasteoi_irq+0x80/0xe0
Oct 30 10:23:25 UnRaid kernel: [] generic_handle_irq+0x19/0x25
Oct 30 10:23:25 UnRaid kernel: [] evtchn_fifo_handle_events+0x12d/0x156
Oct 30 10:23:25 UnRaid kernel: [] __xen_evtchn_do_upcall+0x48/0x75
Oct 30 10:23:25 UnRaid kernel: [] xen_evtchn_do_upcall+0x2e/0x3f
Oct 30 10:23:25 UnRaid kernel: [] xen_do_hypervisor_callback+0x1e/0x30
Oct 30 10:23:25 UnRaid kernel:   [] ? xen_hypercall_sched_op+0xa/0x20
Oct 30 10:23:25 UnRaid kernel: [] ? xen_hypercall_sched_op+0xa/0x20
Oct 30 10:23:25 UnRaid kernel: [] ? xen_safe_halt+0x10/0x18
Oct 30 10:23:25 UnRaid kernel: [] ? default_idle+0x9/0xd
Oct 30 10:23:25 UnRaid kernel: [] ? arch_cpu_idle+0xa/0xc
Oct 30 10:23:25 UnRaid kernel: [] ? cpu_startup_entry+0x12c/0x232
Oct 30 10:23:25 UnRaid kernel: [] ? rest_init+0x72/0x74
Oct 30 10:23:25 UnRaid kernel: [] ? start_kernel+0x3d6/0x3e2
Oct 30 10:23:25 UnRaid kernel: [] ? set_init_arg+0x53/0x53
Oct 30 10:23:25 UnRaid kernel: [] ? x86_64_start_reservations+0x2a/0x2c
Oct 30 10:23:25 UnRaid kernel: [] ? xen_start_kernel+0x521/0x52b
Oct 30 10:23:25 UnRaid kernel: handlers:
Oct 30 10:23:25 UnRaid kernel: [] ahci_interrupt [libahci]
Oct 30 10:23:25 UnRaid kernel: Disabling IRQ #19

Are you having an issue though?

Link to comment
meep Enthusiast

meep

Posted
  • Author
Posted

Hi jonp

 

Nothing specific but I have come across general slowdowns and wholesale system crashes but I've been putting that down to me doing a bunch of experimentation with Xen VMs, swapping hardware about etc.

 

However, on boot today, suddenly one of my onboard sata ports stopped recognising attached disks. (I swapped cables, power leads and disks but to no avail, port 3 aways showed up as 'not connected' in bios).

 

Looking at boot, it seems IRQ19 is assigned to this onboard controller;

 

Oct 30 19:08:49 UnRaid kernel: ata1: SATA max UDMA/133 abar m1024@0xfeb07000 port 0xfeb07100 irq 19
Oct 30 19:08:49 UnRaid kernel: ata2: SATA max UDMA/133 abar m1024@0xfeb07000 port 0xfeb07180 irq 19
Oct 30 19:08:49 UnRaid kernel: ata3: SATA max UDMA/133 abar m1024@0xfeb07000 port 0xfeb07200 irq 19
Oct 30 19:08:49 UnRaid kernel: ata4: SATA max UDMA/133 abar m1024@0xfeb07000 port 0xfeb07280 irq 19
Oct 30 19:08:49 UnRaid kernel: ata5: SATA max UDMA/133 abar m1024@0xfeb07000 port 0xfeb07300 irq 19
Oct 30 19:08:49 UnRaid kernel: ata6: SATA max UDMA/133 abar m1024@0xfeb07000 port 0xfeb07380 irq 19

 

So, putting two and two together, it maybe that my motherboard is developing a fault :-(

 

For now, I've attached the HD that was on port 3 to a PCIe controller and I'll see how that goes. Trouble is it can take about 10 hours for the Disabling IRQ 19 error to show up so it's a tedious test process!

 

Peter

 

 

Link to comment

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...