Forum Discussion

ahaa's avatar
ahaa
Icon for Occasional Contributor rankOccasional Contributor
4 years ago

N3000 bind pcie leads the server reboot

Recently, our two servers which installed N3000-1 and N3000-2 respectively meet the same questions. And both of the servers had been work correctly with N3000 for several months. Here are the main p...
JonWay_C_Intel's avatar
JonWay_C_Intel
Icon for Frequent Contributor rankFrequent Contributor
3 years ago
  1. when burn the sof file with JTAG， the server would reboot in the page of burning and then you need burn it again

==> This is expected. When you program the sof, you are actually reprogramming the FPGA directly (not the FPGA flash). Host will panic when it see Endpoint disappear (during the programming) from its pcie bus

  1. when bind the pcie B:D:F of the FPGA，the servers would reboot as well；

==> What driver are you binding? I dont expect binding OPAE driver will cause any reboot.

  1. when use the command of “sudo rsu bmcimg”， the servers would reboot.

==> rsu bmcimg will first mask the PCIe AER and then reprogram the FPGA from the flash. Server reboot is not expected. What bitstream are you using.

If you can provide more information such as rpm -qa | grep opae, fpgainfo fme, fpgainfo port, dmesg -T, lspci -vvv (before and after reboot). I can help to take further look into it.