Running a similar setup on a ext4 backing store can also trigger ooms
w/o the hangs, where as the first hang occurred when running on a ZFS
backing store.

Jul  2 19:18:52 mahobay kernel: [ 1579.086409] Call Trace:
Jul  2 19:18:52 mahobay kernel: [ 1579.086415]  dump_stack+0x67/0x86
Jul  2 19:18:52 mahobay kernel: [ 1579.086417]  dump_header+0x54/0x2fb
Jul  2 19:18:52 mahobay kernel: [ 1579.086419]  ? 
cpuset_mems_allowed_intersects+0x25/0x30
Jul  2 19:18:52 mahobay kernel: [ 1579.086421]  
oom_kill_process.cold.31+0xb/0x10
Jul  2 19:18:52 mahobay kernel: [ 1579.086422]  out_of_memory+0x1c0/0x480
Jul  2 19:18:52 mahobay kernel: [ 1579.086424]  
__alloc_pages_slowpath+0xb6d/0xeb0
Jul  2 19:18:52 mahobay kernel: [ 1579.086427]  
__alloc_pages_nodemask+0x2e3/0x330
Jul  2 19:18:52 mahobay kernel: [ 1579.086429]  alloc_pages_vma+0x7e/0x1d0
Jul  2 19:18:52 mahobay kernel: [ 1579.086431]  __handle_mm_fault+0x93d/0x1240
Jul  2 19:18:52 mahobay kernel: [ 1579.086433]  handle_mm_fault+0xc9/0x1f0
Jul  2 19:18:52 mahobay kernel: [ 1579.086435]  __get_user_pages+0x248/0x720
Jul  2 19:18:52 mahobay kernel: [ 1579.086437]  
get_user_pages_unlocked+0x156/0x1f0
Jul  2 19:18:52 mahobay kernel: [ 1579.086456]  
__gfn_to_pfn_memslot+0x12e/0x400 [kvm]
Jul  2 19:18:52 mahobay kernel: [ 1579.086471]  try_async_pf+0x89/0x250 [kvm]
Jul  2 19:18:52 mahobay kernel: [ 1579.086486]  tdp_page_fault+0x140/0x280 [kvm]
Jul  2 19:18:52 mahobay kernel: [ 1579.086491]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:52 mahobay kernel: [ 1579.086505]  kvm_mmu_page_fault+0x79/0x640 
[kvm]
Jul  2 19:18:52 mahobay kernel: [ 1579.086509]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086512]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086515]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086518]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086522]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086525]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086528]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086532]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086535]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086538]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086542]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086545]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086548]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086551]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086554]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086557]  ? vmx_vmexit+0x1b/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086560]  ? vmx_vmexit+0xf/0x30 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086564]  handle_ept_violation+0xcf/0x220 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086567]  vmx_handle_exit+0xab/0x7d0 
[kvm_intel]
Jul  2 19:18:53 mahobay kernel: [ 1579.086581]  vcpu_enter_guest+0x2db/0x1500 
[kvm]
Jul  2 19:18:53 mahobay kernel: [ 1579.086583]  ? __schedule+0x2c2/0x650
Jul  2 19:18:53 mahobay kernel: [ 1579.086597]  
kvm_arch_vcpu_ioctl_run+0xd5/0x580 [kvm]
Jul  2 19:18:53 mahobay kernel: [ 1579.086609]  kvm_vcpu_ioctl+0x24f/0x620 [kvm]
Jul  2 19:18:53 mahobay kernel: [ 1579.086611]  ? __seccomp_filter+0x7e/0x6c0
Jul  2 19:18:53 mahobay kernel: [ 1579.086613]  ? __wake_up_locked_key+0x1f/0x30
Jul  2 19:18:53 mahobay kernel: [ 1579.086616]  do_vfs_ioctl+0xad/0x640
Jul  2 19:18:53 mahobay kernel: [ 1579.086617]  ? __secure_computing+0x42/0xd0
Jul  2 19:18:53 mahobay kernel: [ 1579.086619]  ksys_ioctl+0x6b/0xa0
Jul  2 19:18:53 mahobay kernel: [ 1579.086621]  __x64_sys_ioctl+0x1e/0x30
Jul  2 19:18:53 mahobay kernel: [ 1579.086623]  do_syscall_64+0x5e/0x140
Jul  2 19:18:53 mahobay kernel: [ 1579.086625]  
entry_SYSCALL_64_after_hwframe+0x44/0xa9

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835072

Title:
  vm related hang on Eoan 5.2.0-7-generic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835072/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to