3 Replies Latest reply on Sep 18, 2015 10:32 AM by einave

    Mellanox FlexBoot hangs system startup

    holografika

      On all boots, the MCX313A-BCBT 40GbE adapter brings up the Mellanox FlexBoot screen. However on some occasions, it hangs and does not let the boot process continue.

      In such a case, it prints:

      Mellanox FlexBoot v3.4.521

      iPXE (http://ipxe.org) 0A:00.0 003E PCI3.00 PnP PMM+_

      ..and then it just stops until a power cycle.

      Any ideas why?

        • Re: Mellanox FlexBoot hangs system startup
          einave

          Hello Peter,

           

          Can you please attach a screenshot?

          Also can you please tell whether the Mellanox HCA is enabled on the pxe boot sequence?

           

          Thanks,

          Einav

            • Re: Mellanox FlexBoot hangs system startup
              holografika

              Hi,

               

              at this point in the boot process I cannot make a screenshot yet, so attached is a photo.

              Normally, the sequence is like Mellanox Flexboot inits, Integrated Ethernet boot ROM1 inits, Integrated Ethernet boot ROM2 inits, then comes the AMI BIOS screen, and then it starts booting the first boot device.

              Please note that the Mellanox card is not used for PXE, as in this specific case we have been booting from a local SSD drive. Therefore none of the PXE entries have been activated.

              Nevertheless, this message appears first during the whole boot process.

              When it hangs, it does so at this point:

              Boot_stopped2.JPG

               

              Please note that I have tried to disable this (as we do not need it) from:

              -the FlexBoot configuration (set Option ROM -> Disabled)

              -using "flint -dev <mst device name> drom" -> this did not succeed.

               

              Then, on the official support site, I have been advised to use

              flint -d <mst device> --allow_rom_change drom

              instead, which apparently removed the ROM and the message altogether. This avoids the problem in my case, but I guess it should not stop there anyway.

               

              Best regards,

              Peter