Kernel panic on fresh install
-
lspci on host:
01:00.0 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01) 01:00.1 Ethernet controller: Intel Corporation Ethernet Controller 10G X550T (rev 01)MTU on OpnSense:
LAN interface (lan, xn1) Status up MTU 1500RoadWarriorWG0 interface (opt1, wg0) Status up MTU 16304WAN interface (wan, xn0) Status up MTU 1500site2siteWG1 interface (opt2, wg1)Status up MTU 1420xcp interface (opt3, xn2) Status up MTU 1500Unassigned interface (lo0) MTU 16384Unassigned interface (enc0) Status down MTU 1536Unassigned interface (pflog0) Status down MTU 33160Unassigned interface (ovpns1) Status up MTU 1500 -
We just released new patches that might solve this. Please update and keep us posted next time you have the problem
-
@olivierlambert
Thank you for quick fix!
I'll leave it w/o patch for couple of days to see how it works with reduced MTU on WireGuard interface before applying patch. Just in case MTU will do the trick. -
@olivierlambert Thanks ! Will try it as soon as I'm off vacation in early september.
-
@olivierlambert Server just rebooted with same error. Updates installed and waiting for next reboot
Log file almost identical:
Main differences between previous 2 days ago:
oldcode_textWARN: CPU: 4 PID: 0 Comm: swapper/4 Tainted: G O 4.19.0+1 #1new
code_textWARN: CPU: 2 PID: 0 Comm: swapper/2 Tainted: G O 4.19.0+1 #1
-
So you had the same issue after all the last updates + a "manual" reboot?
-
@olivierlambert said in Kernel panic on fresh install:
So you had the same issue after all the last updates + a "manual" reboot?
No reboot after updates. Just a mention, that in my case reducing MTU on heavy-utilised Wireguard interface didn't help.
Also these reboots completely unpredictable, sometimes during busy day, but more often during night hours where only backups can run.
-
Okay so now you have the updates really installed, we'll see if it happens
-
@olivierlambert said in Kernel panic on fresh install:
Okay so now you have the updates really installed, we'll see if it happens
Just got crash reboot again, while trying to restart a VM from XCP-center from another VM in the pool. This reboot should apply all patches from last updates.
-
Just had two consecutive crashes 15 minutes apart.
This is comparison between old crash before updates and after latest updates.
-
New crash, same message...
-
It's weird, OVS is not involved. So it might be something else
Any chance you know how to trigger it artificially? That would be really helpful to pinpoint the issue.
-
@olivierlambert
I would love to! Only thing I can say - is when I was using windows XCP-console from VM inside the pool, once starting VM caused whole system to crash with this error, another day changing VAPP config also crashed server. That is why I am trying to avoid using xcp-console during business time. I'll try to reproduce it once again and reply. -
@sasha It's worth notice that the BIOS (from 2019) is relatively old/outdated. It's recommended to update the BIOS to a more recent version.
-
@tuxen said in Kernel panic on fresh install:
@sasha It's worth notice that the BIOS (from 2019) is relatively old/outdated. It's recommended to update the BIOS to a more recent version.
Thank you for pointing out! I'll try to reach support team for this.
