fork wedging (I think)

Peter Jeremy peterjeremy at optushome.com.au
Mon Mar 5 18:34:32 UTC 2007


On 2007-Mar-05 11:36:41 +1030, Daniel O'Connor <doconnor at gsoft.com.au> wrote:
>I was incrementally dumping sysctl trees and when I got to vm it hung..
>
>eureka:~>sysctl vm
>load: 0.07  cmd: sysctl 72864 [user map] 0.00u 0.00s 0% 852k
>load: 0.07  cmd: sysctl 72864 [user map] 0.00u 0.00s 0% 852k
>load: 0.07  cmd: sysctl 72864 [user map] 0.00u 0.00s 0% 852k
>load: 0.05  cmd: sysctl 72864 [user map] 0.00u 0.00s 0% 852k
>
>I tried to reboot in another window but..
>eureka:~>reboot
>load: 0.06  cmd: csh 71159 [allproc] 0.03u 0.00s 0% 4652k

The fact that reboot eventually came back shows that the system is not
deadlocked.  "user map" and "allproc" refer to the wait channel names.
"user map" is not very helpful to me (it's the lock associated with a
class of vm maps and tracking where it's waited on is not easy).
"allproc" refers to allproc_lock.

The output from "vmstat -i" would be interesting, though it may not
respond...

How difficult would it be to build a test system somewhere where the
console was accessible?  I don't think you are going to make progress
without console access.

-- 
Peter Jeremy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070305/4d0dfe5d/attachment.pgp


More information about the freebsd-stable mailing list