My Oracle Support Banner

Linux/Exadata: Dom-U Crash During CPU Modification On OCI Console (Doc ID 2699977.1)

Last updated on AUGUST 27, 2020

Applies to:

Oracle Cloud Infrastructure - Version N/A to N/A [Release 1.0]
Oracle Cloud Infrastructure - Exadata Cloud Service - Version N/A to N/A [Release N/A]
Linux x86-64 on Oracle Public Cloud
UEK-4.1-QU7
ORACLE LINUX 7.x
Exadata Cloud Service
Exadata Cloud at Customer

Symptoms

 In ExaCC/ExaDB environment during CPU scaling on the Dom-0 (Hot Plugging) through OCI console, Dom-U crashes.

/var/log/xen/xend.log shows errors and clearly shows Dom-U crashed

[2020-06-04 03:33:10 63783] INFO (XendDomainInfo:2103) Set VCPU count on domain <VM NAME> to 6
[2020-06-04 03:33:12 63783] WARNING (XendDomainInfo:2197) Domain has crashed:naa me=<VM NAME> id=6.
[2020-06-04 03:33:12 63783] DEBUG (XendDomainInfo:3865) XendDomainInfo.destroy:domid=6
[2020-06-04 03:33:12 63783] DEBUG (pci:1469) 0000:3b:00.1 [pxm=0]
[2020-06-04 03:33:41 63783] DEBUG (XendDomainInfo:2587) Destroying device model
[2020-06-04 03:33:41 63783] INFO (image:741) mtlhq-excc01-2.muangthai.co.th deviice model terminated

 

VMCORE log buffer output 

crash> log 
[1337395.193020] ------------[ cut here ]------------
[1337395.198768] kernel BUG at block/blk-flush.c:251!
[1337395.202831] invalid opcode: 0000 [#1] SMP
... ...
[1337395.254187] CPU: 0 PID: 11 Comm: migration/0 Tainted: G W
4.1.12-124.35.1.el6uek.x86_64 #2
... ...
[1337395.275440] RIP: 0010:[<ffffffff81301bd9>] [<ffffffff81301bd9>]
flush_end_io+0x279/0x2b0
[1337395.395137] Call Trace:
[1337395.398434] <IRQ>
[1337395.400365] [<ffffffff8130826d>] blk_mq_end_request+0x3d/0x80
[1337395.407660] [<ffffffff813092fb>] __blk_mq_complete_request+0xcb/0x110
[1337395.414448] [<ffffffff8130935c>] blk_mq_complete_request+0x1c/0x20
[1337395.421126] [<ffffffffc00708a2>] blkif_interrupt+0x9f2/0xe30
[xen_blkfront]
[1337395.429074] [<ffffffff810e2ab9>] handle_irq_event_percpu+0x99/0x200
[1337395.435605] [<ffffffff810e2c61>] handle_irq_event+0x41/0x70
[1337395.441517] [<ffffffff810e5fae>] handle_edge_irq+0x6e/0x120
[1337395.447718] [<ffffffff810e2042>] generic_handle_irq+0x32/0x50
[1337395.453596] [<ffffffff813fd418>]
__evtchn_fifo_handle_events+0x178/0x190
[1337395.461370] [<ffffffff81126e00>] ? cpu_stop_park+0x10/0x70
[1337395.467442] [<ffffffff813fd440>] evtchn_fifo_handle_events+0x10/0x20
[1337395.473944] [<ffffffff813f9e55>] __xen_evtchn_do_upcall+0x55/0xa0
[1337395.480616] [<ffffffff813fc0c4>] xen_evtchn_do_upcall+0x34/0x50
[1337395.487311] [<ffffffff816fbda6>] xen_hvm_callback_vector+0x1b6/0x1c0

 

Changes

 CPU scale down (Hot plugging) from OCI Console in ExaCC instance.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.