From owner-freebsd-current Mon Nov 9 09:35:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27457 for freebsd-current-outgoing; Mon, 9 Nov 1998 09:35:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27447 for ; Mon, 9 Nov 1998 09:35:12 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id JAA13973 for ; Mon, 9 Nov 1998 09:34:29 -0800 Date: Mon, 9 Nov 1998 09:34:29 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: freebsd-current@FreeBSD.ORG Subject: sorry if I missed a thread here... 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 I'm having problems with 3.0-current (as of a day or so ago) where there are panics in the ffs code where a 'supervisor page not present' panic occurs (it occurred in ffs_fragextend for me). I'm not the only one this is happening to- in testing some Exabyte 8200 related fixes, dump seems to have triggered this. But I've been able to trigger this whilst doing a dump | restore operation. Any threads I should pick up on this? I'll try and isolate it a bit more closely... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message