Panic on latest stable on KVM

From: Kris von Mach <mach_at_swishmail.com>
Date: Fri, 18 Mar 2022 12:11:41 UTC
Hello,

I'm running stable/13-4c622a8f0 (from few days ago) and had a Kernel 
Panic after few days on KVM (latest Proxmox VE.)

Mar 18 07:04:39 server1 kernel: [405912] Fatal trap 12: page fault while 
in kernel mode
Mar 18 07:04:39 server1 kernel: [405912] cpuid = 22; apic id = 16
Mar 18 07:04:39 server1 kernel: [405912] fault virtual address  = 0x18
Mar 18 07:04:39 server1 kernel: [405912] fault code             = 
supervisor read data, page not present
Mar 18 07:04:39 server1 kernel: [405912] instruction pointer    = 
0x20:0xffffffff80db3c57
Mar 18 07:04:39 server1 kernel: [405912] stack pointer          = 
0x28:0xfffffe0134085690
Mar 18 07:04:39 server1 kernel: [405912] frame pointer          = 
0x28:0xfffffe0134085720
Mar 18 07:04:39 server1 kernel: [405912] code segment           = base 
0x0, limit 0xfffff, type 0x1b
Mar 18 07:04:39 server1 kernel: [405912]                        = DPL 0, 
pres 1, long 1, def32 0, gran 1
Mar 18 07:04:39 server1 kernel: [405912] processor eflags       = 
interrupt enabled, resume, IOPL = 0
Mar 18 07:04:39 server1 kernel: [405912] current process                
= 12 (irq40: virtio_pci1)
Mar 18 07:04:39 server1 kernel: [405912] trap number            = 12
Mar 18 07:04:39 server1 kernel: [405912] panic: page fault
Mar 18 07:04:39 server1 kernel: [405912] cpuid = 22
Mar 18 07:04:39 server1 kernel: [405912] time = 1647600357
Mar 18 07:04:39 server1 kernel: [405912] KDB: stack backtrace:
Mar 18 07:04:39 server1 kernel: [405912] #0 0xffffffff80c43255 at 
kdb_backtrace+0x65
Mar 18 07:04:39 server1 kernel: [405912] #1 0xffffffff80bf690f at 
vpanic+0x17f
Mar 18 07:04:39 server1 kernel: [405912] #2 0xffffffff80bf6783 at panic+0x43
Mar 18 07:04:39 server1 kernel: [405912] #3 0xffffffff8107a385 at 
trap_fatal+0x385
Mar 18 07:04:39 server1 kernel: [405912] #4 0xffffffff8107a3df at 
trap_pfault+0x4f
Mar 18 07:04:39 server1 kernel: [405912] #5 0xffffffff810520f8 at 
calltrap+0x8
Mar 18 07:04:39 server1 kernel: [405912] #6 0xffffffff80db21be at 
tcp_output+0x13be
Mar 18 07:04:39 server1 kernel: [405912] #7 0xffffffff80da99aa at 
tcp_do_segment+0x2b7a
Mar 18 07:04:39 server1 kernel: [405912] #8 0xffffffff80da60e8 at 
tcp_input_with_port+0xb78
Mar 18 07:04:39 server1 kernel: [405912] #9 0xffffffff80da6d9b at 
tcp_input+0xb
Mar 18 07:04:39 server1 kernel: [405912] #10 0xffffffff80d98647 at 
ip_input+0x157
Mar 18 07:04:39 server1 kernel: [405912] #11 0xffffffff80d26b51 at 
netisr_dispatch_src+0xb1
Mar 18 07:04:39 server1 kernel: [405912] #12 0xffffffff80d0af18 at 
ether_demux+0x138
Mar 18 07:04:39 server1 kernel: [405912] #13 0xffffffff80d0c222 at 
ether_nh_input+0x352
Mar 18 07:04:39 server1 kernel: [405912] #14 0xffffffff80d26b51 at 
netisr_dispatch_src+0xb1
Mar 18 07:04:39 server1 kernel: [405912] #15 0xffffffff80d0b339 at 
ether_input+0x69
Mar 18 07:04:39 server1 kernel: [405912] #16 0xffffffff80a3570d at 
vtnet_rxq_eof+0x71d
Mar 18 07:04:39 server1 kernel: [405912] #17 0xffffffff80a34ee6 at 
vtnet_rx_vq_process+0xa6
Mar 18 07:04:39 server1 kernel: [405912] Uptime: 4d16h45m12s


The VM is setup pretty standard/default:

qm config 186
agent: 1
balloon: 0
boot: cdn
bootdisk: scsi0
cores: 24
cpu: host,flags=+aes
machine: q35
memory: 49152
name: server1
net0: virtio=82:DA:1A:16:12:7F,bridge=vmbr0,queues=8
numa: 0
onboot: 1
ostype: l26
scsi0: local-zfs:vm-186-disk-0,discard=on,size=256G,ssd=1
scsi1: storage:vm-186-disk-0,backup=0,discard=on,size=6656G,ssd=1
scsihw: virtio-scsi-single
smbios1: uuid=2505f409-e508-4229-99f3-0d7e96ceb811
sockets: 1
tablet: 0
vmgenid: 839c5af8-b867-49f1-915a-a12d4e8e3c9c


Any ideas what could be the culprit?


__
Kris.