[Xen-users] [4.14.66-6.el7xen.x86_64] Oops: PVH domUs blocked, Windows HVM domU running 100%

[Adi Pircalabu <adi@xxxxxxxxxxx>]

(First, sorry for cross-posting)

Can't remember seeing this before. Been using the kernel-xen and xen 
4.10 packages from:
http://au1.mirror.crc.id.au/repo/kernel-xen-release-el7-latest.noarch.rpm

kernel-xen-4.14.66-6.el7xen.x86_64
xen410-licenses-4.10.1-3.el7.x86_64
xen410-runtime-4.10.1-3.el7.x86_64
xen410-hypervisor-4.10.1-3.el7.x86_64
xen410-4.10.1-3.el7.x86_64
xen410-libs-4.10.1-3.el7.x86_64
xen410-ocaml-4.10.1-3.el7.x86_64

The affected system is an Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz 
desktop, Intel H110M PRO-VH PLUS (MS-7A15) motherboard running CentOS 7 
with 2 CentOS 7 PVH domUs running the same kernel as dom0 and one HVM 
running Windows 2012 R2. I'm also using it as an SMS test service with a 
Galaxy S6 connected into one of the USB ports using the cdc_acm module.
First, the warning, most likely caused by disconnecting the mobile 
phone:
Aug 23 16:43:00 xen3 kernel: usb 1-5: USB disconnect, device number 9
Aug 23 16:43:00 xen3 kernel: ------------[ cut here ]------------
Aug 23 16:43:00 xen3 kernel: WARNING: CPU: 0 PID: 10962 at 
arch/x86/xen/multicalls.c:130 xen_mc_flush+0x19a/0x1a0
Aug 23 16:43:00 xen3 kernel: Modules linked in: tun xt_physdev 
br_netfilter iptable_filter bridge stp llc snd_hda_codec_hdmi 
crct10dif_pclmul ghash_clmulni_intel snd_hda_codec_realtek 
snd_hda_codec_generic pcbc dm_mod dax snd_hda_intel s
nd_hda_codec snd_hda_core snd_hwdep snd_seq iTCO_wdt iTCO_vendor_support 
snd_seq_device mxm_wmi snd_pcm aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd sg snd_timer pcspkr snd soundcore i2c_i801 shpchp 
mei_me mei wmi xenfs cdc_acm
xen_privcmd ip_tables xfs libcrc32c sd_mod i915 iosf_mbi i2c_algo_bit 
drm_kms_helper drm crc32c_intel serio_raw xhci_pci r8169 mii ahci 
libahci xhci_hcd i2c_core video xen_acpi_processor xen_pciback 
xen_netback xen_gntalloc xen_gntdev xe
n_evtchn ipv6 crc_ccitt autofs4
Aug 23 16:43:00 xen3 kernel: CPU: 0 PID: 10962 Comm: kworker/0:1 Not 
tainted 4.14.66-6.el7xen.x86_64 #2
Aug 23 16:43:00 xen3 kernel: Hardware name: MSI MS-7A15/H110M PRO-VH 
PLUS (MS-7A15), BIOS 1.70 04/21/2017
Aug 23 16:43:00 xen3 kernel: Workqueue: usb_hub_wq hub_event
Aug 23 16:43:00 xen3 kernel: task: ffff88002d97b600 task.stack: 
ffffc90042b0c000
Aug 23 16:43:00 xen3 kernel: RIP: e030:xen_mc_flush+0x19a/0x1a0
Aug 23 16:43:00 xen3 kernel: RSP: e02b:ffffc90042b0fae8 EFLAGS: 00010002
Aug 23 16:43:00 xen3 kernel: RAX: 0000000000000000 RBX: 0000000000000000 
RCX: 0000000000000001
Aug 23 16:43:00 xen3 kernel: RDX: ffff88003f614298 RSI: 0000000000000004 
RDI: 0000000000000000
Aug 23 16:43:00 xen3 kernel: RBP: 0000000000000001 R08: 0000000000000000 
R09: ffffffff82643340
Aug 23 16:43:00 xen3 kernel: R10: ffff880036b58000 R11: ffffea000013e400 
R12: 0000000000000000
Aug 23 16:43:00 xen3 kernel: R13: ffff88003f614180 R14: 0000000000000000 
R15: 0000000000000004
Aug 23 16:43:00 xen3 kernel: FS:  0000000000000000(0000) 
GS:ffff88003f600000(0000) knlGS:0000000000000000
Aug 23 16:43:00 xen3 kernel: CS:  e033 DS: 0000 ES: 0000 CR0: 
0000000080050033
Aug 23 16:43:00 xen3 kernel: CR2: 00000000018a4338 CR3: 0000000004e84000 
CR4: 0000000000042660
Aug 23 16:43:00 xen3 kernel: Call Trace:
Aug 23 16:43:00 xen3 kernel: xen_remap_exchanged_ptes+0x18f/0x260
Aug 23 16:43:00 xen3 kernel: xen_destroy_contiguous_region+0x10e/0x180
Aug 23 16:43:00 xen3 kernel: xen_swiotlb_free_coherent+0x174/0x230
Aug 23 16:43:00 xen3 kernel: ? __free_pages_ok+0x140/0x290
Aug 23 16:43:00 xen3 kernel: acm_write_buffers_free+0x35/0x40 [cdc_acm]
Aug 23 16:43:00 xen3 kernel: acm_disconnect+0x107/0x170 [cdc_acm]
Aug 23 16:43:00 xen3 kernel: usb_unbind_interface+0x84/0x280
Aug 23 16:43:00 xen3 kernel: device_release_driver_internal+0x148/0x210
Aug 23 16:43:00 xen3 kernel: bus_remove_device+0xe5/0x160
Aug 23 16:43:00 xen3 kernel: device_del+0x1d5/0x320
Aug 23 16:43:00 xen3 kernel: ? usb_remove_ep_devs+0x1b/0x30
Aug 23 16:43:00 xen3 kernel: usb_disable_device+0x92/0x250
Aug 23 16:43:00 xen3 kernel: usb_disconnect+0x92/0x270
Aug 23 16:43:00 xen3 kernel: hub_event+0x709/0x14c0
Aug 23 16:43:00 xen3 kernel: process_one_work+0x13b/0x340
Aug 23 16:43:00 xen3 kernel: worker_thread+0x47/0x3e0
Aug 23 16:43:00 xen3 kernel: kthread+0xff/0x140
Aug 23 16:43:00 xen3 kernel: ? process_one_work+0x340/0x340
Aug 23 16:43:00 xen3 kernel: ? kthread_create_on_node+0x40/0x40
Aug 23 16:43:00 xen3 kernel: ret_from_fork+0x1f/0x40
Aug 23 16:43:00 xen3 kernel: Code: 9e 00 41 3b 5d 08 72 da 41 c7 45 08 
00 00 00 00 4c 89 e7 e8 49 11 00 00 66 90 85 ed 75 0d 5b 5d 41 5c 41 5d 
41 5e 41 5f c3 0f 0b <0f> 0b eb ef 0f 0b 0f 1f 44 00 00 55 48 89 e5 41 
57 41 56 41 55
Aug 23 16:43:00 xen3 kernel: ---[ end trace f8c8cfe05a44d06d ]---

Then later the OOPS, out of the blue:

Aug 24 03:39:16 xen3 kernel: BUG: unable to handle kernel paging request 
at ffff880036b5b000
Aug 24 03:39:16 xen3 kernel: IP: clear_page_erms+0x7/0x10
Aug 24 03:39:16 xen3 kernel: PGD 200c067 P4D 200c067 PUD 200d067 PMD 
3ff4f067 PTE 0
Aug 24 03:39:16 xen3 kernel: Oops: 0002 [#1] SMP NOPTI
Aug 24 03:39:16 xen3 kernel: Modules linked in: tun xt_physdev 
br_netfilter iptable_filter bridge stp llc snd_hda_codec_hdmi 
crct10dif_pclmul ghash_clmulni_intel snd_hda_codec_realtek 
snd_hda_codec_generic pcbc dm_mod dax snd_hda_intel snd_hda_codec 
snd_hda_core snd_hwdep snd_seq iTCO_wdt iTCO_vendor_support 
snd_seq_device mxm_wmi snd_pcm aesni_intel aes_x86_64 crypto_simd 
glue_helper cryptd sg snd_timer pcspkr snd soundcore i2c_i801 shpchp 
mei_me mei wmi xenfs cdc_acm xen_privcmd ip_tables xfs libcrc32c sd_mod 
i915 iosf_mbi i2c_algo_bit drm_kms_helper drm crc32c_intel serio_raw 
xhci_pci r8169 mii ahci libahci xhci_hcd i2c_core video 
xen_acpi_processor xen_pciback xen_netback xen_gntalloc xen_gntdev 
xen_evtchn ipv6 crc_ccitt autofs4
Aug 24 03:39:16 xen3 kernel: CPU: 0 PID: 1439 Comm: 1.xvda1-0 Tainted: G 
       W       4.14.66-6.el7xen.x86_64 #2
Aug 24 03:39:16 xen3 kernel: Hardware name: MSI MS-7A15/H110M PRO-VH 
PLUS (MS-7A15), BIOS 1.70 04/21/2017
Aug 24 03:39:16 xen3 kernel: task: ffff880037160000 task.stack: 
ffffc900405a8000
Aug 24 03:39:16 xen3 kernel: RIP: e030:clear_page_erms+0x7/0x10
Aug 24 03:39:16 xen3 kernel: RSP: e02b:ffffc900405ab958 EFLAGS: 00010246
Aug 24 03:39:16 xen3 kernel: RAX: 0000000000000000 RBX: ffff880037160000 
RCX: 0000000000001000
Aug 24 03:39:16 xen3 kernel: RDX: 0000000000000000 RSI: ffffffffffffffff 
RDI: ffff880036b5b000
Aug 24 03:39:16 xen3 kernel: RBP: ffffc900405ab978 R08: 0000000000000000 
R09: 00000000000171ab
Aug 24 03:39:16 xen3 kernel: R10: 0000000000000010 R11: 0000000000000000 
R12: 0000000000000000
Aug 24 03:39:16 xen3 kernel: R13: 00000000014200c0 R14: ffffea0000dad6c0 
R15: 0000160000000000
Aug 24 03:39:16 xen3 kernel: FS:  0000000000000000(0000) 
GS:ffff88003f600000(0000) knlGS:0000000000000000
Aug 24 03:39:16 xen3 kernel: CS:  e033 DS: 0000 ES: 0000 CR0: 
0000000080050033
Aug 24 03:39:16 xen3 kernel: CR2: ffff880036b5b000 CR3: 0000000037970000 
CR4: 0000000000042660
Aug 24 03:39:16 xen3 kernel: Call Trace:
Aug 24 03:39:16 xen3 kernel: decrease_reservation+0xcd/0x2f0
Aug 24 03:39:16 xen3 kernel: alloc_xenballooned_pages+0x15f/0x1c0
Aug 24 03:39:16 xen3 kernel: ? set_phys_to_machine+0x12/0x40
Aug 24 03:39:16 xen3 kernel: ? set_foreign_p2m_mapping+0x126/0x3a0
Aug 24 03:39:16 xen3 kernel: gnttab_alloc_pages+0x11/0x40
Aug 24 03:39:16 xen3 kernel: xen_blkbk_map+0x51b/0x7b0
Aug 24 03:39:16 xen3 kernel: dispatch_rw_block_io+0x3b3/0x9a0
Aug 24 03:39:16 xen3 kernel: __do_block_io_op+0x1e4/0x630
Aug 24 03:39:16 xen3 kernel: ? _raw_spin_unlock_irqrestore+0x14/0x20
Aug 24 03:39:16 xen3 kernel: ? try_to_del_timer_sync+0x3d/0x50
Aug 24 03:39:16 xen3 kernel: xen_blkif_schedule+0xc5/0x880
Aug 24 03:39:16 xen3 kernel: ? __switch_to+0x228/0x410
Aug 24 03:39:16 xen3 kernel: ? finish_task_switch+0x79/0x200
Aug 24 03:39:16 xen3 kernel: ? wait_woken+0x80/0x80
Aug 24 03:39:16 xen3 kernel: kthread+0xff/0x140
Aug 24 03:39:16 xen3 kernel: ? xen_blkif_be_int+0x30/0x30
Aug 24 03:39:16 xen3 kernel: ? kthread_create_on_node+0x40/0x40
Aug 24 03:39:16 xen3 kernel: ret_from_fork+0x1f/0x40
Aug 24 03:39:16 xen3 kernel: Code: 10 48 89 47 18 48 89 47 20 48 89 47 
28 48 89 47 30 48 89 47 38 48 8d 7f 40 75 d9 90 c3 0f 1f 80 00 00 00 00 
b9 00 10 00 00 31 c0 <f3> aa c3 90 90 90 90 90 90 0f 1f 44 00 00 48 85 
ff 0f 84 92 00
Aug 24 03:39:16 xen3 kernel: RIP: clear_page_erms+0x7/0x10 RSP: 
ffffc900405ab958
Aug 24 03:39:16 xen3 kernel: CR2: ffff880036b5b000
Aug 24 03:39:16 xen3 kernel: ---[ end trace f8c8cfe05a44d06e ]---

The domUs are still unavailable, how can I gather useful information 
with the system in the current state?
Thanks,

--
Adi Pircalabu

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-users