From owner-freebsd-current Wed Sep 16 23:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25749 for freebsd-current-outgoing; Wed, 16 Sep 1998 23:08:24 -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 XAA25707 for ; Wed, 16 Sep 1998 23:08:15 -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 XAA02908 for ; Wed, 16 Sep 1998 23:14:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199809170614.XAA02908@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Possble deadlock on ffsvgt or spl() leak? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Sep 1998 23:14:00 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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