rpc.lockd exiting just after startup @r240811

[Pedro Giffuni]

Hello David;

Sorry to have caused you trouble.

----- Original Message -----
> From: David Wolfskill <david at catwhisker.org>
...
> 
> On Sun, Sep 23, 2012 at 06:43:49PM +0300, Konstantin Belousov wrote:
>>  ...
>>  Try to revert the r240799. If this does not help, then some digging with
>>  gdb would be needed to see why kernel dislikes the buffer. Well, the same
>>  digging would be needed even if the revert helps.
> 
> Thanks for the suggestiion.
> 
> As noted earlier, I first tried a rebuild (not specifying -DNOCLEAN);
> that proved ineffective.
> 
> I then reverted r240799, and rpc.lockd runs; I am now able to issue
> svn commands against an NFS-resident working copy.  The procedure
> I used (in case I screwed up -- or there's a less inelegant way to
> do it) was:
> 
> cd /usr/src && \
> svn diff -c 240799 >/tmp/d && \
> svn patch --reverse-diff /tmp/d
> 
> I then performed:
> 
> make -DNOCLEAN -j 4 buildworld && make -DNOCLEAN -j 4 kernel
> 
> The machine is now running:
> 
> FreeBSD freebeast.catwhisker.org 9.1-PRERELEASE FreeBSD 9.1-PRERELEASE #478 
> 240856M: Sun Sep 23 15:02:33 PDT 2012    
> root at freebeast.catwhisker.org:/usr/obj/usr/src/sys/GENERIC  i386
> 
> 
> I have subsequently seen similar symptoms on my work desktop, which
> is running stable/9 as of r240849.
> 
> 
> 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.

> 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.

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.

Pedro.