From owner-freebsd-hackers Sun Oct 12 17:31:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01250 for hackers-outgoing; Sun, 12 Oct 1997 17:31:37 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01245 for ; Sun, 12 Oct 1997 17:31:35 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id RAA03265; Sun, 12 Oct 1997 17:31:19 -0700 (MST) From: Terry Lambert Message-Id: <199710130031.RAA03265@usr05.primenet.com> Subject: Re: Problem with 2.2.2-RELEASE machine To: julian@whistle.com (Julian Elischer) Date: Mon, 13 Oct 1997 00:31:19 +0000 (GMT) Cc: khetan@iafrica.com, hackers@FreeBSD.ORG In-Reply-To: from "Julian Elischer" at Oct 12, 97 03:17:17 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Audience upgraded to hackers.. > > re: a panic at 0xf01b0384B > it's in nortqr.. > This is excactly the problem I see in 2.2 based machines. > we have MANY in the field and occasioanally get hit by this. > > > someohow the vm system manages to confuse things > to the extent that the same process is on both the run queue > and a sleep queue. I think this can happen in an M_WAIT allocation in some circumstances (the vnode allocation code that is the antecedent to vclean is one of them). I'm sorry, but I don't have any specific recommendations for the trace you provided. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.