From owner-freebsd-current Thu Sep 17 12:04:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05710 for freebsd-current-outgoing; Thu, 17 Sep 1998 12:04:36 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05698 for ; Thu, 17 Sep 1998 12:04:27 -0700 (PDT) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA04117; Thu, 17 Sep 1998 11:52:35 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdNA4106; Thu Sep 17 18:52:28 1998 Date: Thu, 17 Sep 1998 11:52:22 -0700 (PDT) From: Julian Elischer To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: Possble deadlock on ffsvgt or spl() leak? In-Reply-To: <199809170614.XAA02908@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG soft updates involved? On Wed, 16 Sep 1998, Mike Smith wrote: > > Trying to build a 3.0 snapshot for public consumption here, we're > seeing the system come to a relative halt (no user processes running, > still possible to break into DDB). > > There's a collection of processes sleeping on 'ffsvgt', and the kernel > is running in the idle loop (breaking to DDB interrupts _default_halt). > > This is on a reasonably current SMP kernel (midday yesterday). > _cpl looked a little worrying (0xc300009a), which is why I was > wondering about a possible spl() leak. > > Anyone have any bright ideas? > > -- > \\ 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message