From owner-freebsd-stable Tue Jan 18 4:56:48 2000 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 920A814CA6 for ; Tue, 18 Jan 2000 04:56:46 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id FAA09257; Tue, 18 Jan 2000 05:19:51 -0800 (PST) Date: Tue, 18 Jan 2000 05:19:51 -0800 From: Alfred Perlstein To: "Jeffrey J. Libman" Cc: stable@FreeBSD.ORG Subject: Re: panic: dirty bufs Message-ID: <20000118051951.B8736@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jeffrl@wantabe.com on Tue, Jan 18, 2000 at 06:51:02AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jeffrey J. Libman [000118 05:15] wrote: > one of my machines with 3.4-stable (build of Friday Jan 14 cvsup'd the > same day) just locked up with malloc errors ...couldn't even log onto the > console. > > on cntrl-alt-delete, i got: > > panic: vimvalbufs: dirty bufs > > can you tell me what this means? it means that for some reason when the kernel tried to flush a file to the underlying storage (NFS, disk, whatever) it failed, without a backtrace or your kernel config and a general idea of 'what you were doing' before the panic, it's pretty hard to pin this down on anything. please see: http://www.freebsd.org/handbook/kerneldebug.html -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message