Bug#957468: Can this be closed?

2020-12-06 Thread Brian Smith
Can BTS #957468 be closed? -- Brian T. Smith System Fabric Works Senior Principal Engineer bsm...@systemfabricworks.com GPG Key: 0xB3C2C7B73BA3CD7F

Bug#957468: libpsm2: ftbfs with GCC-10

2020-09-08 Thread Brian Smith
I have uploaded libpsm 11.2.185-1, which addresses this bug. As requested, I'm leaving Bug #957468 open. -- Brian T. Smith System Fabric Works Senior Principal Engineer bsm...@systemfabricworks.com GPG Key: 0xB3C2C7B73BA3CD7F

Bug#910485: Confirm issue with libpsm2-2/11.2.68-1

2018-10-29 Thread Brian Smith
Hi Mehdi, On Mon, Oct 29, 2018 at 4:48 AM Mehdi Dogguy wrote: > > Sorry for not replying sooner. > > On 2018-10-20 17:54, Brian Smith wrote: > > The change is in psm2_hal.c. It is a brand new file. Reference the > > initialization loop at line 246. > > > > I

Bug#910485: Confirm issue with libpsm2-2/11.2.68-1

2018-10-20 Thread Brian Smith
28 AM Mehdi Dogguy wrote: > > On 2018-10-19 19:53, Brian Smith wrote: > > The problem occurs when the OFI psm2 provider invokes psm2_init() when > > there are no hfi1 devices present on the system. The call chain > > eventually invokes hfi1_wait_for_device() with a timeout of

Bug#910485: Confirm issue with libpsm2-2/11.2.68-1

2018-10-19 Thread Brian Smith
Sorry for my late reply on this issue. The BTS notifications were sent to spam. I'm looking into adjusting the filters. -- Brian T. Smith System Fabric Works Senior Technical Staff bsm...@systemfabricworks.com GPG Key: 0xB3C2C7B73BA3CD7F

Bug#910485: Confirm issue with libpsm2-2/11.2.68-1

2018-10-19 Thread Brian Smith
I have confirmed this behavior with libfabric1_1.6.1-5 and libpsm2_11.2.68-1. There is no existing workaround for the problem, other than downgrading libpsm2 to 10.3.58-2. The problem occurs when the OFI psm2 provider invokes psm2_init() when there are no hfi1 devices present on the system. The ca

Bug#906485: libpsm2: FTBFS in buster/sid ('%s' directive output may be truncated)

2018-08-17 Thread Brian Smith
Greetings Santiago, I have reproduced this issue and am investigating. Regarding the reproducible build FTBFS, that appears to be an issue with GNU assembler: build_path_captured_in_assembly_objects. I've been scratching my head on that one. The only potential solution that I have come up with is