Arresti anomali del kernel nel server RHEL

Installazione sui seguenti componenti:

1- PowerPath versione 6.4.
2- Sistema operativo: Kernel RHEL 7.5: build Oracle di RHEL 7.5 3.10.0-862.3.2el7.x86_64.
3- VCS: VRTSvxfs-7.4.0.1200.  
4- Infoscale 7.4.
 

Configurazione:
DELL EMC SW: PowerPath per Linux 6.4
OS : RHEL 7.5
non SW DELL EMC: VRTSvxfs-7.4.0.1200.
SW non Dell EMC: Infoscale 7.4.

Il server si arresta in modo anomalo al riavvio con :

Dec 20 13:16:12 kernel "Host_name": AVVERTENZA: CPU: 5 PID: 20408 a block/blk-sysfs.c:605 blk_register_queue+0x213/0x240
Dec 20 13:16:12 kernel "Host_name": VxDMP2 sta registrando una coda
già registrata Dec 20 13:16:12 kernel "Host_name": Moduli collegati in: dmpjbod(POE) dmpap(POE) dmpaa(POE) vxspec(POE) vxio(POE) vxdmp(POE) llt(POE) rdma_cm iw_cm ib_cm ib_core bonding
vxcafs(POE) vxportal(POE) fdd(POE) amf(POE) vxfs(POE) veki(POE) sunrpc emcpdm(POE) emcpgpx(POE) emcpmpx(POE) emcp(POE) iTCO_wdt iTCO_vendor_support sb_edac intel_pow
erclamp coretemp intel_rapl iosf_mbi kvm_intel kvm irqbypass crc32_pclmul ghash_clmulni_intel aesni_intel lrw gf128mul glue_helper ablk_helper crittografato, pcspkr, hpilo, hpw
, dt, i2c_i801 lpc_ich, ioatdma, dca, ipmi_ssif, sg, ipmi_si ipmi_devintf ipmi_msghandler pcc_cpufreq, shpchp, acpi_power_meter, wmi, binfmt_misc ip_tables, xfs, sd_mod, lpfc, mgag20
, 0, i2c_algo_bit drm_kms_helper serio_raw syscopyarea, crc32c_intel, sysfillrect, sysimgblt, fb_sys_fops, ttm, nvmet_fc, drm, nvmet, bnx2x, crc_t10dif crct10dif_generic, crct10dif
, _pclmul
Dec 20 13:16:12 kernel "Host_name": nvme_fc nvme_fabrics nvme_core hpsa scsi_transport_fc i2c_core mdio ptp scsi_tgt pps_core scsi_transport_sas libcrc32c crct10dif_co
mmon dm_mirror dm_region_hash dm_log dm_mod [ultimo scaricamento: emcpioc]
Dec 20 13:16:12 kernel "Host_name": CPU: 5 PID: 20408 Comm: vxconfigd Contaminato: P OE ------------ 3.10.0-862.14.4.el7.x86_64 #1
Dec 20 13:16:12 kernel "Host_name": Nome dell'hardware: HP ProLiant BL460c Gen9, BIOS I36 12/07/2017
Dec 20 13:16:12 kernel "Host_name": Call Trace: 
Dec 20 13:16:12 Kernel "Host_name": [<ffffffffb7313754>] dump_stack+0x19/0x1b
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6c945d8>] __warn+0xd8/0x100
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6c9465f>] warn_slowpath_fmt+0x5f/0x80
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6f22483>] blk_register_queue+0x213/0x240
Dec 20 13:16:12 "Host_name" kernel: [<ffffffffb7072ba7>] ? put_device+0x17/0x20
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6f33648>] __add_disk+0x318/0x4f0
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6f33833>] add_disk+0x13/0x20
Dec 20 13:16:12 kernel "Host_name": [<ffffffffc11000d4>] dmp_register_disk+0x104/0x150 [vxdmp]
20 dic 13:16:12 kernel "Host_name": [<ffffffffc1123fb4>] dmp_reconfigure_db+0xb4/0xe0 [vxdmp]
20 dic 13:16:12 kernel "Host_name": [<ffffffffc110d1bc>] gendmpioctl+0x41c/0x940 [vxdmp]
20 dic 13:16:12 kernel "Host_name": [<ffffffffc110d8e9>] dmpioctl+0x39/0x80 [vxdmp]
20 dic 13:16:12 kernel "Host_name": [<ffffffffc1133b2a>] dmp_ioctl+0x3a/0x70 [vxdmp]
20 dic 13:16:12 kernel "Host_name": [<ffffffffb6f313b2>] blkdev_ioctl+0x272/0x9b0
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6e5dd11>] block_ioctl+0x41/0x50
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6e34100>] do_vfs_ioctl+0x360/0x550
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6e30a7d>] ? putname+0x3d/0x60
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb6e34391>] SyS_ioctl+0xa1/0xc0
Dec 20 13:16:12 kernel "Host_name": [<ffffffffb732579b>] system_call_fastpath+0x22/0x27

Questa configurazione non è supportata.

Per supportare questa particolare configurazione, è necessario inviare una RPQ.