From owner-freebsd-current  Tue Aug  4 10:14:02 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id KAA13364
          for freebsd-current-outgoing; Tue, 4 Aug 1998 10:14:02 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13319
          for <current@FreeBSD.ORG>; Tue, 4 Aug 1998 10:13:49 -0700 (PDT)
          (envelope-from dillon@backplane.com)
Received: (dillon@localhost) by apollo.backplane.com (8.8.8/8.6.5) id KAA02861; Tue, 4 Aug 1998 10:13:30 -0700 (PDT)
Date: Tue, 4 Aug 1998 10:13:30 -0700 (PDT)
From: Matthew Dillon <dillon@backplane.com>
Message-Id: <199808041713.KAA02861@apollo.backplane.com>
To: Julian Elischer <julian@whistle.com>
Cc: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>, current@FreeBSD.ORG,
        hag@ai.mit.edu
Subject: Re: Bizarre deadlock
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


:was there any 'mount' operation going on?
:there are some suspicious paths related to locking mounts and the root vn 
:
:julian
:

    I dunno re: garrett's box, but my test box running -current/SMP/SoftUpdates
    locked up in a similar manner two weeks ago.  Definitely no mount op going
    on.  I didn't get a dump, unfortunately.  The lockup occured when I tried 
    to do a 'df'.  That is, everything was fine until I did the 'df', and 
    that caused the machine to lockup (or perhaps the sync df does caused
    the machine to lockup).

							-Matt

    Matthew Dillon  Engineering, HiWay Technologies, Inc. & BEST Internet 
                    Communications
    <dillon@backplane.com> (Please include original email in any response)    


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message