search for: irq_get_irq_data

...| irq_to_desc(); 1) | handle_edge_irq() { 1) 0.107 us | _raw_spin_lock(); 1) | ack_dynirq() { 1) | evtchn_from_irq() { 1) | info_for_irq() { 1) | irq_get_irq_data() { 1) 0.052 us | irq_to_desc(); 1) 0.418 us | } 1) 0.782 us | } 1) 1.135 us | } 1) 0.049 us | irq_move_irq(); 1) 1.800 us | } 1) | handle_irq_event() { 1) 0.16...

...[<c10b5462>] ? sched_clock_local+0xb2/0x190 [ 43.193098] [<c1077a77>] ? pvclock_clocksource_read+0xd7/0x170 [ 43.193098] [<c1039d75>] ? xen_clocksource_read+0x25/0x40 [ 43.193098] [<c1103dd4>] handle_irq_event_percpu+0x54/0x200 [ 43.193098] [<c1106438>] ? irq_get_irq_data+0x8/0x10 [ 43.193098] [<c134b188>] ? info_for_irq+0x8/0x20 [ 43.193098] [<c1106724>] handle_percpu_irq+0x34/0x50 [ 43.193098] [<c134ba0d>] __xen_evtchn_do_upcall+0x2cd/0x2e0 [ 43.193098] [<c10d7f54>] ? tick_check_idle+0xb4/0xc0 [ 43.193098] [<c134ba4b>]...

Hi, I have been receiving messages on a new DomU''s kern.log. I''ve done a lot of googling, but haven''t came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on