From owner-freebsd-current Wed Mar 17 17:11:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id D48C0153E1 for ; Wed, 17 Mar 1999 17:11:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA34092; Wed, 17 Mar 1999 17:11:00 -0800 (PST) (envelope-from dillon) Date: Wed, 17 Mar 1999 17:11:00 -0800 (PST) From: Matthew Dillon Message-Id: <199903180111.RAA34092@apollo.backplane.com> To: Pierre Beyssac Cc: freebsd-current@freebsd.org Subject: Re: panic: vfs_busy: unexpected lock failure References: <19990315174734.A400@enst.fr> <199903152124.NAA02779@apollo.backplane.com> <19990316111040.A384@enst.fr> <199903161911.LAA11778@apollo.backplane.com> <19990316213355.A4561@enst.fr> <199903162052.MAA12300@apollo.backplane.com> <19990316221057.A382@enst.fr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Tue, Mar 16, 1999 at 12:52:32PM -0800, Matthew Dillon wrote: :> Ahhhh.. And if you make those AMD mounts normal nfs mounts it doesn't :> fry? If so, then we have a bug in AMD somewhere. : :I tried the cp several times again on a regular NFS mount, to make :sure, and no, it doesn't seem to panic. So yes, that seems to be :AMD-related. Can't it be in the vfs layer though? :-- :Pierre Beyssac pb@enst.fr It's probably AMD. I'm not really up on how AMD works... hasn't someone done some work on it recently to fix other breakages? Maybe they could look at this panic. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message