Random kernel panic

Grouack

Member
Mar 4, 2021
14
1
8
34
hi everyone,

That's more than one year that I'm running proxmox without issue but this last time I get every week some kernel panic.it happen's during the night between midnight and 3:00AM.
I have take some screenshot but I don't arrive to get the full trace.

material :
motherboard : TRX40D8-2N2T
Ram : 4 * Kingston 32 Go ( KSM32ED8/32HC *2 + KSM32ED8/32ME *2)
Raid Card : LSI MegaRAID SAS 9261-8i ( 4 DD raid 10 and 3 raid 5 )
HDD : 7 * seagate 4To
SSD: 2 * nvme samsung 1To

Proxmox:
5 VM used for Kubernetes
3 VM used for Kubernetes ( test )
1 VM windows for remote gaming ( pcie pass through gtx 970)
1 LXC for wireguard
1 LXC for nfs ( k8s storage)
1 LXC for Adguard and DNS ( coreDns)
1 LXC for borg backup

proxmox kernel version: 5.15.85-1-pve
proxmox version : 7.3-6

What's new since I have the problem ?
I have add the two Ram KSM32ED8/32HC and I have create a new lxc for backup with borg backup.

I was thinking that it's Borg Backup which cause the problem so I have try to turn it off and nothing change.
I have seen in kernel some apparmor=DENIED concerning my wireguard lxc. I don't know if it can be the problem.
I'm testing with this lxc turned off for see if the problem happen again.

I am asking my self if it can come from the new Ram that I have add ?
If someone have a clue, it will be welcome

Thanks for your help and your reply.
 

Attachments

  • Screenshot 2023-03-06 at 23.24.17.png
    Screenshot 2023-03-06 at 23.24.17.png
    203.4 KB · Views: 11
  • Screenshot 2023-02-16 at 09.07.40.png
    Screenshot 2023-02-16 at 09.07.40.png
    749.3 KB · Views: 10
  • Screenshot 2023-03-01 at 20.42.30.png
    Screenshot 2023-03-01 at 20.42.30.png
    749 KB · Views: 9
  • Screenshot 2023-03-05 at 08.49.40.png
    Screenshot 2023-03-05 at 08.49.40.png
    763 KB · Views: 10
Thx for your reply.

where? host? VM? which?
it's the host which return the kernel panic
then remove them and try again?
I found that I was having on lxc with os disk getting full I was thinking it was the problem.
I didn't get error during more than 1 week and I supposed that it have restart today (I cannot confirm because I have some trouble with ipmi I will try to fix it).

I have contact Kingston and ask me to try only with the new ram.
I will try both during the week coming after correcting my ipmi
 
Last edited: