On Tue, Jan 02, 2018 at 07:58:08AM -0700, Jason Gunthorpe wrote: > On Tue, Jan 02, 2018 at 03:41:25PM +0800, Honggang LI wrote: > > On Mon, Jan 01, 2018 at 12:19:50PM -0700, Jason Gunthorpe wrote: > > > > Yes, it is systemd-219-51.el7.x86_64 error code. > > > > > > > > > Is this because of PrivateNetwork=yes or something similar? > > > > > > > > How to test or verify this? > > > > > > Remove all the sandboxing thing and see if it starts working. > > > > "PrivateNetwork=yes/no" is not the root cause of this issue. > > > > > > > > Add them back in until you find the one that breaks it. > > > > I had confirmed this is a systemd issue with Fedora-27 distro. F27 > > works as higher version systemd is running. > > > > Please drop this patch. > > Very mysterious then, any idea what is going on? sorry but no. I'm done with this issue, unless it bites me again. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
