From owner-freebsd-current Tue Aug 4 11:04:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25546 for freebsd-current-outgoing; Tue, 4 Aug 1998 11:04:45 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25432 for ; Tue, 4 Aug 1998 11:04:18 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA26250; Tue, 4 Aug 1998 10:53:48 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdW26245; Tue Aug 4 17:53:47 1998 Message-ID: <35C74AA8.3F54BC7E@whistle.com> Date: Tue, 04 Aug 1998 10:53:44 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Matthew Dillon CC: Garrett Wollman , current@FreeBSD.ORG, hag@ai.mit.edu Subject: Re: Bizarre deadlock References: <199808041713.KAA02861@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :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 > (Please include original email in any response) there once was a bug where df would crash the system as it did an open on the device which did a NON-IO operation on the drive which preemted the IO operations and forgot to restart them when it finished.. this was in sd.c but I would have expected to have heard of this a lot more if this bug had resurfaced. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message