ports/82730: SMP + portupgrade on -CURRENT = hung machine

[Adam Kirchhoff]

>Number:         82730
>Category:       ports
>Synopsis:       SMP + portupgrade on -CURRENT = hung machine
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Jun 28 11:40:20 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator:     Adam Kirchhoff
>Release:        FreeBSD 6.0-CURRENT i386
>Organization:
>Environment:
FreeBSD memory.visualtech.com 6.0-CURRENT FreeBSD 6.0-CURRENT #3: Tue Jun 28 03:04:52 EDT 2005     root@:/usr/obj/usr/src/sys/MEMORY  i386
>Description:
I have three machines which I just upgraded from 5.4 to -CURRENT.  They are two SMP desktops and a UP laptop.

After building world and installing, I started to run portupgrade on my systems.  On the laptop, everything has been running smoothly..  On both SMP systems, portupgrade hangs.  top shows the ruby18 process stuck in the *vnode state.  On one machine, which I can't physically access, it's been this way for hours.  I can't ssh into this machine, and only have access to sessions that were connected before the hang.  On my home machine (which I can physically access), I've been able to log in on the virtual consoles and reboot when this happens (though it's not ever able to sync all buffers and cleanly unmount /).  It's now happened with 5 or 6 consecutive attempts at portupgrade on this machine.  The most recent time this happened, on a hunch, I built a UP kernel, rebooted, and tried portupgrade again.  It ran all night (eight hours) without hanging.
>How-To-Repeat:

Run "portupgrade -r -a" on an SMP kernel (and SMP system) on -CURRENT.      
>Fix:
      
>Release-Note:
>Audit-Trail:
>Unformatted: