From owner-freebsd-hackers Mon Mar 3 12:32:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA25789 for hackers-outgoing; Mon, 3 Mar 1997 12:32:19 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.50]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id MAA25781 for ; Mon, 3 Mar 1997 12:32:17 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id NAA08461; Mon, 3 Mar 1997 13:27:34 -0700 From: Terry Lambert Message-Id: <199703032027.NAA08461@phaeton.artisoft.com> Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. To: joerg_wunsch@uriah.heep.sax.de Date: Mon, 3 Mar 1997 13:27:34 -0700 (MST) Cc: hackers@freebsd.org In-Reply-To: from "J Wunsch" at Mar 3, 97 08:36:36 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > Another good idea - but I only have 12 meg in this particular > > > machine. > > > > Now try not bouncing. > > I've seen the failure on a machine that doesn't use bounce buffers. > (No, Terry, it really doesn't have this option in the config file... :) You'll have to go back through his messages, but he did post a kernel config file with them enabled. If you can trigger the problem on a machine with a config without the option, then I suppose it shoots the idea down. 8-(. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.