http://bugzilla.novell.com/show_bug.cgi?id=553690
User jbeulich@novell.com added comment
http://bugzilla.novell.com/show_bug.cgi?id=553690#c5
--- Comment #5 from Jan Beulich
End of output of kernel console in case of crash :-
do_page_fault page_fault memcpy_c swiotlb_balance
swiotlb_bounce ???
unmap_single swiotlb_umap_sg_attrs _ata_sg_clean __ata_qc_comlete _ata_qc_comlete _ata_qc_comlete_multiple ahci_interrupt handle_IRQ_event handle_level_irq evtchn_do_upcall do_hypercall_callback 0xfffff...f802063ac xen_safe_halt xen_idle cpu_idle rest_init start_kernel x86_64_start_reservations x86_64_start_kernel
Just the function names don't tell much, unfortunately. However, it seems inconsistent that you have unmap_single() and memcpy_c() on the stack: swiotlb_bounce() calls memcpy() only for DMA_TO_DEVICE, but do_unmap_single() passes DMA_FROM_DEVICE. This may indicate there's earlier corruption, and hence we'll get nowhere without seeing the full hypervisor and kernel logs, i.e. we need to wait for you to set up serial. Btw., does this also occur for file:/ backed guest disks? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.