From owner-freebsd-current@FreeBSD.ORG Tue Jun 7 00:55:59 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 B21FF16A41C for ; Tue, 7 Jun 2005 00:55:59 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from pne-smtpout2-sn2.hy.skanova.net (pne-smtpout2-sn2.hy.skanova.net [81.228.8.164]) by mx1.FreeBSD.org (Postfix) with ESMTP id 54F1343D48 for ; Tue, 7 Jun 2005 00:55:59 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: from sentinel (195.198.193.104) by pne-smtpout2-sn2.hy.skanova.net (7.2.059.6) id 429C53B60015CD3F for freebsd-current@freebsd.org; Tue, 7 Jun 2005 02:55:58 +0200 From: "Daniel Eriksson" To: "'FreeBSD Current'" Date: Tue, 7 Jun 2005 02:55:55 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527 Thread-Index: AcU/pG254VxRTrrETTuhb5uzDE3itArVR+8g In-Reply-To: Subject: RE: task queue: supervisor write, page not present X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2005 00:55:59 -0000 I wrote (almost 2 months ago): > This is the third time in 4 days that I get the following > crash on one of my servers. Since the 6.0-RELEASE process is about to start I thought I should finish this thread with a status update: After having some serious stability issues in the second half of April and first half of May, my dual CPU system has been pretty stable and very fast (as long as the VM subsystem isn't put under too much pressure) for the last couple of weeks. I don't know what made the problem go away. I currently have two issues that I will pursue in other threads eventually: 1. A simple 'dd' can make a machine grind to a halt. This is also visible during other activities where the VM subsystem (buffer cache?) is being used extensively. 2. FBSD really doesn't like it when the hardware backing a filesystem disappears (like when a disk dies, or when a ggate server accidentally gets rebooted or crashes). At first it just complains loudly, but if you don't reboot quickly chances are very good the system will panic. /Daniel Eriksson