Date: Thu, 10 Mar 2016 07:16:05 +0900 From: Brendan Sechter <sgeos@hotmail.com> To: Florian Ermisch <florian.ermisch@alumni.tu-berlin.de>, Eric van Gyzen <eric@vangyzen.net>, "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: RE: limits: setrlimit umtxp: Invalid argument Message-ID: <BAY182-W84CAC31FE8B2A30DD6B134A2B30@phx.gbl> In-Reply-To: <FE5F919D-8371-488E-BC3C-841962ACED1B@alumni.tu-berlin.de> References: <BAY182-W54B92C21428A30D70FA5C9A2B30@phx.gbl>, <56E04873.9050200@vangyzen.net>, <FE5F919D-8371-488E-BC3C-841962ACED1B@alumni.tu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
> Subject: Re: limits: setrlimit umtxp: Invalid argument=0A= > From: florian.ermisch@alumni.tu-berlin.de=0A= > Date: Wed=2C 9 Mar 2016 18:45:37 +0100=0A= > To: eric@vangyzen.net=3B sgeos@hotmail.com=3B freebsd-current@freebsd.org= =0A= >=0A= > Am 9. M=E4rz 2016 16:59:47 MEZ=2C schrieb Eric van Gyzen <eric@vangyzen.n= et>:=0A= >> On 03/09/2016 09:49=2C Brendan Sechter wrote:=0A= >>> I am running an 11.0-CURRENT VM.=0A= >>> After recently updating=2C the following appears on startup and=0A= >>> dhclient fails to start.=0A= >>>=0A= >>> Starting dhclient.=0A= >>> limits: setrlimit umtxp: Invalid argument=0A= >>> /etc/rc.d/dhclient: WARNING: failed to start dhclient=0A= >>>=0A= >>> Similar messages appear for the following.=0A= >>>=0A= >>> devd pflog syslogd ntpd powerd sshd sendmail_submit=0A= >>> sendmail_msp_queue cron=0A= >>>=0A= >>> Reverting to the previous kernel did not resolve the issue.=0A= >>> I can manually start dhclient and ntp=2C but not sshd.=0A= >>>=0A= >>> I do not trust that my uname information is being updated with=0A= >>> with build=2C but here it is.=0A= >>>=0A= >>> $ uname -vm=0A= >>> FreeBSD 11.0-CURRENT #0 r287598: Thu Sep 10 14:45:48 JST 2015=0A= >>> root@:/usr/obj/usr/src/sys/MIRAGE_KERNEL amd64=0A= >>=0A= >> This information comes directly from the running kernel=2C so it looks= =0A= >> like your kernel is not getting updated. This seems consistent=0A= >> with the above error messages=2C although I haven't tested this=0A= >> case. The userland tools are aware of the newly added umtxp=0A= >> limit=2C but the kernel is not aware.=0A= >>=0A= >> Eric=0A= >=0A= > I got this problem on my laptop=2C too. I somehow managed not to=0A= > install the kernel during a recent update so my userland is slightly=0A= > newer than my 11-CURRENT r292755 kernel (and also forgot to=0A= > make proper ZFS snapshots=85).=0A= >=0A= > While I can build a newer kernel but when I boot i.e. r296556=0A= > `zfs(8)' coredumps and I can't mount anything but the rootfs=85=0A= > I guess I need to get kernel & userland back in sync to fix this.=0A= >=0A= > I will try to build the userland matching my kernel first as=0A= > I know its revision from `uname -a`.=0A= > If anyone has a better approach or tips=2C please let me know.=0A= =0A= My userland was up to date. =A0This is what I did to get the kernel=0A= in sync enough to resolve the issue.=0A= =0A= svn up /usr/src # omit if want to use the exact same version as world=0A= cd /usr/src=0A= make buildkernel KERNCONF=3DMYKERNEL=0A= make installkernel KERNCONF=3DMYKERNEL=0A= =0A= I found a problem with my kernel configuration in the process.=0A= The plan is to rebuild everything after the configuration issue is=0A= sorted out. =A0You may wish to use GENERIC just to get things up=0A= and running again.=0A= =0A= Regards=2C=0A= -Brendan =
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY182-W84CAC31FE8B2A30DD6B134A2B30>