On 2022-11-08 15:49, Orion Poplawski wrote:
On 11/8/22 13:12, Simon Matter wrote:
Is anyone else experiencing trouble with
kernel-3.10.0-1160.80.1.el7.x86_64?
I'm seeing a kernel panics in the kvm module on one of our VM hosts
with
it.
I did notice a new libvirt update as well, but it seems to work fine
with
the
older kernel (.76.1).
Where did you get the .80.1 kernel from? I'm a bit confused because I
can
only see .76.1 on my systems.
Simon
I'm actually running Scientific Linux, which seems to be a little ahead
here.
Probably not related, but vmlinuz-4.18.0-372.32.1.el8_6.x86_64
(AlmaLinux 8.6) had a kernel panic on a Intel Xeon E5504 processor, but
works fine on Xeon E56XX processors (5620 specifically in our tests).
* Believe from kernel version, the original email is for Centos 7,
possible the same change that went into the EL8 kernel went also to EL7
Triggered right after I used virsh start to start the vm. (Caused Black
Screen, and reboot. Found this in the crashed kernel logs on
/var/crash)
Works fine on vmlinuz-4.18.0-372.26.1.el8_6.x86_64 and
vmlinuz-4.18.0-372.16.1.el8_6.x86_64
[62686.481557] [drm] fb mappable at 0xB0363000
[62686.481567] [drm] vram apper at 0xB0000000
[62686.481570] [drm] size 3145728
[62686.481573] [drm] fb depth is 24
[62686.481576] [drm] pitch is 4096
[62686.482139] fbcon: radeondrmfb (fb0) is primary device
[62686.508939] Console: switching to colour frame buffer device 128x48
[62686.511319] radeon 0000:02:00.0: [drm] fb0: radeondrmfb frame buffer
device
[62871.281318] tun: Universal TUN/TAP device driver, 1.6
[62871.282942] bb.br: port 2(vnet0) entered blocking state
[62871.282981] bb.br: port 2(vnet0) entered disabled state
[62871.283076] device vnet0 entered promiscuous mode
[62871.283310] bb.br: port 2(vnet0) entered blocking state
[62871.283345] bb.br: port 2(vnet0) entered forwarding state
[62871.453289] cgroup: cgroup: disabling cgroup2 socket matching due to
net_prio or net_cls activation
[62872.743528] int3: 0000 [#1] SMP PTI
[62872.743531] CPU: 0 PID: 75559 Comm: CPU 0/KVM Kdump: loaded Not
tainted 4.18.0-372.32.1.el8_6.x86_64 #1
[62872.743532] Hardware name: , BIOS S5500.86B.01.00.0064.050520141428
05/05/2014
[62872.743533] RIP: 0010:setno+0x9/0x10 [kvm]
[62872.743534] Code: e5 dd 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00
0f 90 c0 e9 b8 de e5 dd cc cc cc cc cc cc cc cc 0f 91 c0 e9 a8 de e5 dd
cc <cc> cc cc cc cc cc cc 0f 92 c0 e9 98 de e5 dd cc cc cc cc cc cc cc
[62872.743536] RSP: 0018:ffffaccc03de3c18 EFLAGS: 00000286
[62872.743538] RAX: 00000000ffffffff RBX: ffff88b6472e9f50 RCX:
0000000000000000
[62872.743539] RDX: ffffffffc09a3594 RSI: 0000000000000000 RDI:
ffff88b6472e9f50
[62872.743540] RBP: 0000000000000006 R08: ffff88b6f3360000 R09:
0000000000000000
[62872.743540] R10: 0000000000000230 R11: 0000000000000005 R12:
ffffffffc09dae20
[62872.743541] R13: 0000000000000000 R14: ffff88b6472e9f50 R15:
ffff88b6f3360000
[62872.743542] FS: 00007f6406a37700(0000) GS:ffff88bb97c00000(0000)
knlGS:0000000000000000
[62872.743543] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[62872.743544] CR2: 0000000000000000 CR3: 0000000170378000 CR4:
00000000000026f0
[62872.743544] Call Trace:
[62872.743545] ? x86_emulate_insn+0x1c7/0x1050 [kvm]
[62872.743546] ? x86_decode_emulated_instruction+0x5a/0x210 [kvm]
[62872.743546] ? x86_emulate_instruction+0x2f2/0x560 [kvm]
[62872.743547] ? emulator_pio_in+0x30/0x70 [kvm]
[62872.743548] ? vmx_handle_exit+0x36d/0x7a0 [kvm_intel]
[62872.743549] ? vcpu_enter_guest+0xabb/0x1730 [kvm]
[62872.743549] ? vmx_set_rflags+0xb3/0x240 [kvm_intel]
[62872.743550] ? x86_emulate_instruction+0x47b/0x560 [kvm]
[62872.743551] ? vmx_vcpu_load+0x27/0x40 [kvm_intel]
[62872.743551] ? kvm_arch_vcpu_ioctl_run+0xff/0x5f0 [kvm]
[62872.743552] ? kvm_vcpu_ioctl+0x2cc/0x640 [kvm]
[62872.743553] ? do_vfs_ioctl+0xa4/0x690
[62872.743553] ? ksys_ioctl+0x64/0xa0
[62872.743554] ? __x64_sys_ioctl+0x16/0x20
[62872.743555] ? do_syscall_64+0x5b/0x1b0
[62872.743555] ? entry_SYSCALL_64_after_hwframe+0x61/0xc6
[62872.743556] Modules linked in: vhost_net vhost vhost_iotlb tap tun
rpcsec_gss_krb5 auth_rpcgss nfsv4 dns_resolver nfs lockd grace fscache
ipmi_ssif binfmt_misc scsi_transport_iscsi 8021q garp mrp bridge stp llc
nft_chain_nat nf_nat nft_ct nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4
nft_counter nf_tables_set nf_tables nfnetlink sunrpc iTCO_wdt gpio_ich
iTCO_vendor_support intel_powerclamp coretemp kvm_intel kvm irqbypass
intel_cstate snd_hda_codec_hdmi intel_uncore snd_hda_intel
snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec pcspkr snd_hda_core
snd_hwdep snd_seq snd_seq_device ioatdma snd_pcm snd_timer i2c_i801 snd
lpc_ich soundcore acpi_ipmi ipmi_si ipmi_devintf ipmi_msghandler
i7core_edac i5500_temp acpi_cpufreq vfat fat xfs libcrc32c ext4 mbcache
jbd2 raid1 sd_mod t10_pi sg radeon mgag200 drm_ttm_helper ttm ahci
libahci drm_kms_helper libata syscopyarea sysfillrect sysimgblt
crc32c_intel fb_sys_fops drm igb dca i2c_algo_bit dm_mirror
dm_region_hash dm_log dm_mod
I have not done anything farther in investigation, and have not filed a
redmine, but thought I'd add the info I had so far.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
