On 4/4/22 13:44, Jason Gunthorpe wrote: > On Mon, Apr 04, 2022 at 01:19:21PM -0500, Bob Pearson wrote: >> Back from vacation I see the following warnings when I run the pyverbs test suite. >> >> <frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.device.Context size changed, may indicate binary incompatibility. Expected 160 from C header, got 176 from PyObject >> >> <frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.qp.QPEx size changed, may indicate binary incompatibility. Expected 136 from C header, got 144 from PyObject >> >> <frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.qp.QPInitAttrEx size changed, may indicate binary incompatibility. Expected 208 from C header, got 216 from PyObject >> >> <frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.pd.PD size changed, may indicate binary incompatibility. Expected 128 from C header, got 136 from PyObject >> >> <frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.pd.ParentDomain size changed, may indicate binary incompatibility. Expected 144 from C header, got 152 from PyObject >> >> <frozen importlib._bootstrap>:228: RuntimeWarning: pyverbs.providers.mlx5.mlx5dv.Mlx5Context size changed, may indicate binary incompatibility. Expected 192 from C header, got 200 from PyObject >> >> >> It seems the headers in rdma-core and the kernel are out of sync. I just pulled fresh bits from both. > > > I don't think it has to do with kernel, that looks like a python > compilation problem. Rebuild a fresh rdma-core and make sure it is not > mixing and matching shared librarie somehow > > Jason I removed rdma-core/build and rebuilt everything. That fixed it. Thanks.
