View Issue Details

IDProjectCategoryView StatusLast Update
0016399CentOS-7kernelpublic2019-09-15 04:18
Reporterkouroshez 
PriorityimmediateSeveritycrashReproducibilityalways
Status newResolutionopen 
PlatformKVM + VIRTUALIZOROSCentosOS Version7.6
Product Version7.6.1810 
Target VersionFixed in Version 
Summary0016399: crash the server everyday (kernel problem)- centos 7 + kvm + virtualizor
DescriptionHello,
we have a problem on our server, would you please help us?
every day our server restarted.
we check the log and submit a ticket to the datacenter for hardware issue but they say to us hardware is ok and also we updated bios but not useful.
I change the kernel but the problem still exists.


[root@siamak ~]# cd /var/crash/
[root@siamak crash]# ls -la
total 48
drwxr-xr-x 12 root root 4096 Sep 11 04:05 .
drwxr-xr-x 20 root root 4096 Mar 8 2019 ..
drwxr-xr-x 2 root root 4096 Sep 2 23:28 127.0.0.1-2019-09-02-23:28:43
drwxr-xr-x 2 root root 4096 Sep 4 21:35 127.0.0.1-2019-09-04-21:35:15
drwxr-xr-x 2 root root 4096 Sep 6 05:30 127.0.0.1-2019-09-06-05:30:01
drwxr-xr-x 2 root root 4096 Sep 7 18:07 127.0.0.1-2019-09-07-18:07:05
drwxr-xr-x 2 root root 4096 Sep 8 09:30 127.0.0.1-2019-09-08-09:30:14
drwxr-xr-x 2 root root 4096 Sep 8 11:48 127.0.0.1-2019-09-08-11:48:31
drwxr-xr-x 2 root root 4096 Sep 9 04:19 127.0.0.1-2019-09-09-04:19:04
drwxr-xr-x 2 root root 4096 Sep 9 14:19 127.0.0.1-2019-09-09-14:19:19
drwxr-xr-x 2 root root 4096 Sep 10 10:45 127.0.0.1-2019-09-10-10:45:27
drwxr-xr-x 2 root root 4096 Sep 11 04:05 127.0.0.1-2019-09-11-04:05:43
[root@siamak crash]#


[root@siamak crash]# cd 127.0.0.1-2019-09-11-04\:05\:43/
[root@siamak 127.0.0.1-2019-09-11-04:05:43]# ls
vmcore vmcore-dmesg.txt
[root@siamak 127.0.0.1-2019-09-11-04:05:43]# ls -la
total 263160
drwxr-xr-x 2 root root 4096 Sep 11 04:05 .
drwxr-xr-x 12 root root 4096 Sep 11 04:05 ..
-rw------- 1 root root 269389947 Sep 11 04:05 vmcore
-rw-r--r-- 1 root root 67391 Sep 11 04:05 vmcore-dmesg.txt
[root@siamak 127.0.0.1-2019-09-11-04:05:43]#


0.000000] microcode: microcode updated early to revision 0xb4, date = 2019-04-01
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 3.10.0-957.5.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC) ) #1 SMP Fri Feb 1 14:54:57 UTC 2019
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.10.0-957.5.1.el7.x86_64 root=UUID=153ec4d8-5d72-4a2c-b96d-47de89b113fc ro biosdevname=0 crashkernel=auto nomodeset rd.auto=1 consoleblank=0 LANG=en_US$
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000003613bfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003613c000-0x000000003613cfff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000003613d000-0x000000003613dfff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003613e000-0x000000003abd3fff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003abd4000-0x000000003b045fff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003b046000-0x000000003b1bcfff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003b1bd000-0x000000003b5a5fff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x000000003b5a6000-0x000000003befefff] reserved
[ 0.000000] BIOS-e820: [mem 0x000000003beff000-0x000000003befffff] usable
[ 0.000000] BIOS-e820: [mem 0x000000003bf00000-0x000000003f7fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000010bf7fffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.8 present.
[ 0.000000] DMI: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x10bf800 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: write-back
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0080000000 mask 7F80000000 uncachable
[ 0.000000] 1 base 0040000000 mask 7FC0000000 uncachable
[ 0.000000] 2 base 003E000000 mask 7FFE000000 uncachable
[ 0.000000] 3 base 003D000000 mask 7FFF000000 uncachable
[ 0.000000] 4 disabled
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ 0.000000] 7 disabled
[ 0.000000] 8 disabled
[ 0.000000] 9 disabled
[ 0.000000] PAT configuration [0-7]: WB WC UC- UC WB WP UC- UC
[ 0.000000] e820: last_pfn = 0x3bf00 max_arch_pfn = 0x400000000
[ 0.000000] found SMP MP-table at [mem 0x000fcdd0-0x000fcddf] mapped at [ffffffffff200dd0]
[ 0.000000] Base memory trampoline at [ffff93df40098000] 98000 size 24576
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] BRK [0x74f652000, 0x74f652fff] PGTABLE
[ 0.000000] BRK [0x74f653000, 0x74f653fff] PGTABLE
[ 0.000000] BRK [0x74f654000, 0x74f654fff] PGTABLE
[ 0.000000] BRK [0x74f655000, 0x74f655fff] PGTABLE

logs attached.

[root@siamak ~]# uname -a
Linux siamak 3.10.0-957.5.1.el7.x86_64 #1 SMP Fri Feb 1 14:54:57 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[root@siamak ~]# rpm -q kernel
kernel-3.10.0-957.27.2.el7.x86_64
kernel-3.10.0-957.5.1.el7.x86_64
[root@siamak ~]#


we check the both kernel but the problem still exist.
datacenter checked rams and another hardware and everythings is ok.
virtualizor supports says to us every thins is ok.
TagsNo tags attached.
abrt_hash
URL

Activities

kouroshez

kouroshez

2019-09-15 04:18

reporter  

vmcore-dmesg.txt (777,061 bytes)

Issue History

Date Modified Username Field Change
2019-09-15 04:18 kouroshez New Issue
2019-09-15 04:18 kouroshez File Added: vmcore-dmesg.txt