From owner-freebsd-current Mon Sep 21 12:28:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15495 for freebsd-current-outgoing; Mon, 21 Sep 1998 12:28:02 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15451 for ; Mon, 21 Sep 1998 12:27:59 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id MAA00467; Mon, 21 Sep 1998 12:33:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199809211933.MAA00467@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John DeBoskey cc: freebsd-current@FreeBSD.ORG Subject: Re: Hung amd on -current? In-reply-to: Your message of "Mon, 21 Sep 1998 11:08:19 EDT." <199809211508.LAA07483@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Sep 1998 12:33:00 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I have the following 'amd' process on a current system which > I cannot kill. > > 6969 root -18 0 940K 524K vmopar 0:00 0.00% 0.00% amd > > > The parent amd process is still alive and working... Basically, > all traffic to a machine 'nfssrv05' is now hung, which I believe > is due to the above process.. > > Any ideas? This is on David Greenman's (dg@freebsd.org) plate. He may want you to test various things. First make sure that you are completely up to date with -current. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message