• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

kernel panic when imaging

Scheduled Pinned Locked Moved Solved
FOG Problems
2
9
944
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.
  • T
    tlehrian
    last edited by Mar 20, 2024, 12:03 PM

    I’m trying to image a computer that we fixed (replaced several components), but halfway through the imaging process I get a kernel panic, like the following:
    IMG_1809.jpg
    Closeup of text:
    IMG_1810.jpg
    I’m not sure whether the cause is hardware or on the fog server side.

    Imaging HP Z2 G4
    Fog version 1.5.10
    bzImage and bzImage32 are both on version 6.1.63 (I originally tried the stock 5.15.93 but upgraded in case that was the issue).

    Any ideas?

    1 Reply Last reply Reply Quote 0
    • G
      george1421 Moderator @tlehrian
      last edited by george1421 Mar 20, 2024, 7:08 AM Mar 20, 2024, 1:07 PM

      @tlehrian It is surely a hardware issue. The error message is not detailed enough to point at one thing unfortunately.

      So lets start with the basics:
      What I can glean from the error message is that this computer is using firmware version 1.01. Firmware 01.08.08 Rev.A was released on 21-Nov-23. I would start by updating the firmware.

      If that doesn’t solve it then, swap memory with the working computer.

      If that doesn’t solve it then, remove all non-essential hardware cards.

      If that doesn’t solve it then download the 5.15.x version of the linux kernel for FOG. Edit: I see now that you were at 5.15 and then upgraded. So this isn’t the issue.

      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

      G T 2 Replies Last reply Mar 20, 2024, 1:18 PM Reply Quote 0
      • T
        tlehrian
        last edited by Mar 20, 2024, 12:11 PM

        I’m in the process of trying to deploy the same image on another computer with known good hardware to try to rule out any issues with the image itself.

        1 Reply Last reply Reply Quote 0
        • T
          tlehrian
          last edited by Mar 20, 2024, 12:50 PM

          A successful deploy of this image on another computer indicates that it is not an issue with the image itself or with our server.

          Any ideas what the cryptic messaging is saying? Which hardware caused this?

          Thanks
          Tim

          G 1 Reply Last reply Mar 20, 2024, 1:07 PM Reply Quote 0
          • G
            george1421 Moderator @tlehrian
            last edited by george1421 Mar 20, 2024, 7:08 AM Mar 20, 2024, 1:07 PM

            @tlehrian It is surely a hardware issue. The error message is not detailed enough to point at one thing unfortunately.

            So lets start with the basics:
            What I can glean from the error message is that this computer is using firmware version 1.01. Firmware 01.08.08 Rev.A was released on 21-Nov-23. I would start by updating the firmware.

            If that doesn’t solve it then, swap memory with the working computer.

            If that doesn’t solve it then, remove all non-essential hardware cards.

            If that doesn’t solve it then download the 5.15.x version of the linux kernel for FOG. Edit: I see now that you were at 5.15 and then upgraded. So this isn’t the issue.

            Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

            G T 2 Replies Last reply Mar 20, 2024, 1:18 PM Reply Quote 0
            • G
              george1421 Moderator @george1421
              last edited by Mar 20, 2024, 1:18 PM

              @george1421 I did find this reference:

              invalid opcode: 0000 [#1] PREEMPT SMP PTI

              PTI(Page Table Isolation) is a Spectre/Meltdown correction at the bios and kernel level. Make sure they both are up to date.

              ref: https://www.reddit.com/r/linuxquestions/comments/ajhw7e/what_can_cause_invalid_opcode_0000_1_preempt_smp/

              So lets start with update the firmware.

              Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

              T 2 Replies Last reply Mar 20, 2024, 1:25 PM Reply Quote 0
              • T
                tlehrian @george1421
                last edited by Mar 20, 2024, 1:20 PM

                @george1421 I thought I’d see if I could just install Windows on this computer without deploying an image to it. It gave me a BSOD. I did end up seeing the BIOS version was old, so I updated it to 01.08.08. Windows install BSOD again.

                Memory and NVME hardware tests all come back OK. I have already tried swapping memory.

                1 Reply Last reply Reply Quote 0
                • T
                  tlehrian @george1421
                  last edited by Mar 20, 2024, 1:25 PM

                  @george1421 So, I did update to BIOS version 01.08.08, but that still resulted in a Windows install BSOD:
                  IRQ_NOT_LESS_THAN_OR_EQUAL
                  followed by a reboot and another BSOD:
                  KMODE_EXCEPTION_NOT_HANDLED

                  Both of these point to either bad memory or device drivers. I’ll keep nosing around there.

                  G 1 Reply Last reply Mar 20, 2024, 1:42 PM Reply Quote 0
                  • T
                    tlehrian @george1421
                    last edited by Mar 20, 2024, 1:39 PM

                    @george1421 I replaced RAM with new, and now I get a BSOD: CLOCK_WATCHDOG_TIMEOUT which indicates it might be the processor.

                    This computer has been a thorn in our side - we have replaced the motherboard, and so it’s possible the processor didn’t survive the move. (or it went bad with the previous mobo).

                    I’m satisfied that this is not a FOG issue, but a hardware issue, so I think we can call this issue closed. Thanks for the help!

                    Tim

                    1 Reply Last reply Reply Quote 1
                    • [[undefined-on, T tlehrian, Mar 20, 2024, 1:41 PM]]
                    • G
                      george1421 Moderator @tlehrian
                      last edited by Mar 20, 2024, 1:42 PM

                      @tlehrian Ok so you get a BSOD with windows and under linux you get a kernel panic (same but different). So that points to a hardware issue with this computer.

                      I would swap memory with a known good computer, even if the mem test comes back OK. By moving parts hopefully the problem will move with the hardware.

                      Move other pcie attached devices like GPUs (if external) or other add in riser cards.

                      Now that you updated the bios, go in and reset the firmware settings back to factory defaults. In case there was a firmware setting change with the new firmware that corrects a known issue.

                      Sorry I can only give random ideas, but since this seems to be a hardware issues I can only make logical guesses here.

                      Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

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

                      176

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project