From owner-freebsd-current@FreeBSD.ORG Mon Aug 4 23:32:58 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 56BDD37B401 for ; Mon, 4 Aug 2003 23:32:58 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3206943F93 for ; Mon, 4 Aug 2003 23:32:57 -0700 (PDT) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.9/8.12.9) id h756WtCf029441; Tue, 5 Aug 2003 08:32:55 +0200 (CEST) (envelope-from sos) From: Soeren Schmidt Message-Id: <200308050632.h756WtCf029441@spider.deepcore.dk> In-Reply-To: <20030804133644.X11878@carver.gumbysoft.com> To: Doug White Date: Tue, 5 Aug 2003 08:32:55 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL98b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 cc: freebsd-current@FreeBSD.ORG cc: ryan chris Subject: Re: port 0xd800-0xd80f at device7.1 on pci0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2003 06:32:58 -0000 It seems Doug White wrote: > On Sun, 3 Aug 2003, ryan chris wrote: > > > > > with dma enabled, a sysinstall will only work under the minimal install, > > and after a certain point, apparently using too much hard drive space > > (showed up with a tar > > -xvf ports.tar) causes a panic with anic errors > > Have you tried replacing the IDE cable(s)? I've seen panics and other > erratic behavior due to bad cables, or a defective 60 pin cable, or even a > 30 pin cable that somehow got detected as a 60 pin. Uhm, the cables are 40 vs 80 conductors :) Anyhow I'm pretty sure this problem is because of the buggy VIA 82C686B southbridge and a matching BIOS that doesn't setup the right workarounds for it to function like intended. Clearly the tweaks we install are not enough on this baby. Recommended action is to update (well sometimes downgrade) the BIOS to a version that makes things work... -Søren