|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] dom0 kernel - irq nobody cared ... the continuing saga ..
Hi Jan / David / Konrad,
I was just testing a 3.19 kernel on my intel machine and again
ran into the sporadically appearing "irq nobody cared" on the dom0 kernel.
This occurs now for quite some kernel versions (running xen-unstable now,
but it also appeared in the past with builds that are now xen-4.5).
[ 1905.880200] irq 18: nobody cared (try booting with the "irqpoll" option)
[ 1905.914838] CPU: 0 PID: 0 Comm: swapper/0 Not tainted
3.19.0-creanuc-20150209-doflr+ #1
[ 1905.935473] Hardware name: /D53427RKE, BIOS
RKPPT10H.86A.0017.2013.0425.1251 04/25/2013
[ 1905.956149] 0000000000000000 ffff8800596ae88c ffffffff81897311
ffff8800596ae800
[ 1905.976929] ffffffff81081554 ffff8800596ae800 0000000000000000
0000000000000000
[ 1905.997906] ffffffff81081961 0000000000000000 0000000000000000
0000000000000012
[ 1906.018751] Call Trace:
[ 1906.039416] <IRQ> [<ffffffff81897311>] ? dump_stack+0x40/0x50
[ 1906.060678] [<ffffffff81081554>] ? __report_bad_irq+0x1e/0xbb
[ 1906.081953] [<ffffffff81081961>] ? note_interrupt+0x1a9/0x234
[ 1906.102733] [<ffffffff8107fac7>] ? handle_irq_event_percpu+0xd7/0xf1
[ 1906.122995] [<ffffffff8107fb18>] ? handle_irq_event+0x37/0x57
[ 1906.143275] [<ffffffff8108224a>] ? handle_fasteoi_irq+0x74/0xcb
[ 1906.163455] [<ffffffff8107f4b2>] ? generic_handle_irq+0x15/0x20
[ 1906.182889] [<ffffffff813a6b0b>] ? evtchn_fifo_handle_events+0x138/0x16f
[ 1906.202356] [<ffffffff813a48c9>] ? __xen_evtchn_do_upcall+0x39/0x69
[ 1906.222156] [<ffffffff813a5c41>] ? xen_evtchn_do_upcall+0x27/0x36
[ 1906.241987] [<ffffffff818a015e>] ? xen_do_hypervisor_callback+0x1e/0x30
[ 1906.261917] <EOI> [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20
[ 1906.282116] [<ffffffff810013aa>] ? xen_hypercall_sched_op+0xa/0x20
[ 1906.302364] [<ffffffff81007138>] ? xen_safe_halt+0xc/0x13
[ 1906.322525] [<ffffffff81013ae1>] ? default_idle+0x5/0x8
[ 1906.342592] [<ffffffff81078b8a>] ? cpu_startup_entry+0x114/0x25e
[ 1906.362771] [<ffffffff81efee9d>] ? start_kernel+0x422/0x42d
[ 1906.383029] [<ffffffff81efe880>] ? set_init_arg+0x50/0x50
[ 1906.402921] [<ffffffff81f019a0>] ? xen_start_kernel+0x4d3/0x4db
[ 1906.422483] handlers:
[ 1906.441717] [<ffffffff8155cd42>] ata_bmdma_interrupt
[ 1906.461174] Disabling IRQ #18
Is there any thing i could do / dump when this occurs or patch the kernel
to auto dump something to hopefully find out where this sporadic issue
comes from ?
Because previous attempts didn't seem to deliver any useful data, but i can't
trigger it, so probably i have to partly rely on hooking it up to the code
that leads to the "irq nobody cared" message, but probably on far less then
200000 iterations for it to contain something sensible.
The funky part is that this time it's the ata device with on ssd attached,
however i can still read and write normally (so it doesn't seem to need the irq
?)
/proc/interrupts shows the high count:
CPU0 CPU1 CPU2 CPU3
8: 0 0 0 0 xen-pirq-ioapic-edge rtc0
9: 1 0 0 0 xen-pirq-ioapic-level acpi
16: 29 0 0 0 xen-pirq-ioapic-level
ehci_hcd:usb3
18: 200000 0 0 0 xen-pirq-ioapic-level
ata_generic
23: 23145 0 0 0 xen-pirq-ioapic-level
ehci_hcd:usb4
24: 111697 0 0 0 xen-percpu-virq timer0
25: 0 0 0 0 xen-percpu-ipi spinlock0
26: 12989 0 0 0 xen-percpu-ipi resched0
27: 1123 0 0 0 xen-percpu-ipi callfunc0
28: 0 0 0 0 xen-percpu-virq debug0
29: 330 0 0 0 xen-percpu-ipi
callfuncsingle0
30: 1 0 0 0 xen-percpu-ipi irqwork0
31: 0 25012 0 0 xen-percpu-virq timer1
32: 0 1 0 0 xen-percpu-ipi spinlock1
33: 0 20107 0 0 xen-percpu-ipi resched1
34: 0 2232 0 0 xen-percpu-ipi callfunc1
35: 0 0 0 0 xen-percpu-virq debug1
36: 0 426 0 0 xen-percpu-ipi
callfuncsingle1
37: 0 0 0 0 xen-percpu-ipi irqwork1
38: 0 0 82595 0 xen-percpu-virq timer2
39: 0 0 0 0 xen-percpu-ipi spinlock2
40: 0 0 83192 0 xen-percpu-ipi resched2
41: 0 0 1295 0 xen-percpu-ipi callfunc2
42: 0 0 0 0 xen-percpu-virq debug2
43: 0 0 372 0 xen-percpu-ipi
callfuncsingle2
44: 0 0 0 0 xen-percpu-ipi irqwork2
45: 0 0 0 38677 xen-percpu-virq timer3
46: 0 0 0 0 xen-percpu-ipi spinlock3
47: 0 0 0 62021 xen-percpu-ipi resched3
48: 0 0 0 2130 xen-percpu-ipi callfunc3
49: 0 0 0 0 xen-percpu-virq debug3
50: 0 0 0 469 xen-percpu-ipi
callfuncsingle3
51: 0 0 0 0 xen-percpu-ipi irqwork3
52: 2422 0 0 0 xen-dyn-event xenbus
53: 0 0 0 0 xen-percpu-virq xen-pcpu
55: 23 0 0 0 xen-pirq-msi mei_me
56: 26273 0 0 0 xen-pirq-msi
0000:00:1f.2
57: 143 0 0 0 xen-pirq-msi xhci_hcd
58: 1222 0 0 0 xen-dyn-event
evtchn:xenstored
59: 0 0 0 0 xen-dyn-event
evtchn:xenstored
60: 413 0 0 0 xen-dyn-event
evtchn:xenstored
61: 1 0 0 0 xen-dyn-event
evtchn:xenconsoled
62: 1345095 0 0 0 xen-dyn-event
evtchn:qemu-system-i38
63: 46 0 0 0 xen-dyn-event
evtchn:qemu-system-i38
64: 495 0 0 0 xen-dyn-event
evtchn:xenstored
65: 16 0 0 0 xen-dyn-event
evtchn:xenconsoled
66: 426359 0 0 0 xen-dyn-event
evtchn:qemu-system-i38
67: 25116 0 0 0 xen-dyn-event
evtchn:qemu-system-i38
68: 9085 0 0 0 xen-dyn-event
evtchn:qemu-system-i38
69: 67 0 0 0 xen-dyn-event
evtchn:qemu-system-i38
70: 11671 0 0 0 xen-dyn-event
blkif-backend
71: 1657 0 0 0 xen-dyn-event
blkif-backend
72: 19392 0 0 0 xen-dyn-event
vif2.0-q0-tx
73: 1 0 0 0 xen-dyn-event
vif2.0-q0-rx
74: 503 0 0 0 xen-dyn-event
blkif-backend
75: 14565 0 0 0 xen-dyn-event
vif1.0-q0-tx
76: 1 0 0 0 xen-dyn-event
vif1.0-q0-rx
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 0 0 0 0 Local timer interrupts
SPU: 0 0 0 0 Spurious interrupts
PMI: 0 0 0 0 Performance monitoring
interrupts
IWI: 1 0 0 0 IRQ work interrupts
RTR: 0 0 0 0 APIC ICR read retries
RES: 12989 20107 83193 62022 Rescheduling interrupts
CAL: 1453 2658 1667 2599 Function call interrupts
TLB: 0 0 0 0 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: 9 9 9 9 Machine check polls
HYP: 2196482 47720 167263 103207 Hypervisor callback
interrupts
ERR: 0
MIS: 0
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |