From owner-freebsd-bugs Thu Mar 23 04:03:42 1995 Return-Path: bugs-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id EAA09046 for bugs-outgoing; Thu, 23 Mar 1995 04:03:42 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id EAA09039 for ; Thu, 23 Mar 1995 04:03:38 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id EAA05746; Thu, 23 Mar 1995 04:03:23 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id EAA01578; Thu, 23 Mar 1995 04:03:23 -0800 Message-Id: <199503231203.EAA01578@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: Heikki Suonsivu cc: gvrooij@mmra1.ms.philips.nl (Guido van Rooij), freebsd-bugs@freefall.cdrom.com Subject: Re: Changed information for PR kern/267 In-reply-to: Your message of "Thu, 23 Mar 95 13:00:20 +0200." <199503231100.NAA12431@zetor.clinet.fi> From: David Greenman Reply-To: davidg@Root.COM Date: Thu, 23 Mar 1995 04:03:16 -0800 Sender: bugs-owner@FreeBSD.org Precedence: bulk >Guido van Rooij writes: > > But what about his comments that when it happens, the machine seems to hang > > for a few seconds? (or am I mixing up 2 reports now?) > >If the cause is related to lost NFS packet, it could the the timeout which >would seem as a hang. This is my theory on the problem. As far as I can tell, the code doesn't take dropped packets into consideration when the diagnostic was printed - this is why it was bogus. The delay was another symptom of the dropped packet. Note that this is an NFS client problem - so you apparantly have some NFS mounted on that machine. -DG