Date: Tue, 16 Jan 2018 18:09:02 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 225229] hwloc broken on 11.1-RELEASE Message-ID: <bug-225229-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D225229 Bug ID: 225229 Summary: hwloc broken on 11.1-RELEASE Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: jwb@freebsd.org hwloc-info and other hwloc binaries crash on startup on 11.1-RELEASE. This problem also causes slurmd to crash. It occurs consistently on some machines and in some cases not on an identic= al machine. This issue is probably the root cause of the following openmpi issue: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D221946 1.11.1 seems to work fine. I have not tried anything between 1.11.1 and 1.11.7, but the openmpi PR below suggests 1.11.3 as the cutoff. We might w= ant to consider rolling back to that version until the root cause is determined. Compiling with -O0 helps on some systems, but not others. -O1 also helps on some systems. Upstream developer suggested a clang bug. It seems unlikely to me that a c= ode generator bug of this sort could go undetected this long, but given the unu= sual things hwloc does, it should be considered a possibility. https://github.com/open-mpi/hwloc/issues/282#issuecomment-357539630 Compiling with gcc seems to help, but that may only mean that gcc arranges variables in a different way that prevents an hwloc bug from causing critic= al corruption. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-225229-13>