[OMPI users] hwloc: Topology became empty, aborting!
On a VPS I tested my build of hwloc-2.9.2 by running lstopo: ./lstopo hwloc: Topology became empty, aborting! Segmentation fault On a GCP n1-standard-2 a similar build (GCC 12.2 vs. 13.2) seemed to work: ./lstopo hwloc/nvml: Failed to initialize with nvmlInit(): Driver Not Loaded Machine (7430MB total) Package L#0 NUMANode L#0 (P#0 7430MB) L3 L#0 (45MB) + L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0 PU L#0 (P#0) PU L#1 (P#1) HostBridge PCI 00:03.0 (Other) Block(Disk) "sda" PCI 00:04.0 (Ethernet) Net "ens4" PCI 00:05.0 (Other) What steps should I take to find the cause of the failure on the VPS? I suspect an OS issue because in the past my builds of OpenMPI worked.
Re: [OMPI users] hwloc: Topology became empty, aborting!
Hello This is a hwloc issue, the mailing list is hwloc-us...@lists.open-mpi.org (please update the CCed address if you reply to this message). Try building with --enable-debug to get a lot of debug messages in lstopo. Or run "hwloc-gather-topology foo" and send the resulting foo.tar.gz (you will likely get some error messages but you may ignore them). Or better, put all this in https://github.com/open-mpi/hwloc/issues/new Brice Le 01/08/2023 à 16:17, Max R. Dechantsreiter via users a écrit : On a VPS I tested my build of hwloc-2.9.2 by running lstopo: ./lstopo hwloc: Topology became empty, aborting! Segmentation fault On a GCP n1-standard-2 a similar build (GCC 12.2 vs. 13.2) seemed to work: ./lstopo hwloc/nvml: Failed to initialize with nvmlInit(): Driver Not Loaded Machine (7430MB total) Package L#0 NUMANode L#0 (P#0 7430MB) L3 L#0 (45MB) + L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + Core L#0 PU L#0 (P#0) PU L#1 (P#1) HostBridge PCI 00:03.0 (Other) Block(Disk) "sda" PCI 00:04.0 (Ethernet) Net "ens4" PCI 00:05.0 (Other) What steps should I take to find the cause of the failure on the VPS? I suspect an OS issue because in the past my builds of OpenMPI worked. OpenPGP_signature Description: OpenPGP digital signature
Re: [OMPI users] hwloc: Topology became empty, aborting!
Hi Brice, Thank you - I was unaware there was an hwloc-users list. Regards, Max --- On Tue, Aug 01, 2023 at 05:11:29PM +0200, Brice Goglin wrote: > Hello > > This is a hwloc issue, the mailing list is hwloc-us...@lists.open-mpi.org > (please update the CCed address if you reply to this message). > > Try building with --enable-debug to get a lot of debug messages in lstopo. > > Or run "hwloc-gather-topology foo" and send the resulting foo.tar.gz (you > will likely get some error messages but you may ignore them). > > Or better, put all this in https://github.com/open-mpi/hwloc/issues/new > > Brice > > > > Le 01/08/2023 à 16:17, Max R. Dechantsreiter via users a écrit : > > On a VPS I tested my build of hwloc-2.9.2 by running lstopo: > > > > ./lstopo > > hwloc: Topology became empty, aborting! > > Segmentation fault > > > > On a GCP n1-standard-2 a similar build (GCC 12.2 vs. 13.2) seemed to work: > > > > ./lstopo > > hwloc/nvml: Failed to initialize with nvmlInit(): Driver Not Loaded > > Machine (7430MB total) > >Package L#0 > > NUMANode L#0 (P#0 7430MB) > > L3 L#0 (45MB) + L2 L#0 (256KB) + L1d L#0 (32KB) + L1i L#0 (32KB) + > > Core L#0 > >PU L#0 (P#0) > >PU L#1 (P#1) > >HostBridge > > PCI 00:03.0 (Other) > >Block(Disk) "sda" > > PCI 00:04.0 (Ethernet) > >Net "ens4" > > PCI 00:05.0 (Other) > > > > What steps should I take to find the cause of the failure on the VPS? > > I suspect an OS issue because in the past my builds of OpenMPI worked. > >
