From owner-freebsd-hackers Sun Mar 2 14:44:24 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA07408 for hackers-outgoing; Sun, 2 Mar 1997 14:44:24 -0800 (PST) Received: from peedub.gj.org (newpc.muc.ditec.de [194.120.126.33]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA07401 for ; Sun, 2 Mar 1997 14:44:21 -0800 (PST) Received: from peedub.gj.org (localhost [127.0.0.1]) by peedub.gj.org (8.8.5/8.6.9) with ESMTP id XAA03676 for ; Sun, 2 Mar 1997 23:43:10 GMT Message-Id: <199703022343.XAA03676@peedub.gj.org> X-Mailer: exmh version 2.0gamma 1/27/96 To: freebsd-hackers@freefall.FreeBSD.org Subject: Re: Another installment of the "dup alloc"/"bad dir" panic problems. Reply-To: Gary Jennejohn In-reply-to: Your message of "Sun, 02 Mar 1997 08:17:26 EST." <199703021317.IAA13157@lakes.water.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 02 Mar 1997 23:43:09 +0000 From: Gary Jennejohn Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thomas David Rivers writes: > Also, you should recall that I am experiencing this problem on an >8-meg 386dx (intel 387) with an IDE drive... that kinda points to >something "higher-level" then the physical device drivers... > this may be irrelevant, but IIRC, in an earlier posting you showed the flags you're using to compile the kernel and I586 and I486 were both in there. Seems like at least I586 should NOT be defined for an i386, and probably I486 also. --- Gary Jennejohn Home - Gary.Jennejohn@munich.netsurf.de Work - gjennejohn@frt.dec.com