From owner-freebsd-bugs Wed Jan 9 2:40: 9 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id DDFB437B41D for ; Wed, 9 Jan 2002 02:40:02 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g09Ae2L36658; Wed, 9 Jan 2002 02:40:02 -0800 (PST) (envelope-from gnats) Date: Wed, 9 Jan 2002 02:40:02 -0800 (PST) Message-Id: <200201091040.g09Ae2L36658@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Ted Mittelstaedt" Subject: RE: kern/33637: Panic: vm_page_unwire: invalid wire count: 0 Reply-To: "Ted Mittelstaedt" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/33637; it has been noted by GNATS. From: "Ted Mittelstaedt" To: "Karsten Thygesen" , Cc: Subject: RE: kern/33637: Panic: vm_page_unwire: invalid wire count: 0 Date: Wed, 9 Jan 2002 02:38:47 -0800 In summary: The server ran fine for 6 months using INN. The server is now broken running Diablo. Why is this a FreeBSD problem? If it was fine without Diablo, and crashes with Diablo, then the problem is Diablo!!!! I'd recommend that this PR be suspended until such time that the Diablo developers have had a chance to respond to this, and explain why the problem is FreeBSD when the FreeBSD server only started crashing after Diablo was run on it. Ted Mittelstaedt tedm@toybox.placo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message