post ino64: lockd no runs?

David Wolfskill david at catwhisker.org
Sun Jun 11 20:51:28 UTC 2017


On Sun, Jun 11, 2017 at 09:58:30PM +0300, Konstantin Belousov wrote:
> On Sun, Jun 11, 2017 at 11:12:25AM -0700, David Wolfskill wrote:
> >   2811 rpc.lockd CALL  nlm_syscall(0,0x1e,0x4,0x801015040)
> >   2811 rpc.lockd RET   nlm_syscall -1 errno 14 Bad address
> 
> If you revert r319614 on stable/11, does the problem go away ?
> ....

As it happens, apparently so.

I was able to reproduce the symptom on my build machine:

freebeast(11.1)[1] uname -a && service lockd status 
FreeBSD freebeast.catwhisker.org 11.1-BETA1 FreeBSD 11.1-BETA1 #366  r319823M/319823:1100514: Sun Jun 11 03:55:49 PDT 2017     root at freebeast.catwhisker.org:/co
mmon/S1/obj/usr/src/sys/GENERIC  amd64
lockd is not running.
freebeast(11.1)[2] 

I then "cloned" slice 1 to slice 3, and on slice 3's /usr/src, I
used "svn diff" and "svn patch --reverse-diff" to effectively revert
r319614, then rebooted from slice 3, did a normal src-based update;
rebooted, and:

freebeast(11.1)[1] uname -a && service lockd status
FreeBSD freebeast.catwhisker.org 11.1-BETA1 FreeBSD 11.1-BETA1 #367  r319823M/319823:1100514: Sun Jun 11 13:31:49 PDT 2017     root at freebeast.catwhisker.org:/co
mmon/S3/obj/usr/src/sys/GENERIC  amd64
lockd is running as pid 600.
freebeast(11.1)[2]


If there's a patch someone would like me to try that's a bit more
involved than just reverting r319614, I'm up for it.

Peace,
david
-- 
David H. Wolfskill				david at catwhisker.org
Looking forward to telling Mr. Trump: "You're fired!"

See http://www.catwhisker.org/~david/publickey.gpg for my public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 603 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20170611/64c30172/attachment.sig>


More information about the freebsd-stable mailing list