XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Kernel panic on fresh install

    Compute
    4
    26
    252
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      sasha @sasha
      last edited by sasha

      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	1500
      
      RoadWarriorWG0 interface (opt1, wg0) Status	up 
      MTU	16304
      
      WAN interface (wan, xn0) Status	up 
      MTU	1500
      
      site2siteWG1 interface (opt2, wg1)Status	up 
      MTU	1420
      
      xcp interface (opt3, xn2) Status	up 
      MTU	1500
      
      Unassigned interface (lo0) 
      MTU	16384
      
      Unassigned interface (enc0) Status	down 
      MTU	1536
      
      Unassigned interface (pflog0) Status	down 
      MTU	33160
      
      Unassigned interface (ovpns1) Status	up 
      MTU	1500
      
      1 Reply Last reply Reply Quote 0
      • olivierlambertO
        olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
        last edited by

        We just released new patches that might solve this. Please update and keep us posted next time you have the problem 🙂

        S J 3 Replies Last reply Reply Quote 1
        • S
          sasha @olivierlambert
          last edited by

          @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.

          1 Reply Last reply Reply Quote 0
          • J
            JEDIBC @olivierlambert
            last edited by

            @olivierlambert Thanks ! Will try it as soon as I'm off vacation in early september.

            1 Reply Last reply Reply Quote 0
            • S
              sasha @olivierlambert
              last edited by sasha

              @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:
              old

              code_textWARN: CPU: 4 PID: 0 Comm: swapper/4 Tainted: G           O      4.19.0+1 #1
              

              new

              code_textWARN: CPU: 2 PID: 0 Comm: swapper/2 Tainted: G           O      4.19.0+1 #1
              
              

              3a4db225-1ae4-4aa8-9d79-2a576e5efcca-image.png

              1 Reply Last reply Reply Quote 0
              • olivierlambertO
                olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                last edited by

                So you had the same issue after all the last updates + a "manual" reboot?

                S 1 Reply Last reply Reply Quote 0
                • S
                  sasha @olivierlambert
                  last edited by

                  @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.

                  1 Reply Last reply Reply Quote 0
                  • olivierlambertO
                    olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                    last edited by

                    Okay so now you have the updates really installed, we'll see if it happens 🙂

                    S 2 Replies Last reply Reply Quote 1
                    • S
                      sasha @olivierlambert
                      last edited by

                      @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.

                      1 Reply Last reply Reply Quote 1
                      • S
                        sasha @olivierlambert
                        last edited by sasha

                        @olivierlambert

                        Just had two consecutive crashes 15 minutes apart.
                        This is comparison between old crash before updates and after latest updates.
                        f19d588d-7201-46f2-badb-b51945b13f4e-image.png

                        S 1 Reply Last reply Reply Quote 1
                        • S
                          sasha @sasha
                          last edited by

                          New crash, same message...

                          1 Reply Last reply Reply Quote 0
                          • olivierlambertO
                            olivierlambert Vates 🪐 Co-Founder🦸 CEO 🧑‍💼
                            last edited by

                            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.

                            S 1 Reply Last reply Reply Quote 0
                            • S
                              sasha @olivierlambert
                              last edited by

                              @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.

                              T 1 Reply Last reply Reply Quote 1
                              • T
                                tuxen @sasha
                                last edited by

                                @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.

                                S 1 Reply Last reply Reply Quote 0
                                • S
                                  sasha @tuxen
                                  last edited by

                                  @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.

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post