From owner-freebsd-stable@FreeBSD.ORG Sun Jul 16 09:49:36 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5341E16A4DA for ; Sun, 16 Jul 2006 09:49:36 +0000 (UTC) (envelope-from markk@knigma.org) Received: from mail.ncipher.com (mail.ncipher.com [82.108.130.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id E026043D45 for ; Sun, 16 Jul 2006 09:49:35 +0000 (GMT) (envelope-from markk@knigma.org) Received: from cromer.ncipher.com ([172.23.135.200]) by mail.ncipher.com with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 3.34 #1) id 1G23Fk-0004OA-00 for freebsd-stable@freebsd.org; Sun, 16 Jul 2006 10:49:33 +0100 Received: from lap.knigma.org (mourn.ncipher.com [172.19.133.171]) by cromer.ncipher.com (8.13.6/8.13.6) with ESMTP id k6G9nTsE033479 for ; Sun, 16 Jul 2006 10:49:30 +0100 (BST) (envelope-from markk@knigma.org) Message-ID: Date: Sun, 16 Jul 2006 10:47:58 +0100 To: freebsd-stable@freebsd.org From: Mark Knight References: <20060716084210.GL32624@deviant.kiev.zoral.com.ua> <20060716091925.GM32624@deviant.kiev.zoral.com.ua> In-Reply-To: <20060716091925.GM32624@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain;charset=us-ascii;format=flowed User-Agent: Turnpike/6.05-U () Subject: Re: 6.1 panic after approx. 49 days uptime X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jul 2006 09:49:36 -0000 In message <20060716091925.GM32624@deviant.kiev.zoral.com.ua>, Kostik Belousov writes >Thank you for the data. As I see, the problem could be worked around by >the following patch: [snip] I'll try loading this on my box later today. Thank you!! >What seems to be quite untrivial is testing. Quite! > Did you had unmount >some filesystem before that panic happen ? No; I was fast asleep! I think the panic happened while executing a cron job that does a "cvs update" in /usr/ports. The same job ran successfully every morning for the preceding 48 days. Cheers, -- Mark A. R. Knight finger: markk@knigma.org Tel: +44 7880 556751 http://www.knigma.org/