Re: kern/38669: NFS deadlock?

[Andrew Doran <ad%netbsd.org@localhost>]

The following reply was made to PR kern/38669; it has been noted by GNATS.

From: Andrew Doran <ad%netbsd.org@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: 
Subject: Re: kern/38669: NFS deadlock?
Date: Sun, 18 May 2008 15:26:32 +0100

 On Thu, May 15, 2008 at 08:35:00PM +0000, martin%duskware.de@localhost wrote:
 
 > db{0}> ps/w                                              
 >  PID        LID          COMMAND     EMUL  PRI WAIT-MSG    WAIT-CHANNEL
 >  5075         1               as   netbsd   27 tstile       11959f90   
 >  1209         1               sh   netbsd   29 tstile       11959f90
 >  1111         1               as   netbsd   27 nfsrcv       11839828
 >  4784         1               as   netbsd   28 nfsrcv       11839828
 >  5138         1              cc1   netbsd   43 netio        5bb1e60 
 >  4904         1               cc   netbsd   28 wait         12539cc0
 >  4966         1               sh   netbsd   27 wait         1265ad70
 >  5118         1              cc1   netbsd   28 nfsrcv       11839828
 >  5097         1               cc   netbsd   27 wait         1265ba40
 >  5086         1               sh   netbsd   27 wait         11d94fb0
 >  1279         1              cc1   netbsd   27 tstile       11959f90
 >  1149         1               cc   netbsd   27 wait         12538ff0
 >  5070         1               sh   netbsd   27 wait         12502d40
 >  673          1              cc1   netbsd   27 tstile       118ec1c0
 >  4880         1               cc   netbsd   27 wait         117cc2d0
 >  5048         1               sh   netbsd   27 wait         1265b000
 >  4783         1               cc   netbsd   27 wait         127c9ce0
 >  5106         1               sh   netbsd   27 wait         1265bcd0
 >  672          1               cc   netbsd   27 wait         1265aae0
 >  999          1               sh   netbsd   28 wait         12502070
 >  5099         1               cc   netbsd   27 wait         1265a330
 > 
 > Any hints how to debug this further are welcome
 
 With LOCKDEBUG, 'show lock' on the wchan will show you who holds that lock.
 t/a on LWP address of threads blocked on the locks (from ps/l), and on
 threads that hold those locks is useful to unravel the mess and find the
 root cause.
 
 Thanks,
 Andrew