From owner-freebsd-current Thu Mar 18 22: 0: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 1A31514BEF for ; Thu, 18 Mar 1999 22:00:03 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id WAA23916; Thu, 18 Mar 1999 22:59:35 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199903190559.WAA23916@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: mishania@demos.net (Mikhail A. Sokolov), current@FreeBSD.ORG Subject: Re: repeated ufs_dirbad() panics on 4.0-c In-reply-to: Your message of "Tue, 16 Mar 1999 13:36:40 MST." <199903162036.NAA27623@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Mar 1999 22:50:33 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> # Are you *sure* you're running -current as of today? Justin put code in to >> # silence Illegal request error messages from the sync cache command. These messages, since they are occurring only during a panic, are caused by the code in dashutdown(). I didn't modify this code in my last checkin, but cannot see why it would not properly prevent the messages from being displayed. Perhaps Mikhail would be willing to instrument the code and determine why it doesn't work properly? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message