From owner-freebsd-questions Wed Jul 30 00:00:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA14346 for questions-outgoing; Wed, 30 Jul 1997 00:00:22 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA14335 for ; Wed, 30 Jul 1997 00:00:19 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id AAA14094; Wed, 30 Jul 1997 00:01:05 -0700 (PDT) Message-Id: <199707300701.AAA14094@implode.root.com> To: bill@twwells.com (T. William Wells) cc: freebsd-questions@FreeBSD.ORG Subject: Re: can't get panic dump In-reply-to: Your message of "Wed, 30 Jul 1997 02:15:31 EDT." <5rmm46$1b5@twwells.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 30 Jul 1997 00:01:05 -0700 Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I'm running 2.2.2-RELEASE. I have 32M of RAM. I have bounce >buffers in my config. The SCSI controller is an Adaptec 1540. It >dumps 16M and then at the 16M boundary complains about DMA beyond >end of ISA and stops dumping. Any ideas? Yeah, the (lack of) bounce buffers in the dump support is an oversight. I'm not sure that there is a "clean" way to do this since higher level bounce buffers really have no business being used when the system is writing out a crash dump. I think in this case the driver dump routine should be modified to work around the 16MB limitation (yuck). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project