Date: Tue, 16 Mar 1999 22:10:57 +0100 From: Pierre Beyssac <beyssac@enst.fr> To: Matthew Dillon <dillon@apollo.backplane.com> Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: vfs_busy: unexpected lock failure Message-ID: <19990316221057.A382@enst.fr> In-Reply-To: <199903162052.MAA12300@apollo.backplane.com>; from Matthew Dillon on Tue, Mar 16, 1999 at 12:52:32PM -0800 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>
next in thread | previous in thread | raw e-mail | index | archive | help
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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990316221057.A382>