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

Kernel Panic

Scheduled Pinned Locked Moved
Hardware Compatibility
3
20
1.9k
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.
  • G
    george1421 Moderator @ricardomartins
    last edited by Jun 30, 2020, 3:19 PM

    @ricardomartins said in Kernel Panic:

    didnt solve. Do I need to have specific files in server for it to work ?

    Well over time it appears that the linux kernel is having an issue with those specific computers. In other cases disabling acpi resolved the issue. Other times we had the FOG Admins make sure the bios was updated on these computers.

    For testing go to the URL that I provided before with the kernels. Download 4.15.2 that was listed in the ref post. You only need the 64 bit version for this test. Rename the 64 bit version to bzImage4152 and move that file to /var/www/html/fog/service/ipxe directory. Make sure the case is correct. In this test we will NOT overwrite the existing kernel for FOG 1.5.9RC2. Now go back into the host settings where you manually defined this host. Set the “Host Kernel” field to bzImage4152 leave the “Host Kernel Arguments” with noapci=1 and then try to pxe boot this computer.

    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!

    R 1 Reply Last reply Jun 30, 2020, 3:38 PM Reply Quote 0
    • R
      ricardomartins @george1421
      last edited by Jun 30, 2020, 3:38 PM

      @george1421 I followed everything you said but it is still trying to kill himself.

      Very similar error but a little bit different

      G 1 Reply Last reply Jun 30, 2020, 5:02 PM Reply Quote 0
      • G
        george1421 Moderator @ricardomartins
        last edited by Jun 30, 2020, 5:02 PM

        @ricardomartins Are you sure you saw that bzImage4152 was transferred to the target computer, it would be just after boot.php is called then it should transfer bzImage4152 and then init.xz to the target computer.

        Back on the kernel parameters lets try this one acpi=off instead of noacpi=1 They “should” do the same thing.

        Also is this hardware at the latest bios version supported by the hardware?

        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!

        R 1 Reply Last reply Jul 1, 2020, 9:08 AM Reply Quote 0
        • R
          ricardomartins @george1421
          last edited by Jul 1, 2020, 9:08 AM

          Hello @george1421 !

          I updated the bios version from 1.53 to 1.60 (newer version in HP website) and tried to run the deply again with acpi=off.
          It give the exact same error and I confirmed that it uses bzImage4152

          bz.jpg

          G 1 Reply Last reply Jul 1, 2020, 11:29 AM Reply Quote 0
          • R
            ricardomartins
            last edited by Jul 1, 2020, 10:33 AM

            Maybe is missing something in my host config

            HOST.PNG

            1 Reply Last reply Reply Quote 0
            • G
              george1421 Moderator @ricardomartins
              last edited by Jul 1, 2020, 11:29 AM

              @ricardomartins So in this case you are not getting the kernel panic, its just not starting linux? Your host configuration looks good.

              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!

              R 1 Reply Last reply Jul 1, 2020, 11:50 AM Reply Quote 0
              • R
                ricardomartins @george1421
                last edited by Jul 1, 2020, 11:50 AM

                @george1421 after loading correctly the bzImage 4152 and init.xz it goes to the error again (kernel panic error )

                G 1 Reply Last reply Jul 1, 2020, 12:04 PM Reply Quote 0
                • S
                  Single
                  last edited by Jul 1, 2020, 12:03 PM

                  A nickle (may be helpful)
                  https://stackoverflow.com/questions/50115956/kernel-panic-not-syncingattempted-to-kill-init

                  Something wicked is happening to your init image. Mb try to replace it?

                  G 1 Reply Last reply Jul 1, 2020, 12:08 PM Reply Quote 0
                  • G
                    george1421 Moderator @ricardomartins
                    last edited by Jul 1, 2020, 12:04 PM

                    @ricardomartins Does it do this on all DCS5800 models or just this single computer. If its just this single computer there may be a hardware issue with this computer like a bad RAM chip. I don’t understand why the acpi off is not fixing the issue because others have reported it works.

                    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
                    • G
                      george1421 Moderator @Single
                      last edited by Jul 1, 2020, 12:08 PM

                      @Single said in Kernel Panic:

                      A nickle (may be helpful)

                      I don’t think that one fits here since we are not doing nfs at this time. What we really need to see is the actual error that happened just before the stack dump that we see on the screen. Possibly if you can get a slow mode video of the kernel booting process we can see what the actual error message is. I’m not sure what we can do about it because its in the linux kernel but it might give us an idea where to look.

                      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
                        20/20
                        Last post

                      157

                      Online

                      12.1k

                      Users

                      17.3k

                      Topics

                      155.3k

                      Posts
                      Copyright © 2012-2024 FOG Project