From owner-freebsd-hackers Tue Feb 25 19:50:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA11559 for hackers-outgoing; Tue, 25 Feb 1997 19:50:37 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id TAA11553 for ; Tue, 25 Feb 1997 19:50:34 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA09491; Tue, 25 Feb 1997 22:50:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 25 Feb 1997 22:50 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id WAA00283 for ; Tue, 25 Feb 1997 22:15:17 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id WAA19559 for freebsd-hackers@freefall.cdrom.com; Tue, 25 Feb 1997 22:14:29 -0500 (EST) Date: Tue, 25 Feb 1997 22:14:29 -0500 (EST) From: Thomas David Rivers Message-Id: <199702260314.WAA19559@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: A wild idea on the "dup alloc" and "bad dir" panics... Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is just a wild thought I had... We've eliminated different processors, different disk drives, different memory configurations, etc... in an attempt to determine what's common about the machines experiencing these problems. The item that's common for my two machines experiencing the problem that we haven't investigated is: Hercules Monochrome Monitor I know it's *really* reaching here, but can everyone who's involved let me know what kind of monitor they've got connected... Maybe there's something in that device driver that's trashing some random memory, or this happens during a scroll, or something like that... [It is a far stretch, admitedly, but it would explain why this only occurs on a small subset of machines...] Anyway, just a thought... - Dave Rivers -