[diagnostic] cache_lock: blocked on... extremely urgent

[Chris Turner]

Petr Janda wrote:
> [diagnostic] cache_lock: blocked on 0xd5d416e8 "cur"

Not sure if related, but last night I had a flurry of ::

  [diagnostic] cache_resolve: EAGAIN ncp 0xc1d28ab8 home

messages, but didn't report as the system is running,
for lack of a better term 1.8.0.1-optimized

(e.g release branch after the initial flurry of various
  post release bugfixes for e.g. chroot '/', but before
  the bind/linker fixes of for lack of better term "1.8.1 Pre")

and I seemed to recall some kind of namecache related changes
that I hadn't had a chance to verify in the lists..

Things happening @time of incident:

  - various nfs / rpc / amd server related startups ..
  - otherwise mostly idle