From owner-freebsd-current Sat Jan 23 22:30:42 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19972 for freebsd-current-outgoing; Sat, 23 Jan 1999 22:30:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19967 for ; Sat, 23 Jan 1999 22:30:41 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id BAA99480; Sun, 24 Jan 1999 01:36:45 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Sun, 24 Jan 1999 01:36:45 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: 2Re: panic: found dirty cache page 0xf046f1c0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 24 Jan 1999, Brian Feldman wrote: > > :btw, i'm hardly 'stressing' this machine it's a k6-233+96ram and > > :i'm running X and doing a 'make release' > > : > > :Is it safe to enable crashdumps on IDE disks yet? > > : > > :-Alfred > > > > I don't know. > > > > I wasn't aware that there was a problem with crash dumps on > > ide disks. There shouldn't be. > > > > Crashdumps on IDE disks never stopped working for me. gee, that's nice to know. Brian, search the -current lists about this, there was/is some confusion in the driver about LBA. Basically, LBA would work at ALL times for the disk, except during a crash dump where it would use those addresses as CHS or something and cream one of my partitions. This lovely affected 2 seperate machines. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message