Re: possible race on HEAD?

[Joe Talbott <josepht@xxxxxxxxxx>]

On Fri, May 11, 2007 at 10:46:11AM -0700, Matthew Dillon wrote:
> 
> :So I noticed that I wasn't getting my morning emails from periodic...
> :When I looked at ps, it showed that the tasks have been running for
> :hours.  Also, I noticed that some nightly cron jobs were also running.
> :One of these was cvsup...about 10 of them.  So when I did a 'killall
> :cvsup' I figured they'd go away.  No such luck.  Then I 'killall -9
> :cvsup'.  No change.  So, I investigated further by running a cvsup
> :process myself.  It hung after "Parsing supfile "/root/DragonFly-supfile"".
> :Hitting ctrl-c had no effect (other than printing ^C on my term).  Running
> :ktrace on that process left me with a blank ktrace.out.  'ps alx' looks like:
> :
> :  UID   PID  PPID CPU PRI  NI   VSZ  RSS WCHAN  STAT  TT       TIME COMMAND
> :    0  7027  1084   0 152   0  1632 1036 clock  DL+   p5    0:00.09 cvsup -L 2 /root/DragonFly-supfile
> :
> :
> :Some of the other cvsups have vnode instead of clock.
> :
> :ylem:~# uname -a
> :DragonFly ylem.theshell.com 1.9.0-DEVELOPMENT DragonFly 1.9.0-DEVELOPMENT #10: Wed May  9 18:32:59 EDT 2007     root@ylem.theshell.com:/usr/obj/usr/src/sys/YLEM  i386
> :(sources from May 9th)
> :
> :Ideas of how I can further troubleshoot?
> :
> :--Peter
> 
>     "clock" is a namecache lock.  It's possible that you found a deadlock
>     but it is also possible that a low level block device or NFS mount got
>     stuck or something of that ilk.
> 
>     Drop into the debugger, panic the system, and see if you can get a
>     kernel core dump.  If you can, upload the core and the kernel to leaf.
> 

These were the two states my cvs processes were getting stuck in as
well.

Joe