From owner-freebsd-current Fri Oct 25 1: 6:27 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEB4D37B401 for ; Fri, 25 Oct 2002 01:06:26 -0700 (PDT) Received: from warez.scriptkiddie.org (uswest-dsl-142-38.cortland.com [209.162.142.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 27B0843E75 for ; Fri, 25 Oct 2002 01:06:26 -0700 (PDT) (envelope-from lamont@scriptkiddie.org) Received: from [192.168.69.11] (unknown [192.168.69.11]) by warez.scriptkiddie.org (Postfix) with ESMTP id 67B3662D1A; Fri, 25 Oct 2002 01:06:20 -0700 (PDT) Date: Fri, 25 Oct 2002 01:06:20 -0700 (PDT) From: Lamont Granquist To: Julian Elischer Cc: freebsd-current@freebsd.org Subject: Re: mi_switch deadlock? In-Reply-To: Message-ID: <20021025010318.U715-100000@coredump.scriptkiddie.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 okay, any idea what i'm looking for then? something is locking the whole system up... On Thu, 24 Oct 2002, Julian Elischer wrote: > On Thu, 24 Oct 2002, Lamont Granquist wrote: > > my -current box keeps freezing about every 24h. i broke into the kernel > > and forced a panic and found lots of processes stuck in mi_switch(). > > Most processes are actually in mi_switch > that's the last think a process does before it is switched away from.. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message