On Sun, Sep 23, 2012 at 04:19:13PM -0700, Pedro Giffuni wrote: > Hello David; > > Sorry to have caused you trouble.
One of the reasons I call my laptop's kernel config file "CANARY"
is because I use it to check for danger. :-}
> ...
> > Since rpc.lockd seems OK on the systems running head, perhaps there
> > was an issue with the MFC?
> >
>
> Both should have the same issue. It does depend on what kind of load
> your -current box is running, of course.
Sure -- but in this case, it's just a matter of whether or not the
machine acts as an NFS client.
> > I'll be happy to test further -- I just need a bit of guidance from
> > time to time. :-}
> >
>
> What I can do is send you individual patches to see if we
> can narrow down the culprit. If I can avoid reverting all the
> change it will be better.
Of course; I saw that r240799 was a collection of individual changes.
> It will be a bit boring because you may have to build kernel
> and libc each time, so I would start with the most obvious
> candidates. For now just leave r240799 reverted.
OK.
Would it be OK for me to do the (usual, for me):
make -DNOCLEAN -j 4 buildworld && make -DNOCLEAN -j 4 kernel
?
(I do all the work within script(1), so we have a record.)
If you have a patch, please send it & I'll give it a try.
Alternatively, if there's a useful way to build a debugging version of
rpc.lockd & run it under a debugger, maybe I could see what's going on?
Oh -- one other thing (before I forget again): I'm using clang:
freebeast(9.1-P)[1] cat /etc/src.conf
CC=clang
CXX=clang++
CPP=clang-cpp
WITH_LIBCPLUSPLUS=yes
freebeast(9.1-P)[2]
Peace,
david
--
David H. Wolfskill da...@catwhisker.org
Depriving a girl or boy of an opportunity for education is evil.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
pgpVNuc2HaMQ3.pgp
Description: PGP signature
