From owner-freebsd-current@FreeBSD.ORG Thu Feb 19 17:36:00 2004 Return-Path: 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 D8B6416A4CE; Thu, 19 Feb 2004 17:36:00 -0800 (PST) Received: from angmar.mel.vet.com.au (angmar.mel.vet.com.au [203.39.245.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F61E43D1F; Thu, 19 Feb 2004 17:36:00 -0800 (PST) (envelope-from odela01@ca.com) Received: from nargothrond.ca.com (nargothrond.ca.com [155.35.178.10]) by angmar.mel.vet.com.au (Postfix) with ESMTP id C7D5014F317; Fri, 20 Feb 2004 12:38:10 +1100 (EST) Received: from [155.35.171.93] (anduril-udp02399829uds.ca.com [155.35.171.93]) by nargothrond.ca.com with esmtp; Fri, 20 Feb 2004 12:35:54 +1100 Mime-Version: 1.0 (Apple Message framework v612) In-Reply-To: <4032CC86.7000800@freebsd.org> References: <20040217102453.V59439@lorax.ldc.upenn.edu> <4032A691.3020006@freebsd.org> <4032CC86.7000800@freebsd.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <1F529EE7-6345-11D8-9307-000A95DBB47C@ca.com> Content-Transfer-Encoding: 7bit From: Lachlan O'Dea Date: Fri, 20 Feb 2004 12:35:53 +1100 To: freebsd-current@freebsd.org, Scott Long X-Pgp-Agent: GPGMail 1.0 (v30, 10.3) X-Mailer: Apple Mail (2.612) Subject: Re: kernel panic after 5.2 RELEASE --> 5.2.1, DELL PE2650, SCSI X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Fri, 20 Feb 2004 01:36:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18 Feb 2004, at 13:23, Scott Long wrote: > Lachlan O'Dea wrote: > >> I managed to observe the system in top the second time this happened. >> One after another, each process freezes forever in getblk. Kind of >> scary to watch :-). >> With 5.2-RELEASE, I was seeing the blocked processes, but I don't >> recall seeing all of that console output before. I haven't actually >> seen experienced any problems with 5.2-RELEASE for a while, I just >> have to avoid long-running find(1) processes. (E.g. put >> daily_status_security_enable="NO" in periodic.conf). > > The same problem exists in 5.2. I thought that I had fixed it, but > apparently not. I put your aacvar.h patch in yesterday (so I'm running the latest 5.2.1-RC2), and since then have experienced zero problems! The overnight security check ran flawlessly for the first time since... well, ever. Thanks so much. - -- Lachlan O'Dea Computer Associates Senior Software Engineer tel: +61 3 8416 5627 fax: +61 3 8416 5810 mobile: +61 412 390 650 odela01@ca.com Relax and enjoy your shoes! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (Darwin) iD8DBQFANWR5oBZahcUBONoRAniuAJ9nABj57k3XV0nbqxee8N/xWCLyBgCg1jFu zWr7jOC06tjjCJIbMouuR3M= =L+QO -----END PGP SIGNATURE-----