From owner-freebsd-current Tue May 29 8:15:26 2001 Delivered-To: freebsd-current@freebsd.org Received: from melchior.cuivre.fr.eu.org (melchior.enst.fr [137.194.161.6]) by hub.freebsd.org (Postfix) with ESMTP id C274337B424 for ; Tue, 29 May 2001 08:15:22 -0700 (PDT) (envelope-from quinot@inf.enst.fr) Received: by melchior.cuivre.fr.eu.org (Postfix, from userid 11117) id 90B4A7983; Tue, 29 May 2001 17:15:18 +0200 (CEST) Date: Tue, 29 May 2001 17:15:18 +0200 From: Thomas Quinot To: current@freebsd.org Subject: rpc.lockd: kernel trap 12 with interrupts disabled Message-ID: <20010529171518.A24840@cuivre.fr.eu.org> Reply-To: Thomas Quinot Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.3.15i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the hope to check for any recent improvements with lockd, I cvsupped this morning and remade world. I now have a very strange behaviour of lockd: * rc.conf has nfs_server_enable, rpc_lockd_enable and rpc_statd_enable set to YES. * the system seems to boot correclty; rpc.lockd and rpc.statd are mentioned in the 'Starting final network daemons' phase. BUT: * ps ax shows no trace of rpc.lockd * an attempt to manually launch rpc.lockd immediately results in a hard freeze with message 'Kernel trap 12 with interrupts disabled (repeated twice). * launching rpc.lockd with truss shows that the crash occurs (shortly) after it has forked. Thomas. -- Thomas Quinot ** Département Informatique & Réseaux ** quinot@inf.enst.fr ENST // 46 rue Barrault // 75634 PARIS CEDEX 13 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message