From owner-freebsd-hackers  Sat Mar  1 14:31:10 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id OAA02356
          for hackers-outgoing; Sat, 1 Mar 1997 14:31:10 -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 OAA02351
          for <hackers@freebsd.org>; Sat, 1 Mar 1997 14:31:07 -0800 (PST)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA05697 for hackers@freebsd.org; Sat, 1 Mar 1997 15:27:15 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199703012227.PAA05697@phaeton.artisoft.com>
Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems.
To: hackers@freebsd.org
Date: Sat, 1 Mar 1997 15:27:15 -0700 (MST)
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

>  Yes, I wish it was that, I'd love to be done with this :-)
> 
>  However, this particular reproduction of the dup-alloc problem
> is with an AHA 1542B and Micropolis ~500meg drive...
> 
>  So, now the question I'm considering is "what could be some
> timing dependent that it affects both IDE and SCSI drivers?"

1542B?

How much RAM do you have?

If you have more than 16M ... it's bouncing.  Try backing down to
16M and not bouncing and see if that's where it is...


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.