Hi,

> Greetings.  FWIW, I was about to send a similar note to the SL list when
> I read your note.  I think the discussion to this point has nailed the
> issue, but, for the record, here's what we see:
> 
>     Aug 29 15:18:24 client-sys kernel: lockd: server xxxxxx not
>     responding, still trying
> 
> While on the server we see:
> 
>     root   3569  0.0  0.0    0     0 ?    D   Aug27   0:00 [lockd]
> 
> The process is not a user-land process and evidently cannot be stopped
> except by killing the kernel, i.e., rebooting.
Yep, the lockd hungs somewhere in a semaphore.

> The user-level ramification is that some, but maybe not all (?),
Only locking do not work ;-))
But that blocks some applications, and definitly blocks logins under KDE.

> And, yes, it WOULD be sweet if somebody could patch this.
Yep.

Sincerly,
Klaus