[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] how to analyse xen call trace?

I got this while do operations on hypercalls, any idea on how to analysis the error? Look at the sentence in bold, the virtual address of do_hvm_op is 0xffff82d0801c988e in xen symbol files, while this log shows it is ffff82d0801b7f68. What does '+0x1a98/0x1fd0' mean?

(XEN) Xen call trace:
(XEN)    [<ffff82d080128132>] _write_unlock+0x22/0x40
(XEN)    [<ffff82d0801dee6e>] paging_log_dirty_range+0x13e/0x180
(XEN)    [<ffff82d08020d9f3>] hap_track_dirty_vram+0x393/0x4f0
(XEN)    [<ffff82d08015f08d>] context_switch+0x13d/0xe80
(XEN)    [<ffff82d08012a3bb>] add_entry+0x4b/0xb0
(XEN)    [<ffff82d0801b7f68>] do_hvm_op+0x1a98/0x1fd0
(XEN)    [<ffff82d080158635>] reprogram_timer+0x75/0xe0
(XEN)    [<ffff82d080215908>] toggle_guest_mode+0x48/0xc0
(XEN)    [<ffff82d080215a40>] do_iret+0xc0/0x1a0
(XEN)    [<ffff82d08021aef9>] syscall_enter+0xa9/0xae
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) FATAL TRAP: vector = 6 (invalid opcode)
(XEN) ****************************************
(XEN) Reboot in five seconds...

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.